CentralSquare Solutions Agreement
This CentralSquare Solutions Agreement (the " Agreement"), effective as of the latest date shown on the signature block below (the "Effective Date"), is entered into between CentralSquare Technologies, LLC with its principal place of business in Lake Mary , FL ("CentralSquare") and Rialto Police Department, CA ("Customer"), together with CentralSquare, the "Parties", and each, a "Party".
WHEREAS, Customer entered into a prior agreement for Software products with TriTech Software Systems, a CentralSquare Technologies, LLC company; and
WHEREAS, Customer is a currently licensed end user of the TriTech Vision Software; and WHEREAS, through asset purchase, CentralSquare is the owner of all TriTech Software products, services, and contractual obligations; and WHEREAS, Customer desires to discontinue use of the TriTech Software products and upgrade to the CentralSquare Software solution identified in Exhibit B to this Agreement; and
WHEREAS, this Agreement shall replace and supersede any and all prior agreements directly related to the TriTech Software products being replaced by this Agreement.
WHEREAS, CentralSquare licenses and gives access to certain software applications (“ Solutions”) to its customers and also provides maintenance, support, migration, installation and other professional services; and WHEREAS, Customer desires to license and/or gain access to certain Solutions and receive professional services described herein, and CentralSquare desires to grant and provide Customer license and access to such offerings as well as to provide support and maintenance, subject to the terms and conditions set forth in this Agreement.
NOW, THEREFORE, in consideration of the mutual covenants, terms, and conditions set forth herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, by the signatures of their duly authorized representative below, the Parties intending to be legally bound, agree to all of the following provisions and exhibits of this Agreement:
CentralSquare Technologies, LLC Rialto Police Department
1000 Business Center Drive
Lake Mary, FL 32746
128 N Willow Avenue,
Rialto, CA , 92376
By: \Signature2\ By: \Signature1\
Print Name: \FullName2\ Print Name: \FullName1\
Print Title: \Title2\ Print Title: \Title1\
Date Signed: \DateSigned2\ Date Signed: \DateSigned1\
Rialto Police Department
128 N Willow Avenue,
Rialto, CA , 92376
By: \Signature1\
Print Name: \FullName1\
Print Title: \Title1\
Date Signed: \DateSigned1\
Solution: PSJ Enterprise
Term.
Initial Term. The Initial Term of this Agreement commences as of the Effective Date and will continue in effect for five (5) year(s) from such date unless terminated earlier pursuant to any of the Agreement’s express provisions (the “Initial Term”).
Renewal Term. This Agreement will automatically renew for additional successive one (1) year terms unless earlier terminated pursuant to any of the Agreement’s provisions (a “Renewal Term” and, collectively, with the Initial Term, the “Term”).
Non-Renewal. Either Party may elect to end renewal of the Agreement by issuing a notice of non-renewal, in writing, to the other Party six (6) months prior to the expiration of the Agreement term.
Fees.
In consideration of the rights and services granted by CentralSquare to Customer under this Agreement, Customer shall make payments to CentralSquare pursuant to the amounts and payment terms outlined in Exhibit 1 (the Solution(s) and Services Fee Schedule).
All invoices shall be billed and paid in U.S. dollars (USD) and in accordance with the terms set forth in Exhibit 1. If Customer delays an invoice payment for any reason, Customer shall promptly notify CentralSquare in writing the reasons for such delay. Unless otherwise agreed by both Parties, CentralSquare may apply any payment received to any delinquent amount outstanding.
Rialto Police Department
128 N Willow Avenue,
Rialto, CA , 92376
By: \Signature1\
Print Name: \FullName1\
Print Title: \Title1\
Date Signed: \DateSigned1\
Standard Terms and Conditions
1. Definitions. Capitalized terms not otherwise defined in this Agreement have the meanings set forth below:
1.1. " Affiliate" means any other Entity that directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with, such Entity.
1.2. " Authorized User" means Customer's employees, consultants, contractors, and agents who are authorized by Customer to access and use the Solutions pursuant to this Agreement, and for whom access to the Solutions has been purchased.
1.3. “Baseline Solution ” means the version of a Solution updated from time to time pursuant to CentralSquare’s warranty services and maintenance, but without any other modification.
1.4. " CentralSquare Systems" means the information technology infrastructure used by or on behalf of CentralSquare to deliver the Solutions, including all computers, software, hardware, databases, electronic systems (including database management systems), and networks, whether operated directly by CentralSquare or through the use of third-party services.
1.5. " Customer Data " means information, data, and content, in any form or medium, collected, downloaded, or otherwise received, directly or indirectly from Customer, an Authorized User or end-users by or through the Solutions, provided the data is not personally identifiable and not identifiable to Customer.
1.6. " Customer Systems" means the Customer's information technology infrastructure, including computers, software, hardware, databases, electronic systems (including database management systems), and networks, whether operated by Customer or through the third-party services.
1.7. “Defect ” means a material deviation between the Baseline Solution and its Documentation, for which Customer has given CentralSquare sufficient information to enable CentralSquare to replicate the deviation on a computer configuration that is both comparable to the Customer Systems and that is under CentralSquare’s control. Further, with regard to any custom modification, Defect means a material deviation between the custom modification and the CentralSquare generated specification and Documentation for such custom modification, and for which Defect Customer has given CentralSquare sufficient information to enable CentralSquare to replicate the deviation on a computer configuration that is both comparable to the Customer Systems and that is under CentralSquare’s control.
1.8. “Delivery” means:
1.8.1. For on-premise Solutions, Delivery shall be when CentralSquare delivers to Customer the initial copies of the Solutions outlined in Exhibit 1 by whichever the following 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. Physical shipment is on FOB - CentralSquare’s shipping point, and electronic delivery is at the time CentralSquare provides Customer with access to download the Solutions.
1.8.2. For cloud-based Solutions Delivery shall be whichever the following applies and occurs first when Authorized Users have (a) received log-in access to the Solution or any module of the Solution or (b) received access to the Solution via a URL.
1.9. " Documentation" means any manuals, instructions, or other documents or materials that CentralSquare provides or makes available to Customer in any form or medium and which describe the functionality, components, features, or requirements of the Solution(s), including any aspect of its installation, configuration, integration, operation, use, support, or maintenance.
1.10. “End User Training” means the process of educating general users of the Software on the operation of the Software.
1.11. “Entity ” means an individual, corporation, partnership, joint venture, limited liability entity, governmental authority, unincorporated organization, trust, association, or other organization.
1.12. “Hardware” means any equipment, computer systems, servers, storage devices, peripherals, and any other tangible assets purchased under this Agreement.
1.13. " Intellectual Property Rights" means any and all registered and unregistered rights granted, applied for, or otherwise now or hereafter in existence under or related to any patent, copyright, trademark, trade secret, database protection, or other intellectual property rights laws, and all similar or equivalent rights or forms of protection, in any part of the world.
1.14. “Managed Services Hardware” means any equipment, computer systems, servers, peripherals, and any other tangible asset purchased as a subscription under this Agreement.
1.15. “Maintenance” means optimization, error correction, modifications, and Updates (defined herein) to CentralSquare Solutions to correct any known Defects and improve performance. Maintenance will be provided for each Solution, the hours and details of which are described in Exhibit 2 (Maintenance and Support)
1.16. “New or Major Releases” means new versions of a Baseline Solution (e.g., version 4.0, 5.0 etc.) not provided as part of Maintenance.
1.17. " Personal Information" means any information that does or can identify a specific individual or by or from which a specific individual may be identified, contacted, or located. Personal Information includes all "nonpublic personal information" as defined under the Gramm -Leach-Bliley Act, "protected health information" as defined under the Health and Insurance Portability and Accountability Act of 1996, "Personal Data" as defined in the EU General Data Protection Regulation (GDPR 2018), "Personal Information" as defined under the Children's Online Privacy Protection Act of 1998, and all rules and regulations issued under any of the foregoing.
1.18. “Professional Services” means configuration, installation, implementation, development work, training or consulting services including custom modification programming, support relating to custom modifications, on -site support services, assistance with data transfers, system restarts and reinstallations provided by CentralSquare.
1.19. “Project Kickoff” is a meeting to occur shortly after contract execution between CentralSquare and Customer in which goals and objectives are set forth, all parties relevant team members are identified, and scope, timelines, and milestones are reviewed.
1.20. “Reliability Period” is the time period in which the Software is tested and confirmed reliable by successfully completing thirty (30) continuous days in a live environment with no repeatable Priority 1 or Priority 2 issues as defined in Exhibit 2, unless otherwise agreed in a statement of work.
1.21. “Software ” means the software program(s) (in object code format only) identified on Exhibit 1 (Solution(s) and Services Fee Schedule). The term “Software” excludes any Third-Party Software.
1.22. “Software Version” means the base or core version of the Solution Software that contains significant new features and significant fixes and is available to the Customer. The nomenclature used for updates and upgrades consists of major, minor, build, and fix and these correspond to the following digit locations of a release, a,b,c,d. An example of which would be 7.4.1.3, where the 7 refers to the major release, the 4 refers to the minor release, the 1 refers to the build, and the 3 refers to a fix.
1.23. " Solutions" means the software, Documentation, development work, CentralSquare Systems and any and all other information, data, documents, materials, works, and other content, devices, methods, processes, hardware, software, technologies and inventions, including any deliverables, technical or functional descriptions, requirements, plans, or reports, provided or used by CentralSquare or any Subcontractor in connection with Professional Services or Support Services rendered under this Agreement.
1.24. “Support Services” means Maintenance, Enhancements, implementation of New Releases, and general support efforts to respond to incidents reported by Customer in accordance with Exhibit 2 (Maintenance & Support) and Exhibit 8 (Managed Services Provisions), if applicable.
1.25. " Third-Party Materials" means materials and information, in any form or medium, including any software, documents, data, content, specifications, products, related services, equipment, or components of or relating to the Solutions that are not proprietary to CentralSquare.
2. License, Access, and Title.
2.1. License Grant. For any Solution designated as a “license” on Exhibit 1, Customer is granted a perpetual (unless terminated as provided herein), nontransferable, nonexclusive right and license to use the Software for Customer’s own internal use for the applications described in the Statement of Work, in the applicable environment (e.g., production, test, training, or disaster recovery system) and in the quantity set forth in Exhibit 1. Additional software licenses purchased after the execution of this Agreement shall also be licensed in accordance with the provisions of this section. Customer shall not use, copy, rent, lease, sell, sublicense, modify, create derivative works from/of, or transfer any software, or permit others to do said acts, except as provided in this Agreement. Any such unauthorized use shall be void and may result in immediate and automatic termination of the applicable license. In such event, Customer shall not be entitled to a refund of any license fees paid. Notwithstanding, Customer shall be entitled to use software at the applicable designated location for the purpose of the application(s) described in the Statement of Work to provide services for itself and other Affiliate governmental agencies/entities, provided that the Software is installed and operated at only one physical location. The Software license granted in this Agreement or in connection with it are for object code only and do not include a license or any rights to source code whatsoever.
2.2. Acce
ss Grant . For any Solution designated as a “subscription” on Exhibit 1, so long as subscription fees are paid and current, (unless terminated as provided herein), Customer is granted a nontransferable, nonexclusive right to use the software for the Customer’s own internal use for the applications described in the Statement of Work, in the applicable environment (e.g., production, test, training, or disaster recovery system) and in the quantity set forth in Exhibit 1. Additional CentralSquare software subscriptions purchased after the execution of this Agreement shall also be accessed in accordance with the provisions of this section. Customer shall not use, copy, rent, lease, sell, sublicense, modify, create derivative works from/of, or transfer any software, or permit others to do said acts, except as provided in this Agreement. Any such unauthorized use shall be void and may result in immediate and automatic termination of the applicable access. In such event, Customer shall
not be entitled to a refund of any subscription fees paid. Notwithstanding, Customer shall be entitled to use software at the applicable designated location for the purpose of the application(s) described in the Statement of Work to provide services for itself and other Affiliate governmental agencies/entities. The subscription access granted in this Agreement or in connection with it are for object code only and do not include a license or any rights to source code whatsoever.
2.3. Documentation License. CentralSquare hereby grants to Customer a non -exclusive, non -sublicensable, non-transferable license to use the Documentation during the Term solely for Customer's internal business purposes in connection with its use of the Solutions.
2.4. A
pplication Programming Interface “API” . If the Customer has purchased any Application Programming Interface (API) license or subscription, Customer may use such API for Customer’s own internal use to develop interfaces which enable interfacing with the applicable CentralSquare Software purchased herein. The development and use of such interfacing applications is specifically permitted under the use granted herein and shall not be deemed derivative works provided that they are not, in fact, derived from the CentralSquare Software or the ideas, methods of operation, processes, technology or know -how implemented therein. Other than the usage rights granted herein, Customer shall not acquire any right, title or interest in the CentralSquare Software or API by virtue of the interfacing of such applications, whether as joint owner, or otherwise. Should Customer desire to provide or share the API to a third-party, the third-party must enter into an API Access Agreement by and between the third-party and CentralSquare directly to govern the usage rights and restrictions of the applicable API.
2.5. H
ardware. Subject to the terms and conditions of this Agreement, CentralSquare agrees to deliver, through hardware vendors, the Hardware itemized on Exhibit 1. The risk of loss or damage will pass to Customer upon the date of delivery to the Customer specified facility. Upon delivery and full satisfaction of the Hardware payment obligations, Hardware shall be deemed accepted and Customer will acquire good and clear title to Hardware. All Hardware manufacturer warranties will be passed through to Customer. CentralSquare expressly disclaims, and Customer hereby expressly waives all other Hardware warranties, express or implied, without limitation, warranties of merchantability and fitness for a particular purpose.
2.6. M
anaged Services Hardware. Subject to the terms and conditions of this Agreement, CentralSquare agrees to deliver the Managed Services Hardware itemized on Exhibit 1. So long as the applicable subscription fees are paid and current, Customer shall maintain a limited right in possessory interest in the Managed Services Hardware. No title in the Managed Services Hardware will pass to Customer at any time or for any reason. Customer agrees to maintain adequate insurance against fire, theft, or other loss for the Managed Services Hardware full insurable value. CentralSquare shall coordinate any defect or warranty claims in accordance with Exhibit 8.
2.7. R
eservation of Rights. Nothing in this Agreement grants any right, title, or interest in or to any Intellectual Property Rights in or relating to the Solutions, or Third-Party Materials, whether expressly, by implication, estoppel, or otherwise. All right, title, and interest in the Solutions, and the Third- Party Materials are and will remain with CentralSquare and the respective rights holders.
3. U se Restrictions. Authorized Users shall not:
3.1. copy, modify, or create derivative works or improvements of the Solutions, or rent, lease, lend, sell, sublicense, assign, distribute, publish, transfer, or otherwise make available any Solutions to any Entity, including on or in connection with the internet or any time-sharing, service bureau, software as a service, cloud, or other technology or service;
3.2. reverse engineer, disassemble, decompile, decode, adapt, or otherwise attempt to derive or gain access to the source code of the Solutions, in whole or in part;
3.3. bypass or breach any security device or protection used by Solutions or access or use the Solutions other than by an Authorized User through the use of his or her own then valid access;
3.4. input, upload, transmit, or otherwise provide to or through the CentralSquare Systems, any information or materials that are unlawful or injurious, or contain, transmit, or activate any harmful code (any software, hardware, device, or other technology, including any virus, worm, malware, or other malicious computer code, the purpose or effect of which is to (a) permit unauthorized access to, or to destroy, disrupt, disable, distort, or otherwise harm or impede any (i) computer, software firmware, hardware, system or network; or (ii) any application or function of any of the foregoing or the security, integrity, confidentiality, or use of any data processed thereby; or (b) prevent Customer or any Authorized User from accessing or using the Solutions as intended by this Agreement;
3.5. damage, destroy, disrupt, disable, impair, interfere with, or otherwise impede or harm in any manner the CentralSquare Systems, or CentralSquare's provision of services to any third-party, in whole or in part;
3.6. remove, delete, alter, or obscure any trademarks, specifications, Documentation, warranties, or disclaimers, or any copyright, trademark, patent, or other intellectual property or proprietary rights notices from any Documentation or Solutions, includin g any copy thereof;
3.7. access or use the Solutions in any manner or for any purpose that infringes, misappropriates, or otherwise violates any Intellectual Property Right or other right of any third-party, or that violates any applicable law;
3.8. access or use the Solutions for purposes of competitive analysis of the Solutions, the development, provision, or use of a competing software service or product or any other purpose that is to CentralSquare's detriment or commercial disadvantage or otherwise access or use the Solutions beyond the scope of the authorization granted in Section 2.
4. Audit.
4.1. CentralSquare shall have the right to audit Customer’s use of the Software to monitor compliance with this Agreement.
Customer shall permit CentralSquare and its directors, officers, employees, and agents to have on-site access at Customer’s premises (or remote access as the case may be) during normal business hours to such systems, books, and records for the purpose of verifying license counts, access counts, and overall compliance with this Agreement. Customer shall render reasonable cooperation to CentralSquare as requested. If as a result of any audit or inspection CentralSquare substantiates a deficiency or non-compliance, or if an audit reveals that Customer has exceeded the restrictions on use, Customer shall be required to pay for any delinquencies in compliance and prompt payment of any underpayment of Fees.
5. Customer Obligations.
5.1. Customer Systems and Cooperation. Customer shall at all times during the Term: (a) set up, maintain, and operate in good repair all Customer Systems on or through which the Solutions are accessed or used; (b) provide CentralSquare Personnel with such access to Customer's premises and Customer Systems as is necessary for CentralSquare to perform the Support Services in accordance with the Support Standards and specifications and if required by CentralSquare, remote access in accordance with Exhibit 3 (CentralSquare Access Management Policy); and (c) provide all cooperation as CentralSquare may reasonably request to enable CentralSquare to exercise its rights and perform its obligations under this Agreement.
5.2. E
ffect of Customer Failure or Delay. CentralSquare is not responsible or liable for any delay or failure of performance caused in whole or in part by Customer's delay in performing, or failure to perform, any of its obligations under this Agreement.
5.3. Corrective Action and Notice. If Customer becomes aware of any actual or threatened activity prohibited by Section 6 , Customer shall, and shall cause its Authorized Users to, immediately: (a) take all reasonable and lawful measures within their respective control that are necessary to stop the activity or threatened activity and to mitigate its effects (including, where applicable, by discontinuing and preventing any unauthorized access to the Solutions and permanently erasing from their systems and destroying any data to which any of them gained unauthorized access); and (b) notify CentralSquare of any such actual or threatened activity.
5.4. M
aintaining Current Versions of CentralSquare Solutions. In accordance with Exhibit 2 (Maintenance & Support) and Exhibit 8 (Managed Services Provisions), if applicable. Customer shall install and/or use any New or Major Release within one year of being made available by CentralSquare to mitigate a performance problem, ineligibility for Support Services, or an infringement claim.
6. Professional Services.
6.1. Compliance with Customer Policies. While CentralSquare personnel are performing services at Customer's site, CentralSquare personnel will comply with Customer’s reasonable procedures and site policies that are generally applicable to Customer’s other suppliers providing similar services and that have been provided to CentralSquare in writing or in advance.
6.2. C ontributed Material. In the process of CentralSquare’s performing Professional Services, Customer may, from time to time, provide CentralSquare with designs, plans, or specifications, improvements, works or other material for inclusion in, or making modifications to, the Solutions, the Documentation or any other deliverables (“ Contributed Material”). Customer grants to CentralSquare a nonexclusive, irrevocable, perpetual, transferable right, without the payment of any royalties or other compensation of any kind and without the right of attribution, for CentralSquare, CentralSquare’s Affiliates and CentralSquare’s licensees to make, use, sell and create derivative works of the Contributed Material.
6.3. C riminal Justice Information Services. To the extent permissible, the parties acknowledge that any employee of CentralSquare who has been granted Criminal Justice Information Services ("CJIS") clearance in any state within the United States shall be deemed to have satisfied the CJIS clearance requirements under this Agreement. This provision is based on the principle of reciprocity, recognizing the validity of CJIS clearance across state lines.
Notwithstanding the foregoing, CentralSquare shall ensure that all employees comply with the applicable laws and regulations of the state in which services under this Agreement are performed. CentralSquare shall also ensure that all employees continue to meet the standards required for CJIS clearance and shall promptly notify Customer of any changes in an employee’s CJIS clearance status.
6.4 Compliance with California CJIS Information and Clearance Requirements Notwithstanding the foregoing, CentralSquare shall ensure that all employees comply with the applicable laws and regulations of California in which services under this Agreement are performed. CentralSquare shall also ensure that all employees continue to meet the standards required for CJIS clearance and shall notify Customer of any changes in an employee’s CJIS clearance status. in alignment with the requirements contained in the most current version of the FBI CJIS Security Policy.
CentralSquare maintains a security program for managing access to client data, particularly HIPAA and CJIS information (“Security Approved Personnel”). This includes:
1. A pre-employment background check;
2. Security training required by Federal CJIS regulations;
3. Criminal background checks/fingerprints required by Federal or State regulations and;
4. All other Personnel Screening and Training requirement necessary for unescorted access to unencrypted CJI data.
CentralSquare will work with the Client to provide reasonably required documentation (such as the CJIS Security Addendum Certification form and CLETS documents).
Client is responsible for maintaining the required certifications for access to Client’s state CJIS system(s), NCIC, and/or other local, state, federal, and/or other applicable systems.
Compliance with CJIS Controls
The parties agree to be bound by and comply with the Criminal Justice Information Services (CJIS) Security Policy controls.
Each party shall implement and maintain all necessary measures to ensure compliance with the CJIS Security Policy, as updated from time to time.
7. Confidentiality.
7.1. Nondisclosure. The Parties agree, unless otherwise provided in this Agreement or required by law, not to use or make each other's Confidential Information available to any third party for any purpose other than as necessary to perform under this Agreement. “Confidential Information” means the Solution(s), Software, and customizations in any embodiment, and either Party’s technical and business information relating to inventions or software, research and development, future product specifications, engineering processes, costs, profit or margin information, marketing and future business plans as well as any and all internal Customer and employee information, and any information exchanged by the Parties that is clearly marked with a confidential, private or proprietary legend or which, by its nature, is commonly understood to be confidential.
7.2. Exceptions. A Party's Confidential Information shall not include information that: (a) is or becomes publicly available through no act or omission of the recipient; (b) was in the recipient’s lawful possession prior to the disclosure and was not obtained by the recipient either directly or indirectly from the disclosing Party; (c) is lawfully disclosed to the recipient by a third party without restriction on recipient’s disclosure, and where recipient was not aware that the information was the confidential information of discloser; (d) is independently developed by the recipient without violation of this Agreement; or (e) is required to be disclosed by law.
8. Security.
8.1. CentralSquare will implement commercially reasonable administrative, technical and physical safeguards designed to ensure the security and confidentiality of Customer Data, protect against any anticipated threats or hazards to the security or integrity of Customer Data, and protect against unauthorized access or use of Customer Data. CentralSquare will review and test such safeguards on no less than an annual basis.
8.2. Customer shall maintain, in connection with the operation or use of the Solutions, adequate technical and procedural access controls and system security requirements and devices, necessary for data privacy, confidentiality, integrity, authorization, authentication, non-repudiation, virus detection and eradication.
8.3. To the extent that Authorized Users are permitted to have access to the Solutions, Customer shall maintain agreements with such Authorized Users that adequately protect the confidentiality and Intellectual Property Rights of CentralSquare in the Solutions and Documentation and disclaim any liability or responsibility of CentralSquare with respect to such Authorized Users.
9. Personal Data. If CentralSquare processes or otherwise has access to any personal data or Personal Information on Customer’s behalf when performing CentralSquare’s obligations under this Agreement, then:
9.1. Customer shall be the data controller (where “data controller” means an entity which alone or jointly with others determines purposes for which and the manner in which any personal data are, or are to be, processed) and CentralSquare shall be a data processor (where “data processor” means an entity which processes the data only on behalf of the data controller and not for any purposes of its own);
9.2. Customer shall ensure that it has obtained all necessary consents and it is entitled to transfer the relevant personal data or Personal Information to CentralSquare so that CentralSquare may lawfully use, process and transfer the personal data and Personal Information in accordance with this Agreement on Customer’s behalf, which may include CentralSquare processing and transferring the relevant personal data or Personal Information outside the country where Customer and the Authorized
Users are located in order for CentralSquare to provide the Solutions and perform its other obligations under this Agreement; and
9.3. CentralSquare shall process personal data and information only in accordance with lawful and reasonable written instructions given by Customer and as set out in and in accordance with the terms of this Agreement; and
9.4. CentralSquare shall take reasonable steps to ensure that its employees, agents and contractors who may have access to Personal Information are persons who need to know / access the relevant Personal Information for valid business reasons; and
9.5. each Party shall take appropriate technical and organizational measures against unauthorized or unlawful processing of the personal data and Personal Information or its accidental loss, destruction or damage so that, having regard to the state of technological development and the cost of implementing any measures, the measures taken ensure a level of security appropriate to the harm that might result from such unauthorized or unlawful processing or accidental loss, destruction or damage in relation to the personal data and Personal Information and the nature of the personal data and Personal Information being protected. If necessary, the Parties will cooperate to document these measures taken.
10. Representations and Warranties.
10.1. Intellectual Property Warranty. CentralSquare represents and warrants that (a) it is the sole and exclusive owner of (or has the right to license) the software; (b) it has full and sufficient right, title and authority to grant the rights and/or licenses granted under this Agreement; (c) the software does not contain any materials developed by a third party used by CentralSquare except pursuant to a license agreement; and (d) the software does not infringe any patent, or copyright.
10.2. Intellectual Property Remedy. In the event that any third party asserts a claim of infringement against the Customer relating to the software contained in this Agreement, CentralSquare shall indemnify and defend the Customer pursuant to section
13.1 of this Agreement. In the case of any such claim of infringement, CentralSquare shall either, at its option, (1) procure for Customer the right to continue using the software; or (2) replace or modify the software so that that it becomes non-infringing, but equivalent in functionality and performance.
10.3. Software Warranty . CentralSquare warrants to Customer that: (i) the Software will substantially conform in all material respects to the specifications set forth in the Documentation, when installed, operated and used as recommended in the Documentation and in accordance with this Agreement; and (ii) at the time of delivery the Software does not contain any virus or other malicious code.
10.4. S
oftware Remedy . If a D efect is confirmed in the CentralSquare Software, CentralSquare shall, at its option, reinstall the Software or correct the Defects. Defects that occur in the Software after the Warranty Period will be corrected pursuant to Exhibit 2 (Maintenance & Support) and Exhibit 8 (Managed Services Provisions), if applicable.
10.5. Se rvices Warranty. CentralSquare warrants that the Professional Services delivered will substantially conform to the deliverables specified in the applicable statement of work and that all Professional Services will be performed in a professional and workmanlike manner consistent with industry standards for similar work. If Professional Services do not substantially conform to the deliverables, Customer shall notify CentralSquare of such non-conformance in writing, within 10 days from completion of Professional Service, and CentralSquare shall promptly repair the non-conforming deliverables.
10.6. D
isclaimer of Warranty. EXCEPT FOR THE EXPRESS LIMITED WARRANTIES SET FORTH ABOVE,
CENTRALSQUARE MAKES NO WARRANTIES WHATSOEVER, EXPRESSED OR IMPLIED, WITH REGARD TO THE
INTELLECTUAL PROPERTY, SOFTWARE, PROFESSIONAL SERVICES, AND/OR ANY OTHER MATTER RELATING
TO THIS AGREEMEN T, AND THAT CENTRALSQUARE DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ALL WARRANTIES ARISING FROM COURSE OF DEALING,
USAGE OR TRADE PRACTICE, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR TITLE. FURTHER, CENTRALSQUARE EXPRESSLY DOES NOT
WARRANT THAT A SOLUTION, ANY CUSTOM MODIFICATION OR ANY IMPROVEMENTS WILL BE USABLE BY
CUSTOMER IF THE SOLUTION OR CUSTOM MODIFICATION HAS BEEN MODIFIED BY ANYONE OTHER THAN
CENTRALSQUARE PERSONNEL, OR WILL BE ERROR FREE, WILL OPERATE WITHOUT INTERRUPTION OR WILL
BE COMPATIBLE WITH ANY HARDWARE OR SOFTWARE EXCEPT TO THE EXTENT EXPRESSLY SET FORTH IN THE DOCUMENTATION. ALL THIRD-PARTY MATERIALS ARE PROVIDED “AS-IS” AND ANY REPRESENTATION OR WARRANTY OF OR CONCERNING ANY OF THEM IS STRICTLY BETWEEN CUSTOMER AND THE THIRD-PARTY.
THIS AGREEMENT DOES NOT AMEND, OR MODIFY CENTRALSQUARE’S WARRANTY UNDER ANY AGREEMENT OR ANY CONDITIONS, LIMITATIONS, OR RESTRICTIONS THEREOF.
11. Notices. All notices and other communications required or permitted under this Agreement must be in writing and will be deemed given when delivered personally, sent by United States registered or certified mail, return receipt requested; transmitted by facsimile or email confirmed by first class mail, or sent by overnight courier. Notices must be sent to a Party at its address shown below, or to such other place as the Party may subsequently designate for its receipt of notices in writing by the other Party.
If to CentralSquare : CentralSquare Technologies, LLC
1000 Business Center Dr.
Lake Mary, FL 32746
Phone: 407-304-3235
Attention: Legal/Contracts
If to Customer: Rialto Police Department
128 N Willow Avenue
Rialto, CA 92376
Phone: 909-421-4926
Email: [email protected]
Attention: Cameron Nelson
12. Force Majeure.
Neither Party shall be responsible for failure to fulfill its obligations hereunder, or be liable for damages resulting from delay in performance as a result of war, fire, strike, riot or insurrection, natural disaster, pandemic or epidemic, delay of carriers, governmental order or regulation, complete or partial shutdown of plant, unavailability of equipment, software, or services from suppliers, default of a subcontractor or vendor to the Party if such default arises out of causes beyond the reasonable control of such subcontr actor or vendor, the acts or omissions of the other Party, or its officers, directors, employees, agents, contractors, or elected officials, and/or other occurrences beyond the Party’s reasonable control (“Excusable Delay” hereunder). In the event of such Excusable Delay, performance shall be extended on a day for day basis or as otherwise reasonably necessary to compensate for such delay.
13. Indemnification.
13.1. CentralSquare Indemnification. CentralSquare shall indemnify, defend, and hold harmless Customer from any and all Claims or liability, including attorneys' fees and costs, brought by a third party, allegedly arising out of, in connection with, or incident to any loss, damage or injury to persons or property or arising solely from a wrongful or negligent act, error or omission of CentralSquare, its employees, agents, contractors, or any subcontractor as a result of CentralSquare’s or any subcontractor’s performance pursuant to this Agreement; however, CentralSquare shall not be required to indemnify Customer for any claims caused to the extent of the negligence or wrongful act of Customer, its employees, agents, or contractors. Notwithstanding anything to the contrary in the foregoing, if a Claim or liability results from or is contributed to by the actions or omissions of Customer, or its employees, agents or contractors, CentralSquare’s obligations under this provision shall be reduced to the extent of such actions or omissions based upon the principle of comparative fault.
13.2. Customer Indemnification. To the extent allowable by law, Customer shall indemnify, defend, and hold harmless CentralSquare from any and all Claims or liability, including attorneys' fees and costs, allegedly arising out of, in connect ion with, or incident to any loss, damage or injury to persons or property or arising solely from a wrongful or negligent act, error or omission of Customer, its employees, agents, contractors, or any subcontractor as a result of Customer’s performance pursuant to this Agreement; however, Customer shall not be required to indemnify CentralSquare f or any Claims or actions caused to the extent of the negligence or wrongful act of CentralSquare, its employees, agents, or contractors.
Notwithstanding anything to the contrary in the foregoing, if a Claim or liability results from or is contributed to by the actions or omissions of CentralSquare, or its employees, agents or contractors, Customer’s obligations under this provision shall be reduced to the extent of such actions or omissions based upon the principle of comparative fault.
13.3. " Claim" in this Section 13 means any claim, cause of action, demand, lawsuit, dispute, inquiry, audit, notice of violation, proceeding, litigation, citation, summons, subpoena or investigation of any nature, civil, criminal, administrative, regulatory or other, whether at law, in equity, or otherwise.
14. T ermination .
14.1. Either Party may terminate this Agreement for a material breach in accordance with this subsection. In such event, the disputing Party shall deliver written notice of its intent to terminate along with a description in reasonable detail of the problems for which the disputing Party is invoking its right to terminate and the specific requirement within this Agreement or any exhibit or schedule hereto that the disputing Party is relying upon. Following such notice, the Parties shall commence dispute resolution procedures in accordance with the dispute resolution procedure pursuant to Section 17.
14.2. CentralSquare shall have the right to terminate this Agreement based on Customer’s failure to pay undisputed amounts due under this Agreement more than ninety (90) days after delivery of written notice of non-payment.
14.3. Customer shall have the right to terminate if the proper appropriation of funds for the continuation of this Agreement is not available for any fiscal year after the first fiscal year during the Term, then this Agreement may be terminated. To effect t he termination of this Agreement, Customer shall, within forty -five (45) days following the beginning of the fiscal year for which the proper appropriation is not available, provide CentralSquare with written notice of the failure to obtain the proper
appropriation of funds. Such notice shall be accompanied by the payment of all sums then owed CentralSquare under this Agreement, if any.
14.4. Customer may also terminate for convenience, in whole or in part, at any time by providing thirty (30) days written notice.
Should Customer terminate for convenience during any twelve (12) month term, CentralSquare shall provide a pro-rated refund for any on-premise subscription asset designated on Exhibit 1, with “(OP)”. Should Customer terminate for convenience, in whole or in part, any cloud hosted subscription asset, no pre-paid fees shall be returned, or pro-rated refund be given, for any remaining months on the then current term. Should Customer terminate for convenience, in whole or in part, any third-party asset, no pre-paid fees shall be returned, or pro-rated refund be given, for any remaining months on the then current term.
15. Effect of Termination or Expiration. On the expiration or earlier termination of this Agreement:
15.1. All rights, licenses, and authorizations granted to Customer hereunder will immediately terminate and Customer shall immediately cease all use of CentralSquare’s Confidential Information and the Solutions, and within ninety (90) days deliver to CentralSquare, or at CentralSquare’s request destroy and erase CentralSquare’s Confidential Information from all systems Customer directly or indirectly controls; and
15.2. All licenses, access or subscription fees, services rendered but unpaid, and any amounts due by Customer to CentralSquare of any kind shall become immediately payable and due no later than forty -five (45) days after the effective date of the termination or expiration, including anything that accrues within those forty-five (45) days.
15.3. The provisions set forth in the following sections, and any other right or obligation of the Parties in this Agreement that, by its nature (including but not limited to: Use Restrictions, Confidential Information, Warranty Disclaimers, Indemnifications, & Limitations of Liability), will survive any expiration or termination of this Agreement.
15.4. In the event that Customer terminates this Agreement or cancels any portions of a project (as may be set forth in a Statement of Work) prior to Go Live (which shall be defined as “first use of a Solution or module of a Solution in a production environment, unless otherwise agreed by the Parties in a statement of work”), Customer shall pay for all Professional Services actually performed by CentralSquare on a time and materials basis, regardless of the payment terms in Exhibit 1.
15.5. Return of Customer Data. If Customer requests in writing at least ten (10) days prior to the effective date of expiration or earlier termination of this Agreement, CentralSquare shall within sixty (60) days following such expiration or termination, deliver to Customer in CentralSquare’s standard format the then most recent version of Customer Data maintained by CentralSquare.
15.6. Deconversion. In the event of (i) expiration or earlier termination of this Agreement, or (ii) Customer no longer purchasing certain Solutions (including those indicated to be Third-Party Materials), if Customer requests assistance in the transfer of Customer Data to a different vendor’s applications (“Deconversion”), CentralSquare will provide reasonable assistance.
CentralSquare and Customer will negotiate in good faith to establish the relative roles and responsibilities of CentralSquare and Customer in effecting Deconversion, as well as the appropriate date for completion. CentralSquare shall be entitled to receive compensation for any additional consultation, services, software, and documentation required for Deconversion on a time and materials basis at CentralSquare’s then standard rates.
15.7. Termination of this Agreement shall not relieve either Party of any other obligation incurred one to the other prior to termination.
16. Assignment. Neither this Agreement nor any rights or obligations hereunder shall be assigned or otherwise transferred by either Party without the prior written consent of the other Party, which consent will not be unreasonably withheld; provided however , that in the event of a merger or acquisition of all or substantially all of CentralSquare’s assets, CentralSquare may assign this Agreement to an entity ready, willing and able to perform CentralSquare’s executory obligations hereunder.
17. D ispute Resolution . Any dispute, controversy or claim arising out of or relating to this Agreement (each, a “Dispute”), including the breach, termination, or validity thereof, shall be resolved as follows:
17.1. G ood Faith Negotiations. The Parties agree to send written notice to the other Party of any Dispute (“Dispute Notice”). After the other Party receives the Dispute Notice, the Parties agree to undertake good faith negotiations to resolve the Dispute. Each Party shall be responsible for its associated travel and other related costs.
17.2. E scalation to Mediation. If the Parties cannot resolve any Dispute through good faith negotiations, the dispute will be escalated to non-binding mediation, with the Parties acting in good faith to select a mediator and establishing the mediation process. The Parties agree the mediator’s fees and expenses, and the mediator’s costs incidental to the mediation, will be shared equally between the Parties. The Parties shall bear their own fees, expenses, and costs.
17.3. C
onfidential Mediation. The Parties further agree all written or oral offers, promises, conduct, and statements made in the course of the mediation are confidential, privileged, and inadmissible for any purpose in any litigation, arbitration or othe r proceeding involving the Parties. However, evidence that is otherwise admissible or discoverable shall not be rendered inadmissible or non-discoverable as a result of its use in the mediation.
17.4. Litigation. If the Parties cannot resolve a Dispute through mediation, then once an impasse is declared by the mediator either Party may pursue litigation in a court of competent jurisdiction.
18. W aiver/Severability. The failure of any Party to enforce any of the provisions hereof will not be construed to be a waiver of the right of such Party thereafter to enforce such provisions. If any provision of this Agreement is found to be unenforceable, that provision will be enforced to the maximum extent possible, and the validity, legality and enforceability of the remaining provisions will not in any way be affected or impaired thereby.
19. L IABILITY . NOTWITHSTANDING ANY PROVISION WITHIN THIS AGREEMENT TO THE CONTRARY, AND REGARDLESS OF THE NUMBER OF LOSSES, WHETHER IN CONTRACT, EQUITY, STATUTE, TORT, NEGLIGENCE, OR OTHERWISE:
19.1. NEITHER PARTY SHALL HAVE LIABILITY TO THE OTHER PARTY FOR ANY SPECIAL, INDIRECT, INCIDENTAL,
PUNITIVE, EXEMPLARY, LIQUIDATED, OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING BUT NOT
LIMITED TO, REPLACEMENT COSTS, AND NEITHER PARTY SHALL BE LIABLE TO THE OTHER PARTY FOR
LOSSES OF PROFIT, REVENUE, INCOME, BUSINESS, ANTI CIPATED SAVINGS, DATA, AND REPUTATION, AND
MORE GENERALLY, ANY LOSSES OF AN ECONOMIC OR FINANCIAL NATURE, REGARDLESS OF WHETHER SUCH
LOSSES MAY BE DEEMED AS CONSEQUENTIAL OR ARISING DIRECTLY AND NATURALLY FROM THE INCIDENT
GIVING RISE TO THE CLAIM, AND REGARDLESS OF WHETHER SUCH LOSSES ARE FORESEEABLE OR WHETHER EITHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES; AND
19.2. CENTRALSQUARE’S TOTAL LIABILITY ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT SHALL NOT EXCEED (i) THE AMOUNT(S) ACTUALLY PAID BY CUSTOMER TO CENTRALSQUARE HEREUNDER FOR THE LAST TWELVE (12) MONTHS PRIOR TO THE DATE THE CLAIM AROSE OR (ii) (II) IN THE CASE OF BODILY INJURY,
PERSONAL INJURY, OR PROPERTY DAMAGE FOR WHICH DEFENSE AND INDEMNITY COVERAGE IS PROVIDED BY CENTRALSQUARE’S INSURANCE CARRIER, THE LESSER OF THE COVERAGE LIMITS OF
SUCH INSURANCE OR THE AMOUNT ACTUALLY PAID BY THE APPLICABLE INSURANCE CARRIER FOR SUCH DAMAGE.
20. I nsurance. During the term of this Agreement, CentralSquare shall maintain insurance coverage covering its operations in accordance with Exhibit 4 (Certificate of Insurance (Evidence of Coverage)) and in no event shall the amount of coverage shown in Exhibit 4 be reduced during the term of this Agreement and for a period of not less than three (3) years thereafter. Upon request by Customer, CentralSquare shall include Customer as an additional insured on applicable insurance policies provided under this Agreement. CentralSquare shall provide proof of current coverage during the term of this Agreement.
21. T hird-Party Materials. CentralSquare may, from time to time, include third parties to perform services, provide software, or provide equipment. Customer acknowledges and agrees CentralSquare provides front-line support services for these Third-Party Materials, but these third parties assume all responsibility and liability in connection with the Third-Party Materials. CentralSquare is not authorized to make any representations or warranties that are binding upon the third-party or to engage in any other acts that are binding upon the third-party, except specifically that CentralSquare is authorized to represent third-party fees and to accept payment of such amounts from Customer on behalf of the third-party for as long as such third-party authorizes CentralSquare to do so. As a condition precedent to installing or accessing certain Third- Party Materials, Customer may be required to execute a click -through, shrink-wrap End User License Agreement (“EULA”) or similar agreement provided by the Third-Party Materials provider. If mapping information is supplied with the CentralSquare Software, CentralSquare makes no representation or warranty as to the completeness or accuracy of the mapping data provided with the CentralSquare Software. The completeness or accuracy of such data is solely dependent on the information supplied by the Customer or the mapping database vendor to CentralSquare. All third-party materials are provided “as-is” and any representation or warranty concerning them is strictly between Customer and the third-party.
22. S
ubcontractors . CentralSquare may from time to time, in its discretion, engage third parties to perform services on its behalf including but not limited to Professional Services, Support Services, and/or provide software (each, a "Subcontractor").
CentralSquare shall be fully responsible for the acts of all subcontractors to the same extent it is responsible for the acts of its own employees. All Subcontractor’s needing to be CJIS compliant will comply with Section 6.3.
23. E ntire Agreement . This Agreement, and any Exhibits specifically incorporated therein by reference, constitute the entire agreement between the Parties with respect to the subject matter. These documents supersede and merge all previous and contemporaneous proposals of sale, communications, representations, understandings and agreements, whether oral or written, between the Parties with respect to the subject hereof.
24. Ame
ndment . Either Party may, at any time during the term, request in writing changes to this agreement. The Parties shall evaluate and, if agreed, implement all such requested changes. No requested changes will be effective unless and until memorialized in either a CentralSquare issued add-on quote signed by Customer, or a written change order or amendment to this Agreement signed by both Parties.
25. No Third -Party Beneficiaries. This Agreement is for the sole benefit of the Parties and their respective successors and permitted assigns and nothing herein, express or implied, is intended to or shall confer on any other person any legal or equitable right, benefit, or remedy of any nature under or by reason of this Agreement.
26. Counterparts. This Agreement, and any amendments hereto, may be executed in several counterparts, each of which when so executed shall be deemed to be an original, and such counterparts shall constitute one and the same instrument. The Agreemen t (and any amendments) shall be considered properly executed by a Party if executed by that Party and transmitted by facsimile or other electronic means, such as DocuSign, Tagged Image Format Files (TIFF), or Portable Document Format (PDF).
27. M aterial Adverse Change. If any law, regulation, applicable standard, process, OEM requirement is changed or comes into force after the Effective Date, including but not limited to PCI standards or Americans with Disabilities Act compliance (collectiv ely, a “Material Adverse Change”), which is not explicitly addressed within this Agreement and results in significant extra costs for either Party in relation to the performance of this Agreement, both Parties shall promptly meet, discuss in good faith, and agree upon reducing the technical, operational, and/or commercial impact of such Material Adverse Change.
28. C
ooperative Purchases. This Agreement may be used by Customer Affiliates. CentralSquare agrees to offer similar services to other Affiliates under the same terms and conditions as stated herein except that the Fees may be negotiated between CentralSquare and other Affiliates based on the specific revenue expectations, agency reimbursed costs, and other Affiliate requirements. The Customer will in no way whatsoever incur any liability in relation to specifications, delivery, payment, or any other aspect of purchases by such Affiliates. CentralSquare and the Affiliate will enter into any such arrangement with an amendment to this Agreement.
29. C alifornia Law. This Agreement shall be interpreted, construed, and governed both as to validity and to performance of the Parties in accordance with the laws of the State of California. Legal actions concerning any dispute, claim, or matter arising out of or in relation to this Agreement shall be instituted in the Superior Court of the County of San Bernardino, State of California, or any other appropriate court in such county, and Consultant covenants and agrees to submit to the personal jurisdiction of such court in the event of such action. In the event of litigation in a U.S. District Court, venue shall lie exclusively in the Central District of California, Eastern Division.
30. O rder of Precedence.
30.1. In the event of any conflict or inconsistency between this Agreement, the Exhibits, or any purchase order, then the following priority shall prevail:
30.1.1. The main body of this Agreement and any associated amendments, statements of work (including Exhibit 5 (Statement of Work)), or change orders and then the attached Exhibits to this Agreement in the order in which they appear.
30.2. Customer’s purchase terms and conditions or CentralSquare’s sales terms and conditions are not applicable and shall have no force or effect, whether referenced in any document in relation to this Agreement.
30.3. Incorporated Exhibits to this Agreement:
Exhibit 1: Solution(s) and Services Fee Schedule
Exhibit 2: Maintenance & Support
Exhibit 3: CentralSquare Access Management Policy
Exhibit 4: Certificate of Insurance (Evidence of Coverage) Exhibit 5: Statement of Work
Exhibit 6: Service Level Commitments
EXHIBIT 1
Solution(s) and Services Fee Schedule
SOFTWARE
CAD
PRODUCT NAME QUANTITY UNIT PRICE DISCOUNT TOTAL
1. Enterprise CAD Archive Server
Software (OP) Annual Subscription
Fee
1 1,100.00 - 165.00 935.00
2. Enterprise CAD Disaster
Recovery System (OP) Annual
Subscription Fee
1 2,500.00 - 375.00 2,125.00
3. Enterprise CAD GISLink Utility
Position (OP) Annual
Subscription Fee
2 2,200.00 - 660.00 3,740.00
4. Enterprise CAD Mapping (OP)
Annual Subscription Fee
15 200.00 - 450.00 2,550.00
5. Enterprise CAD Mapping Test or
Training (OP) Annual Subscription
Fee
1 200.00 - 30.00 170.00
6. Enterprise CAD Position (OP)
Annual Subscription Fee
15 4,300.00 - 9,675.00 54,825.00
7. Enterprise CAD Routing Server -
Disaster Recovery (OP) Annual
Subscription Fee
1 1,300.00 - 195.00 1,105.00
8. Enterprise CAD Routing Server -
Test or Trn. System (OP) Annual
Subscription Fee
1 1,300.00 - 195.00 1,105.00
9. Enterprise CAD Routing Server (OP)
Annual Subscription Fee
1 8,100.00 - 1,215.00 6,885.00
10. Enterprise CAD Server Software
(OP) Annual Subscription Fee
1 13,000.00 - 1,950.00 11,050.00
11. Enterprise CAD Situational
Awareness Manager (SAM)
(OP) Annual Subscription Fee
1 4,300.00 - 645.00 3,655.00
12. Enterprise CAD Test or Training
System (OP) Annual Subscription
Fee
1 2,500.00 - 375.00 2,125.00
13. NCIC/State Query Position for
Enterprise CAD (OP) Annual
Subscription Fee
15 200.00 - 450.00 2,550.00
CAD Software Subtotal 109,200.00 USD
CAD Software Discount - 16,380.00 USD
CAD Software Total 92,820.00 USD
CRIMEVIEW
PRODUCT NAME QUANTITY UNIT PRICE DISCOUNT TOTAL
14. Crimemapping.com Annual
Subscription Fee
1 2,400.00 - 449.75 1,950.25
15. CrimeView Analytics: Informative
(3 years data) CST System
Subscription
1 3,350.00 - 502.50 2,847.50
16. CrimeView Analytics: Standard (3
years data) CST System
Subscription
1 3,125.00 - 468.75 2,656.25
CrimeView Software Subtotal 8,875.00 USD
CrimeView Software Discount - 1,421.00 USD
CrimeView Software Total 7,454.00 USD
INTERFACES
PRODUCT NAME QUANTITY UNIT PRICE DISCOUNT TOTAL
17. CentralSquare Message Switch (OP)
Annual Subscription Fee
1 9,500.00 - 1,425.00 8,075.00
18. CentralSquare Message Switch
Additional Provider (OP) Annual
Subscription Fee - Connection to
San Bernadino
1 3,200.00 - 480.00 2,720.00
19. CentralSquare Message Switch
Additional Provider (OP) Annual
Subscription Fee - ART for
Legacy RMS Data
1 3,200.00 - 480.00 2,720.00
20. CentralSquare Message Switch
Additional Transaction (OP) Annual
Subscription Fee - ART
for Legacy RMS Data
1 1,500.00 - 225.00 1,275.00
21. Enterprise CAD API - Customer (OP)
Annual Subscription Fee
1 2,200.00 - 330.00 1,870.00
22. Enterprise CAD ASAP Interface
Annual Subscription (OP) Annual
Subscription Fee
1 5,500.00 - 825.00 4,675.00
23. Enterprise CAD Axon Evidence.com
Data Extract (OP) Annual
Subscription Fee - Axon
Body Worn Cameras, Auto
Tagging
1 4,700.00 - 705.00 3,995.00
24. Enterprise CAD RapidSOS
Interface (OP) Annual Subscription
Fee
1 5,400.00 - 810.00 4,590.00
25. Enterprise Common Identity
Management (CIM) (OP) Annual
Subscription Fee
1 0.00 0.00
26. Standard ANI/ALI Interface (OP)
Annual Subscription Fee
1 3,900.00 - 585.00 3,315.00
27. Standard Axon Evidence.com
Integration (OP) Annual
Subscription Fee
1 4,100.00 - 615.00 3,485.00
28. Standard Crash Publisher (OP) Annual
Subscription Fee
1 4,100.00 - 615.00 3,485.00
29. Standard CrimeTracer Publisher
(OP) Annual Subscription Fee -
Coplink
1 4,100.00 - 615.00 3,485.00
30. Standard Crossroads Citation
Importer - California (OP) Annual
Subscription Fee
1 4,100.00 - 615.00 3,485.00
31. Standard Crossroads Crash
Importer - California (OP)
Annual Subscription Fee
1 4,100.00 - 615.00 3,485.00
32. Standard LexisNexis DORS
Incident Importer (OP) Annual
Subscription Fee - Coplogic
1 4,100.00 - 615.00 3,485.00
33. Standard LInX Publisher (OP)
Annual Subscription Fee
1 5,500.00 - 825.00 4,675.00
34. Standard Multi-Module Publisher
(OP) Annual Subscription Fee -
LexisNexis AVCC
1 4,100.00 - 615.00 3,485.00
Interfaces Software Subtotal 73,300.00 USD
Interfaces Software Discount - 10,995.00 USD
Interfaces Software Total 62,305.00 USD
MOBILE
PRODUCT NAME QUANTITY UNIT PRICE DISCOUNT TOTAL
35. Enterprise Mobile Base Position
w/ CJIS/NCIC Forms (OP)
Annual Subscription Fee
95 400.00 - 5,700.00 32,300.00
36. Enterprise Mobile Disaster
Recovery System (OP) Annual
Subscription Fee
1 2,300.00 - 345.00 1,955.00
37. Enterprise Mobile Mapping (OP)
Annual Subscription Fee
250 100.00 - 3,750.00 21,250.00
38. Enterprise Mobile Mapping Test
or Training (OP) Annual
Subscription Fee
1 100.00 - 15.00 85.00
39. Enterprise Mobile Server
Software (OP) Annual
Subscription Fee
1 19,400.00 - 2,910.00 16,490.00
40. Enterprise Mobile Test or
Training System (OP) Annual
Subscription Fee
1 2,300.00 - 345.00 1,955.00
41. Enterprise Mobile X Position (OP)
Annual Subscription Fee
155 200.00 - 4,650.00 26,350.00
Mobile Software Subtotal 118,100.00 USD
Mobile Software Discount - 17,715.00 USD
Mobile Software Total 100,385.00 USD
RMS
PRODUCT NAME QUANTITY UNIT PRICE DISCOUNT TOTAL
42. Enterprise RMS Accident (OP)
Annual Subscription Fee
1 5,600.00 - 840.00 4,760.00
43. Enterprise RMS Concurrent
User License (OP) Annual
Subscription Fee
65 600.00 - 5,850.00 33,150.00
44. Enterprise RMS Disaster Recovery
System (OP) Annual
Subscription Fee
1 1,700.00 - 255.00 1,445.00
45. Enterprise RMS Evidence and
Barcoding (OP) Annual Subscription
Fee
1 5,600.00 - 840.00 4,760.00
46. Enterprise RMS GIS (With CAD)
(OP) Annual Subscription Fee
1 0.00 0.00
47. Enterprise RMS NIBRS Module (OP)
Annual Subscription
1 10,800.00 - 1,620.00 9,180.00
48. Enterprise RMS Reporting Server
License (OP) Annual Subscription
Fee
1 1,100.00 - 165.00 935.00
49. Enterprise RMS Server Software
(OP) Annual Subscription Fee
1 21,600.00 - 3,240.00 18,360.00
50. Enterprise RMS Test or Training
System (OP) Annual Subscription
Fee
1 1,700.00 - 255.00 1,445.00
51. NCIC/State Software Enterprise
RMS Concurrent User (OP) Annual
Subscription Fee
7 200.00 - 210.00 1,190.00
RMS Software Subtotal 88,500.00 USD
RMS Software Discount - 13,275.00 USD
RMS Software Total 75,225.00 USD
UNIFY
PRODUCT NAME QUANTITY UNIT PRICE DISCOUNT TOTAL
52. CAD-to-CAD Unify (Cloud)
Annual Subscription Fee
1 29,000.00 - 4,350.00 24,650.00
Unify Software Subtotal 29,000.00 USD
Unify Software Discount - 4,350.00 USD
Unify Software Total 24,650.00 USD
SOFTWARE SUMMARY
Software Subtotal
426,975.00 USD
Software Discount - 64,136.00 USD
Software Total 362,839.00 USD
SERVICES
DATA CONVERSION FUNDS
DESCRIPTION TOTAL
1. Additional White Box ART Service Funds- Fixed Fee 200,000.00
Data Conversion Funds Services Total 200,000.00 USD
ENGAGE CONFERENCE REGISTRATIONS
DESCRIPTION TOTAL
2. CST Annual User Conference - Prepaid Registration Fee (per attendee) 9,192.00
Engage Conference Registrations Services Total 9,192.00 USD
SERVICES
DESCRIPTION TOTAL
3. Public Safety Consulting Services - Fixed Fee 172,380.00
4. Public Safety Data Conversion Services - Fixed Fee 49,335.00
5. Public Safety Development Services - Fixed Fee 1,560.00
6. Public Safety GIS/Analytics Services - Fixed Fee 59,280.00
7. Public Safety Project Management Services - Fixed Fee 110,565.00
8. Public Safety Technical Services - Fixed Fee 208,650.00
9. Public Safety Training Services - Fixed Fee 30,420.00
10. Public Safety Travel & Living Expenses Estimate 89,700.00
11. White Box ART Service - Fixed Fee 49,244.00
12. White Box Implementation Services - Fixed Fee 55,016.00
Services Services Subtotal 826,150.00 USD
Services Services Discount - 81,981.90 USD
Services Services Total 744,168.10 USD
UNIFY
DESCRIPTION TOTAL
13. Public Safety Consulting Services - Fixed Fee 7,800.00
14. Public Safety Development Services - Fixed Fee 975.00
15. Public Safety Project Management Services - Fixed Fee 8,190.00
16. Public Safety Technical Services - Fixed Fee 8,190.00
17. Public Safety Training Services - Fixed Fee 3,120.00
Unify Services Subtotal 28,275.00 USD
Unify Services Discount - 3,675.75 USD
Unify Services Total 24,599.25 USD
SERVICES SUMMARY
Services Subtotal 1,063,617.00 USD
Services Discount - 85,657.65 USD
Services Total 977,959.35 USD
SUMMARY
Software Subtotal
426,975.00 USD
Services Subtotal
1,063,617.00 USD
Subtotal
1,490,592.00 USD
CST-2024-101804
Discount - 149,793.65 USD
Total
1,340,798.35 USD
WHAT ARE THE RECURRING FEES?
TYPE AMOUNT
FIRST YEAR MAINTENANCE TOTAL 0.00
FIRST YEAR SUBSCRIPTION TOTAL 362,839.00
FIRST YEAR RECURRING SERVICES TOTAL 9,192.00
The amount totals for Maintenance and/or Subscription on this quote include only the first year of software use and maintenance.
CST-2024-101804
Payment Terms:
Subscriptions:
- If applicable, Annual Subscription Fees are due on the Delivery Date, and annually thereafter on the anniversary of the Delivery Date.
- The CST Annual User Conference fee shall be due on the first Delivery Date of software, and annually thereafter on the anniversary of the first Delivery Date of Software. - Annual Subscription Fees shall increase by 5% each year beginning on year 6.
Services:
Payment Schedule for all services excluding Unify:
Implementation Services
20% Due on Effective Date
15% Due at completion of CAD and RMS system orientation per SOW sections 4.4.2 and 4.6.2 10% Due at interface completion per SOW sections 4.3.1 and 4.3.2 10% Due at completion and delivery of data conversion, evidenced by final sign-off per SOW sections 16.1.3 Final Sign Off and 16.2.1 Deliver Final Converted Data 10% Due at administrative training completion per SOW section 4.6.5 #3 and Enterprise System Admin Training in SOW Appendix Y
10% Due at completion of End User CAD & RMS Trainings as outlined in SOW Appendix Y 10% Due at Go Live per SOW section 6.1.1 d
15% Due at final acceptance per SOW section 7.1.1 e
Payment Schedule for Unify services:
30% Due on Effective Date
20% Due at Project Kickoff
15% Due at completion of Testing
30% Due at Go Live
5% Due at completion of Reliability Period
- If applicable, non-fixed fee professional services shall be due as incurred on a time and materials basis. Non-fixed fee professional services are not included in the percentages outlined in the above Payment Schedule. - If applicable, non-fixed fee travel expenses shall be due as incurred, invoiced monthly for the travel expenses of the preceding month. Non-fixed fee travel expenses are not included in the percentages outlined in the above Payment Schedule.
- If applicable, Fixed Fee travel expenses are included in the percentages outlined in the above Payment Schedule. - The CST Annual User Conference fee is not included in the percentages outlined in the above Payment Schedule.
The CST Annual User Conference fee shall be due on the first Delivery Date of software, and annually thereafter on the anniversary of the first Delivery Date of Software. -
Hardware:
- If applicable, Non-subscription Hardware Fees are due on the Effective Date.
Licenses:
- If applicable, License Fees are due on the Delivery Date.
Support & Maintenance
- If applicable, Support & Maintenance Fees are due annually, starting prior to the first anniversary of the Delivery Date and annually thereafter.
CST-2024-101804
- Annual Software Maintenance Fees shall increase by 5% each year. - If applicable, legacy support and maintenance shall be due until the Delivery Date of the applicable replacement software. Any unused pre-paid support and maintenance shall be credited as a pro-rated amount towards the next applicable subscription software invoice due under this Agreement, or future invoice.
Third Party:
- If applicable, Third-Party Software Fees are due on the Effective Date. Third-Party software subscriptions and/or support fees shall be due annually thereafter on the anniversary of the Effective Date. Third-Party Software fees are subject to increase each year.
- If applicable, Third-Party Services shall be due 50% at Effective Date, 25% at completion of 1st End User Training Session, and 25% at Go Live.
Invoice Terms:
CentralSquare shall provide an invoice for the items in the schedule above no less than thirty (30) days prior to the due date.
ANCILLARY FEES
a. Customer is responsible for paying all taxes relating to this Agreement. Applicable tax amounts (if any) are not included in the fees set forth in this Agreement. If Customer is exempt from the payment of any such taxes, Customer must provide CentralSquare valid proof of exemption; otherwise, CentralSquare will invoice Customer and Customer will pay to CentralSquare all such tax amounts.
b. To the extent allowable by law, if Customer fails to make any payment when due, then CentralSquare may charge interest on the past due amount at the rate of 1.5% per month calculated daily and compounded monthly, or, if lower, the highest rate permitted under applicable law; and if such failure continues for 90 days following written notice thereof, CentralSquare may suspend performance or access until past due amounts have been paid.
CST-2024-101804
EXHIBIT 2
Maintenance & Support
This Maintenance & Support Exhibit describes support and maintenance relating to technical support that CentralSquare will provide to Customer during the Term of the Agreement.
1. Product Updates and Releases
1.1. Software Version. “Software Version” means the base or core version of the Software that contains significant new features and significant fixes and is available to the Customer. Software Versions may occur as the Software architecture changes or as new technologies are developed. The nomenclature used for updates and upgrades consists of major, minor, build, and fix and these correspond to the following digit locations of a release, a,b,c,d. An example of which would be 7.4.1.3, where the 7 refers to the major release, the 4 refers to the minor release, the 1 refers to the build, and the 3 refers to a fix. All Software Versions are provided and included as part of this Agreement.
1.2. U
pdates. From time to time CentralSquare may develop permanent fixes or solutions to known problems or bugs in the Software and incorporate them in a formal “Update” to the Software. If Customer is receiving technical support from CentralSquare on the general release date for an Update, CentralSquare will provide the Customer with the Update and related Documentation at no extra charge. Updates for custom configurations will be agreed upon by the Parties and outlined in a Statement of Work or Change Order.
1.3. Releases. Customer shall agree to install and/or use any New or Major Release within one year of being made available by CentralSquare to avoid or mitigate a performance problem, ineligibility for Support and Maintenance Services or infringement claim. All modifications, revisions and updates to the Software shall be furnished by means of new Releases of the Software and shall be accompanied by updates to the Documentation whenever CentralSquare determines, in its sole discretion, that such updates are necessary.
2. Support
2.1. CentralSquare shall provide to Customer support via toll-free phone number 833-278-7877 or via the CentralSquare Support Portal. CentralSquare shall provide to Customer, commercially reasonable efforts in solving errors reported by the Customer as well as making available an online support portal. Customer shall provide to CentralSquare reasonably detailed documentation and explanation, together with underlying data, to substantiate errors and to assist CentralSquare in its efforts to diagnose, reproduce and correct the error. Should either Party not be able to locate the error root cause and Customer and CentralSquare agree that on- site services are necessary to diagnose or resolve the problem CentralSquare shall provide a travel estimate and estimated hours in order to diagnose the reported error.
2.2. If after traveling onsite to diagnose a reported error and such reported error did not, in fact, exist or was not attributable to a defect in the Software provided by CentralSquare or an act or omission of CentralSquare, then Customer shall pay for CentralSquare's investigation, travel, and related services in accordance with provided estimate. Customer must provide CentralSquare with such facilities, equipment and support as are reasonably necessary for CentralSquare to perform its obligations under this Exhibit, including remote access in accordance with the Remote Access Policy.
3. Online Support Portal
Online support is available via https://support.centralsquare.com/s/contact -us, offering Customer the ability to resolve its own problems with access to CentralSquare’s most current information. Customer will need to enter its designated username and password to gain access to the technical support areas on CentralSquare’s website. CentralSquare’s technical support areas allow Customer to: (i) search an up-to -date knowledge base of technical support information, technical tips, and featured functions; and (ii) access answers to frequently asked questions (FAQ).
4. E xclusions from Technical Support Services
CentralSquare shall have no support obligations to provide Support or Maintenance for Solutions that are not kept current to one version prior to the then current version of the Solution. CentralSquare shall have no support obligations with respect to any third-party hardware or software product not licensed or sold to Customer by CentralSquare (“Nonqualified Product”). Customer shall be solely responsible for the compatibility and functioning of Nonqualified Products with the Software.
5. Customer Responsibilities
In connection with CentralSquare’s provision of technical support as described herein, Customer acknowledges that Customer has the responsibility to do each of the following:
5.1 Provide hardware, operating system and browser software that meets technical specifications, as well as a fast, stable, high-speed connection and remote connectivity for accessing the Solution.
5.2 Maintain any applicable computer system and associated peripheral equipment in good working order in accordance with the manufacturers’ specifications, and ensure that any problems reported to CentralSquare are not due to hardware malfunction;
5.3 For CentralSquare Solutions that are implemented on Customer Systems, maintain the designated operating system at the latest code revision level reasonably deemed necessary by CentralSquare for proper operation of the Software;
5.4 Supply CentralSquare with access to and use of all information and facilities reasonably determined to be necessary by CentralSquare to render the technical support described herein;
CST-2024-101804
5.5 Perform any test or procedures reasonably recommended by CentralSquare for the purpose of identifying and/or resolving any problems;
5.6 At all times follow routine operator procedures as specified in the Documentation or any error correction guidelines of CentralSquare posted on the CentralSquare website;
5.7 Customer shall remain solely responsible at all times for the safeguarding of Customer’s proprietary, confidential, and classified information contained within Customer Systems; and
5.8 Reasonably ensure that the Customer Systems are isolated and free from viruses and malicious code that could cause harm before requesting or receiving remote support assistance.
6. Priorities and Support Response Matrix
The following priority matrix relates to software errors covered by this Agreement. Causes secondary to non-covered causes - such as hardware, network, and third-party products - are not included in this priority matrix and are outside the scope of this Exhibit. CentralSquare will make commercially reasonable efforts to respond to Software incidents for live remote based production systems using the following guidelines:
Priority Issue Definition Response Time
Priority 1 –
Urgent
The software is completely down and will not
launch or function.
Priority 1 issues must be called in via 833-278-7877 and will be immediately answered and managed by the first
available representative.
Priority 2 –
Critical
A high -impact problem that disrupts the
customer’s operation but there is capacity to
remain productive and maintain necessary
operations.
Priority 2 issues must be called in via 833-278-7877 and will be immediately answered and managed by the first
available representative.
Priority 3 –
Non-Critical
A Software Error related to a user function which
does not negatively impact the User from the use
of the system. This includes system administrator
functions or restriction of user workflow but does
not significantly impact their job function.
Priority 3 issues called in via 833 -278-7877 will be
immediately answered and managed by the first
available representative.
Non-Critical Priority 3 issues may also be reported via Https://support.centralsquare.com/s/contact-us
Priority 4 –
Minor
Cosmetic or documentation errors, including
Customer technical questions or usability
questions.
Priority 4 issues called in via 833 -278-7877 will be
immediately answered and managed by the first
available representative.
Minor Priority 4 issues may also be reported via
Https://support.centralsquare.com/s/contact-us
7. Exceptions. CentralSquare shall not be responsible for failure to carry out its Support and Maintenance obligations under this Exhibit if the failure is caused by adverse impact due to:
7.1. defectiveness of the Customer’s Systems (including but not limited to environment, hardware or ancillary systems), or due to Customer corrupt, incomplete, or inaccurate data reported to the Solution, or documented defect.
7.2. denial of reasonable access to Customer’s System or premises preventing CentralSquare from addressing the issue.
7.3. material changes made to the usage of the Solution by Customer where CentralSquare has not agreed to such changes in advance and in writing or the modification or alteration, in any way, by Customer or its subcontractors, of communications links necessary to the proper performance of the Solution.
7.4. a Force Majeure event (as outlined in Section 12), or the negligence, intentional acts, or omissions of Customer or its agents.
8. Incident Resolution. Actual response times and resolutions may vary due to issue complexity and priority. For critical impact level and above, CentralSquare provides a continuous resolution effort until the issue is resolved. CentralSquare will make commercially reasonable efforts to resolve Software incidents for live remote based production systems using the following guidelines:
CST-2024-101804
Priority Resolution Process Resolution Time
Priority 1 – Urgent CentralSquare will provide a
procedural or configuration
workaround or a code correction that
allows the Customer to resume live
operations on the production
System.
CentralSquare will work continuously to provide the Customer with a solution that allows the Customer to resume live operations on the production system.
CentralSquare will either resolve the issue or provide a resolution plan as soon as possible and not later than twenty-four (24) hours after notification.
Priority 2 –
Critical
CentralSquare will provide a
procedural or configuration
workaround or a code correction that
allows the Customer to resume
normal operations on the production
System.
CentralSquare will work continuously to provide the Customer with a solution that allows the Customer to resume normal operations on the production System.
CentralSquare will either resolve the issue or provide a resolution plan as soon as possible and not later than thirty-six (36) hours after notification.
Priority 3 – Non –
Critical
CentralSquare will provide a
procedural or configuration
workaround that allows the Customer
to resolve the problem.
CentralSquare will work to provide the Customer with a
resolution which may include a workaround or code correction within a timeframe that takes into consideration the impact of the issue on the Customer and CentralSquare’s User base.
Priority 3 issues have priority scheduling in a subsequent release.
Priority 4 – Minor If CentralSquare determines that a
reported Minor Priority error
requires a code correction, such
issues will be addressed in a
subsequent release when
applicable.
CentralSquare will work to provide the Customer with a
resolution which may include a workaround or code correction in a future release of the software. Priority 4 issues have no defined resolution time.
9. Non-Production Environments. CentralSquare will make commercially reasonable efforts to provide fixes to non- production environment(s). Non-production environments are not included under the response or resolution tables provided in this Exhibit.
9.1. Maintenance. All non- production environment resolution processes will follow the structure and schedules outlined above for production environments.
9.2. I ncidents and service requests. Non-production environment incidents are considered priority 3 or 4, dictated by circumstances and will be prioritized and scheduled subordinate to production environment service requests.
10. Training. Outside the scope of training services purchased, if any, Customer is responsible for the training and organization of its staff in the operation of the Software.
11. Development Work. Software support and maintenance does not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Software, except such work as may be specifically purchased and outlined in the Agreement.
CentralSquare retains all intellectual property rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.
12. Technology Life Expectancy. Customer understands, acknowledges and agrees that the technology upon which the Hardware, Solution and Third-Party Software is based changes rapidly. Customer further acknowledges that CentralSquare will continue to improve the functionality and features of the Solution to improve legal compliance, accuracy, functionality and usability. As a result, CentralSquare does not represent or warrant that the Hardware, Solution and/or Third-Party Software provided to Customer under this Agreement or that the Customer Systems recommended by CentralSquare will function for an indefinite period of time. Rather, CentralSquare and Customer may, from time to time, analyze the functionality of the Hardware, Solution, Third-Party Software and Customer Systems in response to changes to determine whether Customer must upgrade the same. Customer upgrades may include without limitation, the installation of a new Release, additional disk storage and memory, and workstation and/or server upgrades. Customer upgrades may also include the installation and/or removal of Third-Party Software. Customer is solely responsible for all costs associated with future resources and upgrades as it relates to Hardware, the Solution, and Third-Party Software.
CST-2024-101804
EXHIBIT 3
CentralSquare Access Management Policy
In order to provide secure, federally compliant connections to agency systems CentralSquare Technologies (“CentralSquare”) requires BeyondTrust or SecureLink as the only approved methodology of connection. BeyondTrust and Securelink provide the necessary remote access in order to service and maintain CentralSquare products while adhering to the Federal Bureau of Investigations Criminal Justice Information Services requirements. Both solutions utilize two-factor authentication Federal Information Processing Standard Publication (“FIPS”) 140- 2 validated cryptographic modules and AES encryption in 256- bit strengths.
BeyondTrust and Securelink are addressed in turn via this Access Management Policy; Customers may choose which remote privileged access management solution will be utilized by CentralSquare.
BeyondTrust
The BeyondTrust remote support solution may be utilized via escorted session or a jump Customer. As for an escorted session, when an agency needs assistance from CentralSquare, the agency employee requesting assistance will receive verbal or email communication with a session key necessary to enable remote access. If a verbal key is provided, the user enters the session key after visiting https://securesupport.centralsquare.com .
Jump Customers are a Windows service that can be stopped/started to facilitate a support session. Connections made via jump Customer can be active or passive. An active jump Customer is always available. A passive connection is enabled for a specific purpose and then disabled when not used. Regardless of the option selected, CentralSquare’s support team will arrange a BeyondTrust session to establish the jump Customer.
The jump Customer resides on the agency side on the installed device, where an agency administrator can manage.
Instructions on how to enable/disable jump Customers can be provided upon request. A sample workflow of a passive jump Customer is provided below:
Should an agency require support from CentralSquare, a call would be placed and/or a support ticket opened in the portal on the CentralSquare customer support website. Before accessing the agency’s system and/or environment, the CentralSquare representati ve would send a notice of connection from the CentralSquare support portal instance. This notice can be sent to the individual at the agency that the CentralSquare representative is working with or other designated contacts as necessary. Upon receipt of the notice of connection, the agency personnel would enable the BeyondTrust jump Customer. The CentralSquare representative would then be admitted to the agency’s system and/or environment to perform the necessary task. Upon completion of the task, the CentralSquare representative sends a notice of disconnection from the CentralSquare support portal instance. Upon receipt of the notice of disconnection, the agency personnel would then disable the BeyondTrust jump Customer.
Securelink
Similar to BeyondTrust’s escorted session, Securelink may be utilized via “quick connect”. To enable a quick connect session when an agency needs assistance from CentralSquare, the Agency employee requesting assistance will enter a key code in order to connect for screen sharing on a device.
Similar to the jump Customer methodology, SecureLink may also be utilized via “gatekeeper”. The sample workflow description for a jump Customer provided above is substantially similar to the workflow for gatekeeper.
Summation
BeyondTrust and Securelink allow customers the ability to monitor connectivity to the customer’s network and maintain CJIS compliance while enabling CentralSquare to perform the necessary support functions.
CST-2024-101804
EXHIBIT 4
Certificate of Insurance (Evidence of Coverage)
CST-2024-101804
EXHIBIT 5
Statement of Work
(Attached)
f
Rialto Police, CA
____
Version 1.5
1000 Business Center Drive, Lake Mary, FL 32746
407.304.3235 l Fax: 407.304.3301 l www.centralsquare.com
STATEMENT OF WORK
PSJ - Enterprise
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. ©2024 CentralSquare Technologies, LLC Page ii
© 2024 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 perbusmission 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.
External Version - Document Control
Date Version Details/Changes Author
05.06.24 1.0 Initial Draft M. Harbin
05.17.24 1.1 Updated Interfaces J. Pitt
07.09.24 1.2 Updated Appendix Y, comments from review, added Appendix G, changed customer TCR approval from 5
to 10 business days. Changed other occurrences
from 5 days to 10 days as well.
M. Harbin
09.06.24 1.3 Updated customer redlines M. Harbin
09.09.24 1.4 Finished redlines, removed appendix G, changed timelines from 5 to 10 days on all due dates
M. Harbin
09.10.24 1.5 Finalized document and removed resolved
comments
M. Harbin
Internal Version - Document Control v1.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. ©2024 CentralSquare Technologies, LLC Page iii
Rialto Police, CA
Vision to Enterprise Migration
Table of Contents
RIALTO POLICE, CA .....................................................................................................................1 1 OVERVIEW ..................................................................................................................................1
1.1 STATEMENT OF WORK ......................................................................................................................... 1
1.2 PROJECT IMPLEMENTATION DEFINITIONS ................................................................................................ 1
1.3 GENERAL CUSTOMER RESPONSIBILITIES .................................................................................................. 4
1.4 PROJECT EXCLUSIONS .......................................................................................................................... 5 2 PROJECT CONTROLLING PROCESSES .............................................................................................7
2.1 OVERVIEW ......................................................................................................................................... 7
2.1.1. CentralSquare Responsibilities ................................................................................................ 8
2.1.2. Customer Responsibilities ........................................................................................................ 8
2.2 CHANGE ORDER PROCESS ..................................................................................................................... 8
2.2.1. CentralSquare Responsibilities ................................................................................................ 9
2.2.2. Customer Responsibilities ........................................................................................................ 9
2.3 PROJECT REPORTING ........................................................................................................................... 9
2.3.1. CentralSquare Responsibilities .............................................................................................. 10
2.3.2. Customer Responsibilities ...................................................................................................... 10
2.4 DOCUMENT REVIEW .......................................................................................................................... 10
2.4.1. Documents Subject to Customer Approval ............................................................................ 11
2.5 DOCUMENTS SUBJECT TO CUSTOMER REVIEW NOT REQUIRING APPROVAL ................................................. 11
2.5.1. CentralSquare Responsibilities .............................................................................................. 11
2.5.2. Customer Responsibilities ...................................................................................................... 11
2.6 THIRD PARTY MANAGEMENT .............................................................................................................. 12
2.6.1. CentralSquare Responsibilities .............................................................................................. 12
2.6.2. Customer Responsibilities ...................................................................................................... 12 3 PROJECT INITIATION AND PLANNING ......................................................................................... 13
3.1 OVERVIEW ....................................................................................................................................... 13
3.1.1. CentralSquare Responsibilities .............................................................................................. 13
3.1.2. Customer Responsibilities ...................................................................................................... 14
3.2 PROJECT KICK OFF ............................................................................................................................. 14
3.2.1. The CentralSquare Execution Process ................................................................................... 14
3.2.2. CentralSquare Responsibilities .............................................................................................. 14
3.2.3. Customer Responsibilities ...................................................................................................... 15 4 PROJECT EXECUTION ................................................................................................................. 16
4.1 OVERVIEW ....................................................................................................................................... 16
4.2 SYSTEM INSTALLATION ....................................................................................................................... 16
4.2.2. Cloud Virtual Provisioning ..................................................................................................... 17 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. ©2024 CentralSquare Technologies, LLC Page iv
Rialto Police, CA
Vision to Enterprise Migration
4.2.3. Review Hardware Specifications (On-Premise Components) ................................................ 18
4.2.4. Procurement\Allocation of Hardware and Third-party Software (On-Premise Components) 19 4.2.5. Basic Server Integration (On-Premise) .................................................................................. 20
4.2.6. System Installation (On-Premise) .......................................................................................... 23
4.3 IMPLEMENTATION OF ENTERPRISE SYSTEM INTERFACES ........................................................................... 27
4.3.1. Enterprise Standard Interfaces - Implementation Overview ................................................. 27
4.3.2. Enterprise Custom Interfaces - Implementation Overview ................................................... 30
4.4 IMPLEMENTATION OF CAD ENTERPRISE ................................................................................................ 35
4.4.1. CAD Enterprise Implementation Process Overview ............................................................... 35
4.4.2. CAD Enterprise System Orientation ....................................................................................... 35
4.4.3. CAD Enterprise Base System Build ......................................................................................... 37
4.4.4. Geographical Information Services ....................................................................................... 38
4.4.5. CAD Enterprise Workshops .................................................................................................... 41
4.4.6. CAD Enterprise Functional Acceptance Testing (FAT) ........................................................... 42
4.4.7. CAD Enterprise Training ........................................................................................................ 44
4.5 IMPLEMENTATION OF MOBILE ENTERPRISE............................................................................................ 46
4.5.1. Implementation Process Overview ........................................................................................ 46
4.5.2. Mobile Enterprise Functional Testing .................................................................................... 47
4.5.3. Mobile Enterprise Training .................................................................................................... 49
4.6 IMPLEMENTATION OF RECORDS ENTERPRISE .......................................................................................... 50
4.6.1. Records Enterprise Implementation Process Overview ......................................................... 50
4.6.2. Records Enterprise System Orientation ................................................................................. 50
4.6.3. Records Enterprise Base System Build ................................................................................... 51
4.6.4. Geographical Information Services ....................................................................................... 53
4.6.5. Records Enterprise Workshops .............................................................................................. 53
4.6.6. Records Enterprise Functional Acceptance Testing ............................................................... 54
4.6.7. Records Enterprise Training .................................................................................................. 57
4.7 IMPLEMENTATION OF COMMON IDENTITY MANAGEMENT (CIM) ............................................................. 57
4.7.1. CIM Configuration ................................................................................................................. 58
4.8 IMPLEMENTATION OF CRIMEVIEW ANALYTICS ....................................................................................... 60
4.8.1. CrimeView Analytics Implementation Process Overview ...................................................... 60
4.8.2. Discovery ............................................................................................................................... 60
4.8.3. Code Mapping & Application Configuration ......................................................................... 61
4.8.4. Initial Demonstration, Consultation, and Content Preparation ............................................ 61
4.8.5. CrimeView Training ............................................................................................................... 62
4.8.6. System Review ....................................................................................................................... 62
4.8.7. CrimeView Analytics Acceptance .......................................................................................... 63
4.9 IMPLEMENTATION OF CRIMEMAPPING.COM .......................................................................................... 64
4.9.1. Crimemapping.com Implementation Overview .................................................................... 64
4.9.2. Discovery ............................................................................................................................... 64
4.9.3. Configuration......................................................................................................................... 64 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. ©2024 CentralSquare Technologies, LLC Page v
Rialto Police, CA
Vision to Enterprise Migration
4.9.4. System Review & Go-Live ...................................................................................................... 65
4.10 SYSTEM INTEGRATION TESTING ........................................................................................................... 66
4.10.1. CentralSquare Responsibilities .............................................................................................. 67
4.10.2. Customer Responsibilities ...................................................................................................... 67 5 SYSTEM AND SUBSYSTEM PRE GO-LIVE TASKS ........................................................................... 68
5.1 OVERVIEW ....................................................................................................................................... 68
5.1.1. CentralSquare Responsibilities .............................................................................................. 69
5.1.2. Customer Responsibilities ...................................................................................................... 69 6 SYSTEM AND SUBSYSTEM GO-LIVE ............................................................................................ 70
6.1 OVERVIEW ....................................................................................................................................... 70
6.1.1. CentralSquare Responsibilities .............................................................................................. 70
6.1.2. Customer Responsibilities ...................................................................................................... 70 7 RELIABILITY PERIOD ................................................................................................................... 72
7.1 OVERVIEW ....................................................................................................................................... 72
7.1.1. CentralSquare Responsibilities .............................................................................................. 73
7.1.2. Customer Responsibilities ...................................................................................................... 73 8 PROJECT CLOSURE ..................................................................................................................... 74
8.1 OVERVIEW ....................................................................................................................................... 74
8.1.1. CentralSquare Responsibilities .............................................................................................. 74
8.1.2. Customer Responsibilities ...................................................................................................... 74 9 APPENDIX A - CONTRACTED MODIFICATIONS TO STANDARD CENTRALSQUARE PRODUCTS ......... 75 10 APPENDIX B - STANDARD CENTRALSQUARE INTERFACES ............................................................ 76 11 APPENDIX C - CUSTOM CENTRALSQUARE INTERFACES ............................................................... 85 12 APPENDIX D - MESSAGE SWITCH ................................................................................................ 86 13 APPENDIX E - SUBCONTRACTOR STATEMENT OF WORK ........................................................... 100 14 APPENDIX J – CENTRALSQUARE CONNECTIVITY TO ENTERPRISE ON-PREMISE SYSTEMS ............ 101 15 APPENDIX Y – WORKSHOP AND TRAINING SUMMARY ............................................................ 102 16 APPENDIX Z – DATA CONVERSIONS.......................................................................................... 105
16.1 CENTRALSQUARE CAD ENTERPRISE DATA CONVERSION ........................................................................ 105
16.1.1. Data Conversion Overview .................................................................................................. 105
16.1.2. Data Conversion Modules ................................................................................................... 106
16.1.3. Data Conversion Process ..................................................................................................... 107
16.2 CENTRALSQUARE RECORDS ENTERPRISE DATA CONVERSION – WHITE BOX .............................................. 110
16.2.1. Property & Evidence Data Conversion ................................................................................. 110
16.2.2. White Box – ART Solution .................................................................................................... 115 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. ©2024 CentralSquare Technologies, LLC Page vi
Rialto Police, CA
Vision to Enterprise Migration
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 1
1 OVERVIEW
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 Rialto Police, CA (“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 and Subsystems specified in the Agreement (collectively the “Project”).
Statement(s) of Work for applicable CentralSquare Subcontractor(s) are presented in Appendix
E – Subcontractor(s) 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); User and Administrator Documentation and training materials.
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.2 Project Implementation Definitions
Unless otherwise defined herein, capitalized terms within this document have the meanings described in the Definitions section of the 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.
Agreement refers to the CentralSquare Solutions Agreement. 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.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 2
Change Order is a collective term for communicating and approving all changes in project scope.
Codefiles are the component fields within each product that define the data to be contained within each table.
Disaster Recovery (DR) is the process of preparing for and recovering from a disaster. An event that prevents a workload or system from fulfilling its business objectives in its primary deployed location is considered a disaster.
FBI CJIS Security Policy means the Federal Bureau of Investigations Criminal Justice Information System Security Policy. The essential premise of the CJIS Security Policy is to provide appropriate controls to protect the full lifecycle of criminal justice information (CJI), whether at rest or in transit. The CJIS Security Policy provides guidance for the creation, viewing, modification, transmission, dissemination, storage, and destruction of CJI.
FDD is an acronym for Functional Design Document, which is a document that will be developed by a Software Engineer for the purpose of documenting customer Interface requirements.
Functional Acceptance Test (FAT) is a test(s) of specific functionality of the Subsystems of the Enterprise System.
GIS is an acronym for Geographic Information System, which is a system for storing and manipulating geographical information on a computer.
Go-Live is defined as the event that occurs when the Customer first uses a Subsystem, an Interface or Modification in a live operational environment (i.e., production use). Hardware means any equipment, computer system, servers, storage devices, peripherals, and any other tangible assets purchased under this Agreement. Installation Service Request (ISR) documents servers required for the implementation and the servers’ Hardware/virtual specifications.
Interface is the integration of a third-party software with CentralSquare software.
Contracted deliverable interfaces are described in the
Appendix B – Standard
CentralSquare Interfaces, in Appendix C – Custom CentralSquare Interfaces, and the Agreement.
Modification means changes or additions from the standard version of the Software. The Modifications, if applicable, are described in Appendix A, Contracted Modifications to Standard CentralSquare Products. T he 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 customers; or as applicable, made available as a separate module or function, separately licensed and priced.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 3
Operational Scenario Document (OSD) is a document that provides an operational description of an Interface, capability, or feature within the applicable CentralSquare solution. OSD documents are of two types:
For standard Interfaces these documents are standard, published CentralSquare documents and are not specific to any Customer.
For customizations (custom Interfaces or custom Features) the OSD will provide a description in sufficient detail that both Customer and CentralSquare team mutually agree to the expected deliverable.
Post Go-Live means the event(s) that occurs after the Customer first uses a Subsystem, an Interface or Modification in a live operational environment (i.e., production use). Pre Go-Live means the event(s) that occurs before the Customer first uses a Subsystem, an Interface or Modification in a live operational environment (i.e., production use). 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.
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.
Project Schedule means the mutually agreed upon 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.
SME is an acronym for Subject Matter Expert, an individual with a deep understanding of a particular topic.
Subsystem means each of the applications described in the Statement of Work including its equipment, other Hardware, and software. In most cases, the Subsystem software will share equipment. Applicable Enterprise core applications, e.g. CAD Enterprise, Mobile Enterprise, Records Enterprise, Jail Enterprise are defined as Subsystems. System means collectively all Subsystem(s) (e.g. CAD, Mobile, Records, Jail) that make up the integrated computer system.
System Integration Test (SIT) is the scenario-based testing event to test the integration and end-to-end functionality of the system.
System Planning Guide provides system administrators and system planners with a single requirements reference.
Task Completion Reports (TCR) is a formal document presented to the Customer that acknowledges completion of a major task or event.
Work Hours:
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 4
Business hours are defined as Monday – Friday, 8:00am-5:00pm (local time) Default training hours are defined as:
Remote Training: Monday - Friday, between 8am-5pm (local time) based on the actual duration of the class.
On Site Training: Tuesday – Friday, between 7am-10pm (local time) based on the actual duration of the class.
Alternate training schedules (e.g., Monday class starts for classes that would normally start on a Tuesday, multiple classes per day, evening, and weekend classes) are subject to additional cost.
1.3 General Customer Responsibilities
In addition to those Customer responsibilities stated elsewhere in this SOW, Customer is responsible for the following:
a) Electrical facilities – cabling, network communications, telephone, other voice/data connections and peripherals for system workstations and mobiles for production and training use.
b) Providing information to CentralSquare staff on network infrastructure, including any firewalls within the overall network that the system will operate and necessary port access for the system to operate in accordance with CentralSquare documentation. c) The installation, configuration, maintenance (including patch management and upgrades of Microsoft software on Workstations and Mobiles.
d) Any Hardware and third-party software or services necessary for implementing the System that is not listed in the Agreement as a CentralSquare Deliverable (not listed as a line item in the Solution(s) and Services Fee Schedule of the Agreement). This includes workstations, server Hardware not included with managed server/hosted solutions, network equipment, telephone or TDD equipment, performance test software, Microsoft licenses, Hypervisor licenses, Disaster Recovery Software, and services required to extract legacy data and convert into acceptable data formats.
e) Configuration, maintenance, testing, and supporting the third-party systems that Customer operates and which will be interfaced with as a part of this project. This project includes the Contracted Interfaces listed in
Appendix B – Standard CentralSquare
Interfaces and Appendix – Custom CentralSquare Interfaces. f) Consoles, furniture, or fixtures as well as any modifications to install equipment used for Systems or Subsystems specified by the Agreement into existing consoles, furniture, vehicles, or existing facilities. Installation of Workstations into consoles, furniture, vehicles or like items, is the responsibility of Customer.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 5
g) Customer is responsible for providing remote connectivity to CentralSquare for the purpose of installation, configuration, testing, and troubleshooting of any CentralSquare applications at Customer site.
h) CentralSquare’s approved remote connectivity methods are described in Appendix J. i) Connect and configure any third-party Hardware (including but not limited to: Bar Code Scanners, Bar Code Printers, Biometric Fingerprint Scanners, Signature Pads, and dongles) to Customer workstations, if these services are not explicitly sold in the System Agreement.
j) Active participation of the appropriate personnel with the necessary background knowledge and availability in the Project implementation meetings and working sessions during the course of the Project. Examples of such implementation sessions are System Orientation, Validation and Readiness, FAT, Training, regular Project meetings, discussion regarding Interfaces, network planning and system installation planning. k) The provision of data as requested by CentralSquare. This information must be provided on a timely basis in order to meet the project timelines. This information will be provided in a format requested by CentralSquare staff in accordance with CentralSquare documentation.
l) If Onsite Training is purchased, provide a facility with the required computer and audio- visual equipment for training.
m) Provision of facilities and electrical power for CentralSquare staff while onsite. n) The project timeline will require a commitment by Customer staff to attend project meetings, attend training, and execute action items within the mutually agreed upon defined time parameters in the project schedule.
1.4 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, Subsystems, 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 Order Process, as described in the Project Management Plan.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 6
d) CentralSquare is not responsible for the deficiencies in Customer’s internal or Contracted network to support Enterprise Suite workstations\mobiles. 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 engaged in the context of standard or custom interfaces, unless the work is defined under a Sub-Agreement with CentralSquare within the scope of this Agreement.
i) CentralSquare is not responsible for the creation or modification of any Crystal Reports, SSRS Reports or other third-party reporting application. This includes changes to connection strings or the migration of custom reports.
j) CentralSquare is not responsible for submitting NIBRS data to the State. Customer assumes responsibility to take the necessary steps within the Subsystem to submit NIBRS data monthly to the State unless otherwise noted in the Agreement.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 7
2 PROJECT CONTROLLING PROCESSES
2.1 Overview
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 a Project Management Plan which includes the Communication Management, Risk Management, and Change Management plans.
As part of the Controlling Processes, CentralSquare utilizes a series of measurements and management reviews to mitigate project risks. 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.
As part of the 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.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 8
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.
2.1.1. CentralSquare Responsibilities
a) CentralSquare will prepare and submit TCRs for Customer’s signature upon completion of the applicable task.
b) TCRs that trigger a payment will include the payment amount in accordance with the Agreement payment schedule.
2.1.2. Customer Responsibilities
a) The Customer is responsible for reviewing and approving all TCRs within ten (10) business days from the time of receipt less any challenges to the validity of the report. b) In the event that the 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 Agreement or this SOW. Such notification from the Customer shall be provided to the CentralSquare Project Manager within ten (10) business days of receipt of the TCR.
2.2 Change Order 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 Order 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 Order process.
The type of documentation needed will depend on the nature and significance of the change.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 9
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.
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 of 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.
2.2.1. CentralSquare Responsibilities
a) CentralSquare will capture the necessary information required to prepare Change Order and submit to the Customer.
2.2.2. Customer Responsibilities
b) When applicable, Customer will identify the services or deliverables that will be subject to a Change Order, per the Agreement between both parties. c) When applicable, Customer will identify changes to application features or functionality, Interfaces, or any other Subsystems that will require a Change Order.
This process may also include participation in the requirements process. d) Customer will approve and process Change Orders in a timely manner.
2.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 Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 10
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 provide the following:
a) Bi-weekly status calls.
b) Monthly status report and schedule updates.
2.3.1. CentralSquare Responsibilities
a) Provide a written report of Project status once a month. b) Track issues and action items to closure.
c) Conduct status calls every two weeks.
d) Maintain an up-to-date Project Schedule.
2.3.2. Customer Responsibilities
a) Review the written report of Project status and provide feedback within ten (10) 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.
2.4 Document Review
In the course of the Project, CentralSquare will deliver several documents to the Customer for review. These documents will include but are not limited to the Functional Acceptance Test Procedures, Project Schedule, OSD, and training materials for the Project. Approved documents are returned to the CentralSquare Project Manager. All documents will be provided via electronic 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 the Customer with a copy.
Should the Customer find any document unacceptable, Customer must provide specific reasons in writing to the CentralSquare Project Manager. CentralSquare can then assess any Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 11
required corrective measures and make revisions or modifications to provide acceptable documents within a mutually satisfactory timeframe.
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 ten (10) business days.
2.4.1. Documents Subject to Customer Approval
a) Change Orders
b) Operational Scenario Documents (OSD)
c) Functional Acceptance Test Procedure documents
d) Task Completion Reports (TCR)
2.5 Documents Subject to Customer Review not Requiring Approval Note: The Project Schedule and any changes hereto are to be mutually agreed upon between Customer and CentralSquare.
a) Functional Design Documents (FDD)
b) Status Reports
c) Project Schedule
2.5.1. 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.
2.5.2. Customer Responsibilities
a) Review the documents presented and provide the appropriate information back to CentralSquare within ten (10) 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 ten (10) business days for requirements documents defined above. Unless unanticipated changes to the Project Schedule would warrant a shortened turn around.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 12
2.6 Third Party Management
CentralSquare will be responsible for the management of third parties that have been identified as Subcontractors within the Agreement.
As part of the Subcontractor agreement, all communications between those third parties and the 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, the Customer will be responsible for the management of third parties that CentralSquare is not responsible for. The 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 the Customer’s System.
2.6.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.
2.6.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.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 13
3 PROJECT INITIATION AND PLANNING
3.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 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. 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.
3.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 Operational Scenario Document (OSD), etc.).
c) Identify and engage the CentralSquare Project team responsible for carrying out Project Execution.
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.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 14
f) Prepare and submit the TCRs for Customer acceptance of the Project Management Plan as defined above.
g) Develop and submit invoice for payment due at execution of the Agreement.
3.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 ten (10) business days.
3.2 Project Kick Off
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:
3.2.1. The CentralSquare Execution Process
a) A high-level description of project deliverables.
b) Roles and responsibilities for the Project team members. c) A high-level review of the preliminary Project Schedule including projected Project milestones and checkpoints.
d) Describe the work that has been either completed, is in progress or is due to begin within the immediate future.
e) Review any project related questions from Customer’s team.
3.2.2. 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) Provide a project schedule prior to kickoff meeting. d) Conduct the kickoff meeting.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 15
3.2.3. 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-visual equipment including a projector(s), screen, and whiteboard.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 16
4 PROJECT EXECUTION
4.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. 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.
All installation and configuration of Hardware, as well as CentralSquare software upgrades for this project will be performed remotely.
Training is a structured program designed to equip the Customer’s staff with the necessary skills and knowledge for effective software utilization. The Customer has the option to record these training sessions, provided that a signed Confidentiality Agreement is submitted to the CentralSquare Project Manager. The responsibility for the management and storage of these recordings’ rests solely with the Customer.
4.2 System Installation
Overview: System installation is one of the early processes in the Project implementation phase and has a significant impact on and critical dependency on several key activities.
Cloud virtual provisioning will be the responsibility of CentralSquare. On-Premise Hardware provisioning is the responsibility of the Customer. Installation of CentralSquare software on on-premise Hardware is the responsibility of CentralSquare.
This implementation will be on-premise components for CAD, Mobile and RMS Enterprise.
Unify will be installed in Cloud.
4.2.1.1 Cloud Components:
The CentralSquare Cloud team will provision the CentralSquare software in the cloud. This will entail a planning meeting with the Customer /Network Administrator and other CentralSquare staff (Project Manager, Technical Services), configuration of the connection, advising on network communications, and configuring access to the provisioned system. CentralSquare will provide the needed DOJ documentation for the Cloud products.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 17
The administration services of the cloud environment are the responsibility of CentralSquare, including support, operation, and maintenance of the underlying infrastructure. Access to any resources by the Customer will not be allowed except through applications and programmatic connections.
It is preferred that connections between the Customer and the CentralSquare AWS environment be on a dedicated circuit that is not shared with general internet users on the Customer side. For most deployments, a business class internet circuit is sufficient when appliances on each end of the connection have 1Gb connections. The Customer will only be responsible for their side of the connection with CentralSquare maintaining the AWS side. Redundant Connections are highly recommended.
4.2.1.2 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 prerequisites document called an ISR (Installation Services Request) to convey specifications and guidelines for the Customer to create the virtual machines needed for software installation.
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.
4.2.2. Cloud Virtual Provisioning
The CentralSquare Cloud team will provision the CentralSquare software in the cloud. This will entail a planning meeting with the Customer System/Network Administrator and other CentralSquare staff (Project Manager, Technical Services), configuration of the connection, advising on network communications, and configuring access to the provisioned system.
4.2.2.1 CentralSquare Responsibilities
a) Host technical meeting with Customer network\systems administration staff. b) Provision connection to Customer’s end point in coordination with the Customer. c) Provide port, protocol information to Customer for firewall rules.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 18
d) Provide guidance on DNS forward lookup zones needed for interoperability between Customer networks and cloud deployment.
e) Provide guidance on routing needed from Customer networks to cloud environment.
f) Configure tunnel for all Customer workstation subnets. g) Provision cloud systems.
h) Provide URLs and any other paths for Customer connectivity. i) Perform Connectivity tests with Customer assistance at least one week prior to any workshops.
4.2.2.2 Customer Responsibilities
a) Attend the technical meeting with CentralSquare resources. b) Acquire ISP connections.
c) Provide an end point device.
d) Provide end point public IP address for the connection to CentralSquare cloud environment.
e) Work with CentralSquare technical staff to provision the connection. f) Open firewall as directed by CentralSquare technical staff. g) Implement DNS forward lookup zones for interoperability with cloud environment.
h) Provide routing rules to route traffic through the connection as advised by CentralSquare technical staff.
i) Identify subnets where workstations will connect to the cloud environment from. j) Perform connectivity tests, with CentralSquare assistance at least one week prior to any workshops.
4.2.3. Review Hardware Specifications (On-Premise Components)
The Review of Hardware specifications is a review of the requirements for any On-Premise Components, be they servers, workstations or peripherals. The Review process is intended to function as an informational exercise for the Customer for any On-Premise Hardware sizing.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 19
4.2.3.1 Customer Procured Server Hardware:
CentralSquare and Customer will review the Hardware specifications and third-party software components to ensure that the correct Hardware and third-party software components are procured. CentralSquare will provide Customer with a Hardware sizing document listing the Hardware and third-party software specifications required for this Project. CentralSquare will provide an overview of deployment recommendations for the CentralSquare Enterprise Suite, to the Customer.
CentralSquare will not reverse engineer third party Hardware quotes or Bills of Materials to certify specifications.
4.2.3.2 Workstation and Peripheral Hardware:
CentralSquare will review workstation and any peripheral specifications with the Customer.
4.2.3.3 CentralSquare Responsibilities
a) Provide Hardware Sizing\Third party-software documentation to Customer prior to the review meeting.
b) Provide System Planning Guide to Customer prior to the review meeting. c) Schedule and participate in review meeting.
4.2.3.4 Customer Responsibilities
a) Provide technical resources for the review meeting.
b) Review and understand Hardware and third-party software documentation.
4.2.4. Procurement\Allocation of Hardware and Third-party Software (On- Premise Components)
This task is for the net new procurement of Hardware and third-party software and equipment per the specifications provided by CentralSquare for the On-Premise components. If there is no net new Hardware purchase associated with the Agreement, either by CentralSquare or the Customer, this task represents the allocation of existing resources for On-Premise components by the Customer.
4.2.4.1 CentralSquare Responsibilities
a) None
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 20
4.2.4.2 Customer Responsibilities
a) The Customer is responsible for the procurement of Hardware and third-party software based on the specifications from the Hardware and third-party software review.
4.2.5. Basic Server Integration (On-Premise)
Basic server integration includes placing the servers in the racks, creating the virtual environment, provisioning virtual machines, joining them to the existing domain, and establishing remote connectivity capability via the CentralSquare remote support solution for authorized CentralSquare personnel to perform configuration.
These activities will be coordinated between CentralSquare and Customer IT staff.
Guidance will be provided by way of a technical kickoff meeting with CentralSquare’s Technical Services Installation team and with the use of the ISR (Installation Services Request) process which organizes the information into CentralSquare’s preferred format.
To begin the software installation phase CentralSquare must have Customer-authorized remote connectivity to the servers, documentation of server names, IP addresses, Administrator Account Information (Username, Password), Services Account Information, and the location of 3
rd Party Software media (such as SQL).
If the connectivity, servers, server details, accounts and media are not ready two weeks prior to the scheduled installation, the Project may need to be rescheduled, which may have an impact on the overall Project timelines.
4.2.5.1 Customer Provided Basic Server Integration:
Customer will perform basic server integration for all On-Premise servers.
The site must be prepared and ready for the installation of CentralSquare software as detailed in CentralSquare’s documentation including the System Planning Guide no later than two (2) weeks prior to the scheduled Installation date. Delay in providing this information in its complete form will result in a delay in the Installation and the activities that follow installation of the System.
4.2.5.2 CentralSquare Responsibilities (Customer provided Basic Server Integration) a) Host a technical kickoff meeting to review the requirements for Installation including the Installation Service Request (ISR) Document. b) Distribute the Installation Service Request (ISR) document to Customer. c) Assist in Customer in completing the ISR.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 21
d) Review the completed ISR prior to the installation.
e) At least one (1) week prior to installation, a member of the CentralSquare Technical Services team will verify: (1) connectivity to Customer site via CentralSquare’s remote support solution, (2) connectivity to each of the servers, and (3) access to all required security accounts.
f) Prepare and submit a TCR for Customer review and approval upon completion of these activities.
4.2.5.3 Customer Responsibilities (Customer provided Basic Server Integration) a) Have appropriate subject matter experts attend the technical kickoff meeting. b) Provide the facility suitable to house Server Hardware and network infrastructure.
c) Have a member of Customer’s IT staff available while software/network configuration is being performed.
d) Provide all horizontal and vertical cable runs, pathways, coring, access points, floor cutting or drilling, and related tasks related to cable and equipment installation.
e) Provide all external Interface connection points, electrical power and other receptacles within manufacturer recommended distance of the equipment and all peripheral components.
f) Provide electrical facilities (e.g., outlets, generator, and other electrical infrastructure facilities required for this project, including necessary maintenance.
g) Provide cabling (e.g., power, network, Interface, and other electrical and data transmission lines) required for this project, including necessary maintenance. All lines will be clearly identified and tested.
h) Provide and install all data communication equipment, switches, routers, and other components necessary for system operation and maintenance, connection to remote sites to other systems, and to other agencies. i) Provide network/communications connections (e.g., LAN/WAN, commercial wireless, telephone, VPN, and other voice/data connections), and maintain ongoing network/communications charges associated with installation, operation or support of the proposed system including the establishment and maintenance of security accounts.
j) Configuration and/or programming of network routers, switches, and bridges – this includes providing information to CentralSquare staff on any firewalls within the overall network that the system will operate and necessary port access for the system to operate in accordance with CentralSquare documentation.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 22
k) Provide TCP/IP communications and connection to the server equipment for any existing networks, workstations, mobiles, and printers that are to have access to the CentralSquare applications.
l) Obtain all necessary IP addresses and schemes.
m) Perform basic server integration including, but not limited to:
i. Installation of servers in applicable racks.
ii. Connecting servers to network switches.
iii. When deploying a SAN, configure the applicable RAID configuration, create the LUN(s), and present them to the physical or virtual servers.
iv. Installation and configuration of the virtual environment. v. Creation of Virtual Machines
vi. Assign Server Names and IP Addresses to virtual machines vii. Install operating system software, perform Windows Genuine Advantage validation, and install all Windows Updates.
viii. Provision of Domain and/or Joining servers to an existing Customer domain.
ix. Enable and configure DNS, enable, and configure DHCP if required.
n) Installation of CentralSquare prerequisite software. o) Create and maintain any local, third party or public SSL certificates for the On- premise servers which require them, per CentralSquare documentation. p) Allow and establish CentralSquare access to all system administrative accounts on all servers running CentralSquare licensed Software. q) Gather all necessary configuration documentation which includes machine naming, IP addresses, Administrator Account information, Service(s) Account information, naming convention, and connectivity as prescribed in the Installation Services Request ISR) and return the ISR to CentralSquare. r) Provide CentralSquare with a high-level network diagram. The diagram should be provided prior to CentralSquare installation.
s) Install all workstations and peripheral equipment, including scanners, printers, barcode readers, etc.
t) Approve the applicable TCR.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 23
4.2.6. System Installation (On-Premise)
CentralSquare Technical Services Engineers will perform the CentralSquare software installation. These services will be performed remotely and include installation of the Contracted CentralSquare products as specified in the Basic Server Integration portion of the project.
These installation activities will be coordinated between CentralSquare and Customer.
CentralSquare will host a technical handoff meeting with the Customer to advise on ongoing maintenance of the on-premise system.
If Customer does not follow the processes and procedures detailed in the CentralSquare System Planning Guide and technical handoff and this results in a need for reinstallation of the Hardware or software, the reinstallation effort will be performed at additional cost to Customer
4.2.6.1 Prerequisites for this Task:
a) Completion of Basic Server Integration Task.
b) Completed ISR.
c) Completed High Level Network Diagram.
d) Provision and Testing of Remote Access and Server User Accounts. e) Location of SQL Installation Media and Keys.
f) Provision of SSL Certificates.
4.2.6.2 Customer Responsibilities
a) Allocate appropriate onsite Project personnel to support CentralSquare personnel during configuration tasks as necessary and designate a primary point of contact to be available to address and answer questions that arise during the installation of the baseline application software. Appropriate Customer personnel include the necessary IT personnel and database administrator(s) as needed during installation.
b) Customer is responsible for making the SQL media and license keys available to CentralSquare for installation.
c) Have appropriate subject matter experts (usually Customer IT) attend the technical handoff meeting.
d) Complete the configuration of workstations (after the installation of any contracted number of workstations by CentralSquare) using the Prerequisite Software Package and applicable Launch configurations.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 24
e) Put in place CentralSquare’s recommended backup procedures as outlined in the System Planning Guide and ensure backup procedures are consistently followed beginning at the completion of this task.
f) Install and configure virus scanning and other security software as outlined in the System Planning Guide.
g) After completion of the initial installation and configuration of System servers, Customer will be responsible for maintaining the System based on CentralSquare System Planning Guide, and the technical handoff meeting and associated document from CentralSquare Technical Services department. h) Review and approve the TCR from the technical handoff meeting.
4.2.6.3 CentralSquare Responsibilities
a) Install and configure Microsoft SQL to operate with each of the applicable CentralSquare product(s).
b) Install and configure the applicable CentralSquare system(s) on the designated servers and applicable environments as specified in the Agreement. c) Integrate on-premise components to cloud installed components. d) Provide verbal support to Customer with self-installation procedures for the workstations.
e) After completion of the initial installation and configuration of each major System (such as Records Enterprise servers), a member of Technical Services team provides a technical handoff meeting to the designated staff from Customer’s information Technology team via a conference call. The following major topics will be discussed during this technical handoff:
Proper procedures for performing System Backups:
i. File Structure – Inclusions and exclusions
ii. Databases
iii. Moving backups to media
iv. Procedures for refreshing test/training system (and related documentation) if applicable
v. Approved configuration and use of Virus Scan software vi. Approved procedure for application of Windows updates vii. System Upgrade process and procedures
viii. Support Website and CentralSquare list server access ix. Managing/Reviewing system logs (SQL and Event Logs) Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 25
f) Provide a Network Layout Diagram of the installed servers. g) Provide a list of network ports and protocols utilized for the purpose of securing the system.
h) Prepare and submit a TCR upon completion of the installation tasks and activities.
4.2.6.4 Disaster Recovery Provisioning (On-Premise)
Disaster Recovery Licensing per product is required for any on-premise Disaster recovery solution, whether it is implemented by CentralSquare, a third party, the Customer or any combination of these. The licensing is for the right to use the software in a Disaster Scenario.
Disaster Recovery is intended for core on-premise production system recovery and does not extend to replicated reporting systems or test\training systems.
Disaster Recovery is not High Availability. Disaster Recovery is a process intended to stand up the entire on-premise setup at another location for operational continuity, not migrate individual servers or services on an ad-hoc basis. Disaster Recovery does not address downtime concerns due to software updates of any kind. The Disaster Recovery solution may contain some elements which do utilize a clustered High Availability approach, as supported by the CentralSquare Enterprise Suite, and as contracted for.
Disaster Recovery is not a system intended to be used as backup software, point-in time snapshots, or for malware/ransomware recovery since the replication is an ongoing process.
In the event where there is a significant failure of the primary server infrastructure, the Disaster Recovery environment allows staff to connect to a Disaster Recovery System located at a remote location to continue operations. This scenario is particularly applicable in situations that involve power and/or network outages, facility failure, and lack of access to the primary server environment.
The synchronization between Primary and the Disaster Recovery server requires CentralSquare approved third-party Disaster Recovery Software product(s). If the license for this synchronization software is not explicitly listed in the Agreement (purchased through CentralSquare) the Customer is responsible for procurement of the required licenses for this software.
If contracted to provide the Disaster Recovery replication software directly or via a CentralSquare Subcontractor, CentralSquare and/or CentralSquare’s Subcontractor Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 26
will provide the software, install the software and provide Disaster Recovery software training and\or documentation.
If the Customer sources Disaster Recovery replication software, the Customer is responsible for providing the software, installation of the software, documenting the procedure and training any staff necessary for the failover operation.
In all cases, whether the replication software is contracted via CentralSquare and\or CentralSquare Subcontractor or provided by the Customer, CentralSquare Technical Services staff will be available for One (1) Failover and Failback operation as part of this engagement.
The Customer must ensure that trained personnel are available for failover/failback and that applicable documentation is carefully followed.
If the Failover and Failback operation is unsuccessful due to CentralSquare and/or Subcontractor misconfiguration or error, Failover and Failback testing will continue until there is a successful Failover and Failback operation. If the Failover and Failback operation is unsuccessful due to Customer configuration (including network issues between the sites, or between Customer software and the DR site), further tests with CentralSquare involvement will need to be contracted with a Change Order.
If the Customer’s preference is to have multiple Failover and Failback tests with CentralSquare involvement, this can also be accommodated with a Change Order.
All Failover and Failback tests are to take place in the pre-production environment. If a Post Go-Live Failover and Failback test is required, this will need to be specifically contracted for.
Additional Information on Disaster Recovery is available in the Enterprise System Planning Guide.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 27
4.3 Implementation of Enterprise System Interfaces
4.3.1. Enterprise Standard Interfaces - Implementation Overview Standard interfaces to be implemented (and designated environments) for this project are listed within the Agreement and Appendix B of this SOW.
Standard Interfaces may require certain work to be completed in the system prior to implementation. This may include code table configuration, system hierarchy, template design and the configuration of servers, certificates and integrations required for Interface operation. Standard Interface FDD documents will detail network, third party and other prerequisites for Interface operation.
Standard Interfaces are deployed in the pre-production environment (which becomes production at Go-Live).
Disaster Recovery Interfaces for on-premise systems are also licensed in the Agreement and listed in Appendix B
of this SOW.
The Disaster Recovery system for on-premise Systems will include licensed Disaster Recovery Interface configurations if the Interface Servers are replicated at a Virtual Machine level, with the assumption that no re-configuration needs to occur to either the CentralSquare or third-party end points as a result of a failover.
If the on-premise Disaster Recovery system contains separately configured, non- replicated, Interface servers then Interface configuration services will need to be included in the Agreement.
4.3.1.1 Standard Interfaces
Major Task Description
Schedule Standard Interfaces are replicated for Disaster Recovery with no end point configuration changes.
CentralSquare and Customer will conduct Interface implementation tasks as indicated in the approved Project Schedule.
Applicable Code Tables, configurations and Templates that must be built as part of the overall Project Schedule as a prerequisite for Interface deployment and/or testing will be detailed by the OSD.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 28
Functional Review Review of standard Interface functional specifications with CentralSquare, Customer’s subject matter expert (SME), and third-party vendor to review the Operational Scenario Document (OSD).
Installation and
Configuration
CentralSquare will install the Interface, configure and dry-run test the Interface.
Functional
Acceptance
Testing
CentralSquare will complete functional testing of the Interface with Customer and third party using a Functional Test document based solely on the OSD.
Customer notates the Functional Test document to indicate which tests passed or did not pass based on the OSD. Any exceptions are resolved and re-tested.
Sign Off Customer signs off on each Interface via a Task Completion Report (TCR) upon completion of Functional Test.
Go-Live The interfaces are brought into production during system Go-Live.
4.3.1.2 Enterprise Standard Interfaces - Roles and Responsibilities
4.3.1.2.1 CentralSquare Responsibilities
a) Review Interface OSD with Customer for each standard Interface. b) Prepare and submit a TCR to Customer documenting the delivery/review of the OSD.
c) Assist with detailing configuration options for the Interface. d) Install, configure and pre-test each Interface based on the agreed-upon configurations.
e) Assist Customer and third-party vendors to complete functional testing in accordance with Functional Test document. CentralSquare is not responsible for configuration of third-party systems.
f) Prepare and submit a TCR documenting completion of Functional Test including any exceptions.
g) Resolve Functional Test issues and re-run tests to confirm they have been resolved.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 29
4.3.1.2.2 Customer Responsibilities
a) Participate in the review of OSDs for each standard Interface. b) Provide the information that is necessary to complete the configuration options for each Interface.
c) Obtain the detailed documentation, schema, protocols, query specifications, sample files, and API access for each of the third-party applications that CentralSquare interfaces with and provide the documentation to CentralSquare. d) Act as the primary point of contact with third parties, including other vendors, state and/or local agencies that control products with which CentralSquare products will Interface with.
e) Ensure connectivity on the designated protocols and ports to or from third party or Customer-hosted end points.
f) Ensure design decisions and functional signoff decisions are made conclusively and in a timely fashion.
g) Provide a point of contact/administrator for each/all standard interfaces with knowledge and experience of the work and data flows.
h) Participate in the Functional Test with CentralSquare and third-party vendor and notate each test has passed, failed, or is not applicable. Validate data transferred to/from CentralSquare systems as part of the testing process of the Interface. i) Assist CentralSquare in documenting, testing, and resolving Functional Test exceptions.
j) Review and approve applicable TCRs.
Changes to the configuration of standard interfaces made by Customer may make the Interface non-supportable. As a result, troubleshooting efforts may be subject to additional cost.
Customer will arrange for third party vendor participation for systems that will be interfaced with to ensure successful configuration and testing for end-end data flow.
Customer is responsible for any services or software needed from third party systems to allow for interaction with the third-party system, or for connection to CentralSquare software in the absence of a third party API. CentralSquare is not responsible for cost associated for the API, any required third-party lab or certification testing, cost associated with required programming, custom work by third party vendors, or any license fees that may be required by third party vendors. No third-party Interface software will be installed on CentralSquare servers without the permission of CentralSquare.
Note: Any changes required to Records Enterprise templates required for standard Interface work is the responsibility of Customer.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 30
Note: Modifications requested by Customer to a standard Interface may incur additional cost and could result in project delays, since modifications to standard interfaces are only released with a major software version.
4.3.2. Enterprise Custom Interfaces - Implementation Overview Custom interfaces to be implemented for this project are listed within the Agreement and Appendix C
of this SOW.
Custom Interfaces may require certain work to be completed in the system prior to implementation. This may include code table configuration, system hierarchy, template design and the configuration of servers, certificates and integrations required for Interface operation. Custom Interface OSD documents will detail network, third party and other prerequisites for Interface operation.
Custom Interfaces are deployed in the pre-production environment (which becomes production at Go-Live). Interfaces are not deployed in test or training environments unless specified in the Agreement and Appendix C
of this SOW.
Disaster Recovery Interfaces for on-premise Systems are also licensed in the Agreement and listed in Appendix C
of this SOW.
The Disaster Recovery system for on-premise Systems will include licensed Disaster Recovery Interface configurations if the Interface Servers are replicated at a Virtual Machine level, with the assumption that no re-configuration needs to occur to either the CentralSquare or third-party end points as a result of a failover.
If the on-premise Disaster Recovery system contains separately configured, non- replicated, Interface servers then Interface configuration services will need to be included in the Agreement.
4.3.2.1 Custom Interfaces
Major Task Description
Schedule Custom Interfaces are replicated for Disaster Recovery with no end point configuration changes.
CentralSquare and Customer will conduct Interface implementation tasks as indicated in the approved Project Schedule.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 31
Applicable Code Tables, configurations and Templates that must be built as part of the overall Project Schedule as a prerequisite for Interface development and/or testing will be detailed by a CentralSquare Consultant or Software Engineer.
Functional Review Review of custom Interface functional specifications with CentralSquare, Customer’s subject matter expert (SME), and third-party vendor to develop the Operational Scenario Document (OSD).
Customer must provide relevant information regarding the operation of the Interface with relation to its operation as well as any interaction with external systems. This is essential for accurate development of the OSD.
Documentation Customer reviews and approves each OSD as a precursor to the start of Interface development. The approved OSDs will be used as a basis for development, configuration, and functional testing of each custom Interface.
Development,
Installation &
Configuration
After development concludes, CentralSquare will install and dry-run test each Interface.
Functional
Acceptance Testing
CentralSquare will complete functional testing of the Interface with Customer and third party using a Functional Test document based solely on the approved OSD.
Customer notates the Functional Test document to indicate which tests passed or did not pass based on the approved OSD. Any exceptions are resolved and re-tested.
Sign Off Customer signs off on each Interface via a Task Completion Report (TCR) upon completion of FAT.
Go-Live The interfaces are brought into production during system Go-Live.
4.3.2.2 Enterprise Custom Interfaces - Roles and Responsibilities
4.3.2.2.1 CentralSquare Responsibilities
a) Create and provide OSDs to Customer for each custom Interface.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 32
b) Prepare and submit a TCR to Customer, documenting Customer’s approval of each custom Interface OSD.
c) Using the approved OSDs, complete development of each custom Interface. d) Install, configure and pre-test each custom Interface. e) Develop Functional Test documents based on the approved OSDs. f) Provide Functional Test documents to Customer for use during the Functional Test of each Interface.
g) Assist Customer in conducting Functional Test in accordance with Functional Test documents.
h) Resolve and retest any Functional Test exceptions.
i) Prepare and submit a TCR to Customer, documenting completion of Functional Test for each Interface, including any Functional Test exceptions.
4.3.2.2.2 Customer Responsibilities
a) Provide the information that is necessary for development of the OSD for each custom Interface.
b) Obtain detailed documentation, schema, protocols, query specifications, sample files and API access for each of the third-party applications that CentralSquare interfaces with and provide the documentation to CentralSquare. c) Review and approve the TCRs for each OSD.
d) Engage the third-party vendors as requested by CentralSquare. e) Act as the primary point of contact with third parties including other vendors, state agencies, and local agencies that control products with which CentralSquare products are to Interface with.
f) Ensure connectivity on the designated protocols and ports to and from third party or Customer-hosted end points.
g) Ensure design decisions and functional signoff decisions are made conclusively and in a timely fashion.
h) Provide a point of contact for each Interface with knowledge and experience of the workflow and data.
i) Participate in the Functional Test of each custom Interface. Validate data transferred to or from CentralSquare systems as part of the Interface. j) Document Functional tests passed, or failed, and assist CentralSquare in providing details regarding any exceptions.
k) Assist in testing and verifying fixes for Functional Test exceptions. l) Review and approve applicable TCRs.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 33
Note: Any changes required to Records Enterprise templates required for custom Interface work is the responsibility of Customer.
Note: Incomplete or inaccurate information, or delayed OSD approval may have a cascading effect on the Project Schedule, and result in a significant delay in completion of the project.
Requirements changes for custom interfaces after approval of the OSD shall follow the Change Order Process and may be subject to additional cost and development time.
Changes may also have a cascading effect on the project schedule, and result in delays to completion of the project.
Customer is responsible for providing application programming Interface (API) documentation for the third-party system. The API must be compatible with the version of the third party software CentralSquare will b be interfacing with; the timeline for providing information must be concurrent with development of the OSD so any limitations associated with integration with the third-party applications can be taken into consideration. Customer is responsible for any services or software needed from third party systems required for integration with the third-party system. CentralSquare is not responsible for any cost associated for the API, any required third-party lab or certification testing, cost associated with required programming or custom work by a third-party vendor, or any license fees that may be required by the third-party vendor.
The scope of functionality for the custom Interface is limited to: 1) the capability of the CentralSquare system being interfaced with and 2) the application programming Interface (API) capabilities of the external system being interfaced.
Customer is responsible (when requested) to coordinate execution of a standard Non- Disclosure Agreement (NDA provided by CentralSquare) between third party vendors and CentralSquare. The NDA must be completed as a prerequisite to sharing technical or other information/documentation, and before testing of the Interface can commence.
Customer is responsible for coordinating the development of the vendor side of all interfaces to third party applications for interfaces for which the vendor is not a CentralSquare Subcontractor, based on the Agreement. CentralSquare is not responsible for the cost of any software, work, customization, coding, or testing that may be required to be performed by third party vendors associated with implementation of the custom Interface (unless the work is defined under a Sub-Agreement agreement with CentralSquare within the scope of the Agreement).
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 34
No third-party Interface software will be installed on CentralSquare servers without the permission of CentralSquare.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 35
4.4 Implementation of CAD Enterprise
CAD Enterprise 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.
4.4.1. CAD Enterprise Implementation Process Overview
Major Task Description
Workshops CentralSquare and Customer will conduct workshops as indicated in Appendix Y.
Base System Build After initial build by CentralSquare, Customer assumes ownership of building and maintaining Codefiles.
Functional
Acceptance Testing
Conducted prior to the start of End User Training.
Training As indicated in Appendix Y.
Go-Live The application is brought into production use.
4.4.2. CAD Enterprise System Orientation
Major Task Description
Overview Orientation includes a business process review of Customer’s current operation as well as discussion regarding key configuration options and assignments related to the Codefile build.
Includes an overview of software functionality.
Comprehensive discussion of workflow from initiation of incident through incident completion.
Determination of agency type setup; segmentation of operational processes including incidents, units, and call-taker/dispatcher roles and responsibilities.
Reporting requirements (geographic reporting segmentation, etc.).
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 36
Customer
Participants
CAD Administrators and core members of Customer implementation team who can address key points and make configuration decisions.
Participants should not exceed ten (10) per class.
Duration As noted in Appendix Y – Workshop and Training Summary.
Note: Customer’s provision of Codefile information is an early Project checkpoint. Remote sessions will be scheduled as a follow up to System Orientation, if applicable to guide Customer through the data collection process and entry.
4.4.2.1 CentralSquare Responsibilities
a) Schedule System Orientation in accordance with Customer’s availability and the Project Schedule.
b) Prepare and distribute meeting agendas and documents for Customer review or completion at least 2 weeks prior to each meeting.
c) Conduct meetings based on distributed agendas.
d) Send the System Module Setup (SMS) worksheet and other reference material to Customer and work with Customer to determine a mutually agreed timeframe for its completion.
e) Document and assign owners and due dates to action items and track to closure. f) Document any gaps between standard functionality of the System and functionality required by the Agreement for further analysis and discussion and/or facilitate the change control process. Customer-requested changes beyond the scope of the Agreement will be evaluated from a functional and timeline perspective during this phase, as well as for additional charges assessed to Customer.
g) Schedule/conduct remote sessions to guide Customer through Codefile data collection process.
h) Prepare and submit a TCR upon completion of relevant activities.
4.4.2.2 Customer Responsibilities
a) Ensure participation of key stakeholders and decision-makers in the System Orientation process.
b) Provide Subject Matter Experts to:
i. Explain current call flow and Customer structure and make decisions regarding any proposed changes in implementing the CAD Enterprise System.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 37
ii. Gather and provide the data elements used to build Codefiles to CentralSquare.
iii. Explain the Customer’s geopolitical/operational boundaries. This person (or persons) should be able to articulate the specific response requirements that will be built within CAD response plans.
iv. Become CAD super users, as well as a CAD Administrator who will be responsible for the ongoing maintenance of the CAD Codefiles and configuration.
v. Be responsible for translating the geopolitical/operational boundaries into data (ESRI shape files) suitable for use within CAD.
vi. Be responsible for the maintenance of street centerline data. vii. Provide information on technical Systems (Interfaces and hardware/network) or field-related functions (Mobile Enterprise or other mobile systems, station alerting and the like).
c) Return completed System Module Setup (SMS) worksheet within the mutually agreed timeframe.
d) Review and approve applicable TCRs.
4.4.3. CAD Enterprise Base System Build
Major Task Description
Overview Initial Codefile review and build by CentralSquare Consultant with active participation by Customer via periodic remote review sessions.
CentralSquare Consultant will configure the System hierarchy based on call flow and operational processes as defined during System Orientation.
Customer
Participants
CAD Administrators and core members of Customer implementation team who can address key points and make configuration decisions while participating in the Codefile building process.
Output CentralSquare Consultant completes the base Codefile entry to a level that allows for evaluation of call flow and incident management functions, including: call-taking layout, system hierarchy, incident numbering, Incident/Unit displays.
Validation via the Codefile building confirms completion of setup, limits the risk of rework, and ensures understanding of how information will translate for usage within CAD Enterprise.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 38
Some Codefiles that require local knowledge of the geography and physical location of business and high-risk areas of the community (such as response plans, premises, and caution note/hazard information) cannot be built by CentralSquare. Customer assumes responsibility for entering and geo- verifying some Codefile elements such as premises.
The CentralSquare Consultant will provide consultation services throughout the project.
Prerequisites Completion of CAD Enterprise System Orientation and receipt of requested Codefile data from Customer’s completed SMS worksheet.
4.4.3.1 CentralSquare Responsibilities
a) Monitor timely delivery, evaluate Codefiles submitted by Customer, and provide oversight with entry.
b) Complete preliminary Codefile build of Customer’s CAD Enterprise System as outlined in the Provisioning Guide. Codefile build will be entered based upon the applicable requirements provided by CentralSquare and responses from Customer.
c) Facilitate updates to the Provisioning Guide.
4.4.3.2 Customer Responsibilities
a) Provide timely input and updates to the SMS sheet to support Codefile building timelines.
b) Participate in the Codefile validation conference call. c) Continue building System Codefiles (those not built by CentralSquare).
4.4.4. Geographical Information Services
4.4.4.1 Data Evaluation
The CentralSquare GIS Analyst will perform a onetime evaluation of Customer- supplied GIS data layers to ensure they are formatted correctly for street-centerline display, address point usage, address functions, routing and Quickest Path Unit Recommendations, and CAD and Mobile map optimization. Upon completion of the analysis, the CentralSquare GIS Specialist will provide a report summarizing the findings.
Note: The one-time GIS data evaluation by the CentralSquare Analyst only applies to custom map conversion of Customer-supplied data. If the Customer purchases TomTom data, the one-time GIS data evaluation is not required. The Customer will Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 39
still need to provide the other required GIS data for the system, such as response areas and layers for the CAD and Mobile Maps.
4.4.4.1.1 CentralSquare Responsibilities
a) Evaluate Customer-supplied GIS data.
b) Provide and present a report summarizing the findings from GIS analysis services for CAD Enterprise.
c) Prepare and submit a TCR upon completion of relevant activities.
4.4.4.1.2 Customer Responsibilities
a) Provide the required GIS data in the required format, and per Project Schedule.
b) Based on the Analysis Report provided by CentralSquare, make requested changes to mapping data to meet CentralSquare’s GIS data requirements. c) Review and approve the appropriate TCR.
4.4.4.2 GIS Conversion and Mapping Configuration
A CentralSquare GIS Analyst will convert the GIS data into the CAD system and configure up to 10 standard GIS layers for viewing on CAD and Mobile Enterprise.
GISLink training will enable the Customer to create additional layers for use in CAD Enterprise and Mobile.
Standard layers are limited to the following:
a) Water line features (rivers, streams, creeks)
b) Water polygon features (ocean, lakes, ponds)
c) Schools/Daycare
d) Railroads
e) Parks
f) City Boundaries
g) County Boundaries
Customer to provide Response Area data to CentralSquare at the time of CAD map conversion, the CentralSquare GIS Analyst will import Response Areas into CAD Enterprise. GISLink training will provide Customer with the capability to add, delete, or modify Response Areas for ongoing GIS maintenance.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 40
4.4.4.2.1 CentralSquare Responsibilities
a) Perform mapping data conversion and import of Customer-supplied data into applicable licensed Systems and Subsystems.
b) Configure routing and mapping components.
c) Prepare and submit a TCR upon completion of relevant activities.
4.4.4.2.2 Customer Responsibilities
a) After initial GIS conversion, assume responsibility for updating the data using CentralSquare provided GIS tools to ensure that data is up to date for Go-Live.
b) Review and approve the applicable TCR.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 41
4.4.4.3 GISLink Utility Training
Major Task Description
Overview CentralSquare will provide hands-on training in usage of the GISLink and other GIS utilities. GISLink is a CAD Enterprise utility that consolidates GIS data-related tools for maintaining and using GIS data in CentralSquare products.
The class prepares Customer personnel to import and manage existing GIS data used in CAD and Mobile Enterprise.
Customer
Participants
GIS Administrator(s).
Participants should not exceed four (4) per class.
Output Students will learn how to use the GISLink utility to manage GIS data in CAD Enterprise.
Prerequisite System installation to include GIS-related components and initial map installation to include at least one CAD Enterprise console with the GISLink utility installed on it.
GIS knowledge and background; familiarity with ESRI tools.
4.4.5. CAD Enterprise Workshops
After the CAD Enterprise operational review has been completed, CentralSquare will conduct one or more CAD Enterprise workshops. Workshops are an extension of the operational review and are specified in the Agreement.
Refer to Appendix Y - Workshop and Training Summary
for a complete listing applicable to
this project.
4.4.5.1 CentralSquare Responsibilities
a) Schedule workshops in accordance with Customer’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Customer review or completion at least 2 weeks prior to each workshop.
c) Conduct workshops based on the distributed agenda.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 42
d) Prepare and submit a TCR upon completion of the workshop.
4.4.5.2 Customer Responsibilities
a) Provide adequate environment to conduct the workshop. b) Ensure participation of the appropriate personnel.
c) Continue Codefile building activities as directed.
d) Review and approve the applicable TCR.
4.4.6. CAD Enterprise Functional Acceptance Testing (FAT)
Major Task Description
Overview Customer leads and CentralSquare will assist with FAT, which is an activity occurring one time after OAR and prior to End User Training and Go-Live. FAT is conducted for the first phase going into production and is not repeated for subsequent phases.
CentralSquare may organize at its discretion, separate breakout FAT sessions for subsections of the Functional Test documents that are applicable only to one agency (for example, applicable only to Law or Fire agencies). Each test will be executed once, and applicable users and agencies must attend the FAT session and conduct the tests.
The FAT process consists of running standard tests in a format designed to verify the functionality of CAD Enterprise. Functional Test documents are submitted and approved by the Customer prior to testing in acknowledgement that the test scenarios will be used to validate System functionality for pre- production and Post Go-Live assessment of features for Software Acceptance.
Test sign off is a precursor to administration of the FAT.
Following the completion of the FAT, any failure will be classified based on the following criteria:
• Go-Live Issues: Issues in the subsystem identified during FAT 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 a subsystem with contractually required functionality that can be corrected after Go-Live. Customer and CentralSquare will mutually agree these issues may be addressed after Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 43
Go-Live. CentralSquare will provide an estimated date for resolution of the issue Post Go-Live
Completion of the Functional Test does not constitute Final System Acceptance.
Customer
Participants
Key members of implementation team familiar with CAD Enterprise from various agencies and/or PSAPs.
Duration As noted in Appendix Y – Workshop and Training Summary.
Output Upon completion, Customer’s CAD Enterprise system is acknowledged as having completed pre-production acceptance.
Customer and CentralSquare will review FAT exceptions (if any), perform an assessment, and determine the timeline for remedying the exceptions (Go-Live versus Post Go-Live).
CentralSquare will not train Customer’s end users until the FAT has been conducted and TCR signoff has been received.
Customer, with CentralSquare assistance as needed, will repeat failed test(s) following correction of issues that caused the test(s) to fail. A full retest of the System will not be conducted.
4.4.6.1 CentralSquare Responsibilities
a) Deliver CentralSquare’s standard FAT document to Customer for review no later than two (2) weeks prior to conducting the FAT.
b) Provide a TCR to Customer to approve receipt of FAT documents and content thereof.
c) Assist Customer in conducting FAT.
d) Identify and document exceptions and passes to determine timeline to remedy exceptions (Go-Live versus Post Go-Live).
e) Upon completion of the FAT, provide a TCR to the Customer for review and approval. FAT exceptions will be documented in the TCR. f) Schedule follow-up testing for validation of exceptions after correction and confirm/document the results via TCR.
g) Provide a final TCR to Customer to confirm resolution of all Go-Live exceptions.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 44
4.4.6.2 Customer Responsibilities
a) Complete all predecessor tasks to include the base system installation and Codefile build required to conduct the FAT.
b) Provide adequate environment to conduct the FAT.
c) Review and signoff on the FAT test documents no later than one week prior to commencement of the FAT via TCR.
d) Lead the FAT by providing operational SME’s with the authority to provide validation of the tests have passed. It should be noted that this is not a training exercise so SME’s should have system knowledge.
e) Assist CentralSquare in documenting FAT results.
f) Review and approve the applicable TCRs.
4.4.7. CAD Enterprise Training
CAD Enterprise Training is conducted on consecutive weekdays during business hours.
Alternate training schedules (e.g., Monday class starts for classes that would normally start on a Tuesday, multiple classes per day, evening, and weekend classes) are subject to additional cost.
Training classes are conducted based on the quantities specified in the Agreement. The appearance of a course description in this Statement of Work does not mean a course will be conducted – it must be listed in the Agreement. Refer to Appendix Y - Workshop and
Training Summary f or a complete listing applicable to this project.
The training classes related to CAD Enterprise and its subsystems are classified into three general groups:
Classes dependent upon specific Customer configurations and requirements; therefore, conducted on Customer’s System after completion of the Functional Test and in preparation for Go-Live. CAD Enterprise Call Taker/Dispatcher User Training Course are examples.
Classes such as GISLink are delivered to a specialized group within Customer’s team throughout the Project to assist with implementation and maintenance of the System.
Classes such as System Administration Training and CAD API Training that are not dependent upon Customer configurations and are generic in nature. These classes are offered on a regular schedule by CentralSquare (not by Customer), and as a remote activity, include attendees from different agencies.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 45
Refer to Appendix Y - Workshop and Training Summary for a complete listing applicable to this project.
4.4.7.1 CentralSquare Responsibilities (For All CAD Enterprise Training) a) Conduct training in increments of one (1), eight (8) hour day. b) Provide feedback to Customer Supervision as to the progress of the students. c) Prepare and submit a TCR upon completion of each type of training.
4.4.7.2 Customer Responsibilities (For All CAD Enterprise Training) a) Provide adequate environment for the execution of the training. b) Provide a supervisor for each class to respond to Customer-specific questions. c) Review and approve the applicable TCRs.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 46
4.5 Implementation of Mobile Enterprise
4.5.1. Implementation Process Overview
Major Task Description
Overview CentralSquare Consultant will complete Mobile configuration options based on related options in CAD Enterprise and Mobile Configuration Sheet once servers are installed at Customer site.
The same configurations are used as a base for the Functional Test document.
Conversion and import of Mobile map and layers needed for Go-Live are also completed.
All activities are performed remotely.
Customer
Participants
CAD/Mobile Administrators and core members of Customer implementation team who can address key points and make decisions to complete Mobile System configuration.
Output Completed Mobile configuration.
The CentralSquare Consultant will provide ongoing consultation services.
4.5.1.1.1 CentralSquare Responsibilities
a) Provide the Customer with the applicable steps to download the MobileX Enterprise application from the Application store.
b) Guide the Customer through the download process and the applicable configurations needed.
c) Validate the MobileX Enterprise handheld device is working in the installed environment.
d) Prepare and submit a TCR upon completion of the installation.
4.5.1.1.2 Customer Responsibilities
a) Provide a list of agencies and number of licenses per agency for configuration. b) Perform all required network configurations as advised by the CentralSquare Consultant prior to the configuration event.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 47
c) For any staff member that is attending the Mobile Train-the-Trainer training session, the handheld device should be installed and configured prior to the class.
d) Review and approve the applicable TCR.
4.5.2. Mobile Enterprise Functional Testing
Major Task Description
Overview Customer leads and CentralSquare will assist with FAT), which is an activity occurring in conjunction with the CAD FAT and prior to end user training and Go-Live.
Since the focus of the FAT is functionality of the System but not a validation of Codefiles, it is not necessary that Mobile is completed prior to conducting the Functional Test.
The FAT process consists of running standard tests in a format designed to verify the functionality of Mobile Enterprise. Functional Test documents are submitted and approved by Customer prior to testing in acknowledgement that the test scenarios will be used to validate System functionality for pre- production and Post Go-Live assessment of features for Software Acceptance.
Script sign off is a precursor to administration of the Functional Test.
Following the completion of the Functional Acceptance Test, any failure will be classified based on the following criteria:
Go-Live Issues: Issues in the subsystem 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 a subsystem with contractually required functionality that can be corrected after Go-Live. Customer and CentralSquare will mutually agree these issues may be addressed after Go-Live. CentralSquare will provide an estimated date for resolution of the issue Post Go-Live.
Completion of the Functional Test does not constitute Final System Acceptance.
Customer
Participants
Key members of implementation team familiar with Mobile Enterprise.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 48
Duration As noted in Appendix Y – Workshop and Training Summary.
Output Upon completion, Customer’s Mobile Enterprise system is acknowledged as having completed pre-production Acceptance.
Customer and CentralSquare will review Functional Test exceptions (if any), perform an assessment, and determine the timeline for remedying the exceptions (pre versus Post Go-Live).
CentralSquare will not train Customer’s end users until the Functional Test has been conducted and TCR signoff has been received.
Customer, with CentralSquare assistance as needed, will repeat failed test(s) following correction of issues that caused the test(s) to fail. A full retest of the System will not be conducted.
4.5.2.1 CentralSquare Responsibilities
a) Deliver CentralSquare’s standard Functional Test documents to Customer no later than two weeks prior to conducting the Functional Test. b) Provide a TCR to Customer to approve the receipt of the Functional Test documents.
c) Install at least one Mobile Customer (device) to conduct the Functional Test. d) Assist Customer in conducting the Functional Test.
e) Identify and document any exceptions discovered during the Functional Test. f) Upon completion of the Functional Test, provide a TCR to Customer for review and approval. Functional Test exceptions will be documented in the TCR. g) Schedule follow-up testing for validation of exceptions after correction and confirm/document the results via TCR.
h) Provide a final TCR to Customer to confirm resolution of all Go-Live exceptions.
4.5.2.2 Customer Responsibilities
a) Complete all predecessor tasks to include the base system installation and Codefile build required to conduct the Functional Acceptance Test. b) Provide adequate environment to conduct the Functional Test. c) Review and sign off on the Functional Test document, via TCR, no later than one (1) week prior to commencement of the Functional Test.
d) Lead the Functional Test by providing operational Subject Matter Experts with the authority to provide validation that the tests have passed.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 49
e) Assist CentralSquare in documenting Functional Test results. f) Review and approve the applicable TCRs.
4.5.3. Mobile Enterprise Training
Mobile Enterprise Training classes are conducted based on the quantities specified in the Agreement and are conducted on consecutive weekdays during business hours. Alternate training schedules (multiple classes per day, evening, and weekend classes) are subject to additional charge. Training classes will only be delivered after the Functional Test has been completed and the results are documented and approved via TCR.
CentralSquare trains a small group of trainers/users, who then train the balance of field users.
Refer to Appendix Y - Workshop and Training Summary
for a complete listing applicable to
this project.
4.5.3.1 CentralSquare Responsibilities
a) Schedule training classes.
b) Conduct train-the-trainer classes.
c) Prepare and submit a TCR to Customer upon completion.
4.5.3.2 Customer Responsibilities
a) Schedule appropriate Customer staff to attend training. b) Conduct Customer led training for remaining staff.
c) Provide adequate environment for the execution of training to include seating for each workstation and an overhead projector.
d) Review and approve the applicable TCRs.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 50
4.6 Implementation of Records Enterprise
Records Enterprise 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 the proper functionality prior to Go-Live.
4.6.1. Records Enterprise Implementation Process Overview
Major Task Description
System Orientation Initial activity to kick off work on deliverable.
Workshops CentralSquare and Customer will conduct workshops as indicated in the approved Project Schedule.
Base System Build After Records Enterprise Administration and Review Training, Customer assumes ownership of building and maintaining modules and templates.
Functional
Acceptance Testing
Conducted prior to the start of End User Training.
Training As indicated in the approved Project Schedule.
Go-Live The application is brought into production use.
4.6.2. Records Enterprise System Orientation
Major Task Description
Overview Comprehensive business process review of Customer’s current operation as well as discussion regarding key configuration options and assignments related to the system build.
Discussion of workflow processes from the field report to State submission.
May include observation of Department Divisions such as Patrol, Records, Investigations, Property & Evidence, etc.
Review of reporting requirements.
Determination of event numbering (Incidents) including master incident numbers and case numbers.
Customer
Participants
Records Administrators and core members of Customer implementation team who can address key points and make business process decisions.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 51
CentralSquare Project Manager will work with Customer PM to determine the appropriate number of attendees for each breakout group.
4.6.2.1 CentralSquare Responsibilities
a) Schedule the System Orientation meeting in accordance with Customer’s availability and the Project Schedule.
b) Prepare and distribute meeting agendas and documents for Customer review or completion at least 2 weeks prior to each meeting.
c) Conduct the meetings based on a distributed agenda.
d) Document and assign owners and due dates to action items and track to closure. e) Prepare and submit a TCR upon completion of relevant activities.
4.6.2.2 Customer Responsibilities
a) Ensure participation of key stakeholders and decision-makers in the System Orientation process.
b) Provide subject matter experts that can explain the agency’s current workflow and application processes and make decisions regarding any proposed changes in implementing the Records Enterprise System.
c) Provide subject matter experts who will become Records super users, as well as a Records Administrator who will be responsible for the ongoing maintenance of the Records application.
d) Provide subject matter experts responsible for translating the geopolitical/operational boundaries into data (ESRI shape files) suitable for use within Records.
e) Provide subject matter experts responsible for the maintenance of street centerline data.
f) Review and approve applicable TCRs.
4.6.3. Records Enterprise Base System Build
Major Task Description
Overview After completion of the Records Enterprise Administration and Review Workshop, and through subsequent workshops and training classes, Customer assumes ownership of completion and ongoing
maintenance of system.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 52
Customer
Participants
Records Enterprise Administrators and core members of Customer implementation team who can address key points and make configuration decisions while participating in the system building process.
Output After initial build by CentralSquare Consultant, Customer completes and maintains system files and templates, to include Personnel, Roles, Property Locations, and Violation Codes.
CentralSquare delivers the Records Enterprise system with base NCIC and NIBRS codes. It is the Customer’s responsibility to complete NIBRS code-mapping to Violation Codes.
CentralSquare does not provide training or assistance with Customer’s understanding of State or Federal IBRS requirements or laws.
CentralSquare services are reserved exclusively to the configuration and use of Records Enterprise to collect and output state or federal required data.
No conversion of historical incident data from UCR to NIBRS is included. As a result, there may be historical records that will contain missing NIBRS mandatory fields.
The CentralSquare Consultant will provide ongoing consultation services throughout the project.
4.6.3.1 CentralSquare Responsibilities
a) Monitor and evaluate System build throughout implementation and provide guidance as needed.
4.6.3.2 Customer Responsibilities
a) Provide timely input and updates to Templates, Workflows, Users, Roles, and System codes.
b) Continue and complete building the Templates, Workflows, Users, Roles, and System files (those not built by CentralSquare).
Note: Any changes required to Records Enterprise templates required for standard or custom Interface work is the responsibility of the Customer.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 53
4.6.4. Geographical Information Services
4.6.4.1 Data Evaluation
The CentralSquare GIS Analyst will work with the Customer to create the address locator packages and configure Records GIS services. Each GIS layer type (street centerlines and address points) must be delivered and maintained in a single layer.
4.6.4.2 CentralSquare Responsibilities
a) Evaluate Customer-supplied GIS data to ensure it is formatted correctly for creation of the address locator packages.
b) Create address locator packages and configure Records GIS services. c) Prepare and submit a TCR upon completion.
4.6.4.3 Customer Responsibilities
a) Provide data in the required format, and per Project Schedule. b) Based on the analysis provided by CentralSquare, make requested changes to mapping data to meet CentralSquare’s GIS data requirements. c) Review and approve the appropriate TCR.
4.6.5. Records Enterprise Workshops
CentralSquare will conduct Records Enterprise workshops after the Records Enterprise Administration and Review Training has been completed. Workshops are specified in the Agreement but include:
Records Enterprise Workshop #1 – Incident, Arrest, Field Interview and Case Management
Review, configuration, and completion of the Incident, Arrest, and Case Management modules including the queues, templates, and code tables.
Records Enterprise Workshop #2 – Crash, Citation, Other Event Review, configuration, and completion of the Crash, Citation, and Other Event & Field Interview modules including the queues, templates, and code tables.
Records Enterprise Workshop #3 – Records Administration/State Reporting Review, training and testing of the Records Administration tasks including the redaction, expungement, searching, validations, and State Reporting.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 54
Records Enterprise Workshop #4 – Property & Evidence
Configuration and setup of the Evidence module to include: evidence storage locations, barcode labeling and scanning evidence, performing inventory, and tracking chain of custody for evidence items.
Participants include key members of Customer’s implementation team to include Records central and local administrators, and each key functional area, and should not exceed ten (10) students.
Refer to Appendix Y - Workshop and Training Summary
for a complete listing applicable to
this project.
4.6.5.1 CentralSquare Responsibilities
a) Schedule workshops in accordance with Customer’s availability and the Project Schedule.
b) Prepare and distribute the meeting agendas and documents for Customer review or completion prior to each workshop.
c) Conduct workshops based on the distributed agenda.
d) Prepare and submit a TCR upon completion of the workshop.
4.6.5.2 Customer Responsibilities
a) Provide adequate environment to conduct the workshop. b) Ensure participation of the appropriate personnel.
c) Continue system building activities as directed.
d) Review and approve the applicable TCR.
4.6.6. Records Enterprise Functional Acceptance Testing
Major Task Description
Overview Customer leads and CentralSquare will assist with FAT, which is an activity occurring prior to End User Training and Go-Live.
Since the focus of the Functional Test is functionality of the System but not a validation of Codefiles, it is not necessary that all Codefiles be built prior to conducting the Functional Test.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 55
The Functional Test process consists of running standard tests in a format designed to verify the functionality of Records Enterprise. Functional Test documents are submitted and approved by Customer prior to testing in acknowledgement that the test scenarios will be used to validate System functionality for pre-production and Post Go-Live assessment of features for Software Acceptance. Script sign off is a precursor to administration of the Functional Test.
CentralSquare may organize at its discretion, separate breakout Functional Test sessions for subsections of the Functional Test documents that are applicable only to one agency (for example, applicable only to a Sheriff’s Department or single agency). Each test will be executed once, and all applicable users and agencies must attend the Functional Test session and observe the tests.
Following the completion of the FAT, any failure will be classified based on the following criteria:
Go-Live Issues: Issues in the subsystem 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 a subsystem with contractually required functionality that can be corrected after Go-Live. Customer and CentralSquare will mutually agree these issues may be addressed after Go- Live. CentralSquare will provide an estimated date for resolution of the issue Post Go-Live
Support Issues: Issues in a subsystem identified that are not contractually required functionality and do not prevent the Customer from performing normal daily or monthly processes; and therefore, can be corrected after the subsystem Go-Live. These issues will not affect acceptance of the system.
Support issues will be managed based upon the procedures outlined in the Agreement.
Completion of the Functional Test does not constitute Final System Acceptance.
Customer
Participants
Key members of the implementation team familiar with Records Enterprise and should not exceed five (5) per class.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 56
Output Upon completion, Customer’s Records Enterprise system is acknowledged as having completed pre-production Acceptance.
Customer and CentralSquare will review Functional Test exceptions (if any), perform an assessment, and determine the timeline for remedying the exceptions (pre versus Post Go-Live).
CentralSquare will not begin training until the Functional Test has been conducted and TCR signoff has been received.
Customer, with CentralSquare assistance as needed, will repeat failed test(s) following correction of issues that caused the test(s) to fail. A full retest of the System will not be conducted.
4.6.6.1 CentralSquare Responsibilities
a) Deliver CentralSquare’s standard Functional Test documents to Customer no later than two weeks prior to conducting the Functional Test. b) Provide a TCR to Customer to approve receipt of the Functional Test documents and content thereof.
c) Assist Customer in conducting the Functional Test.
d) Identify and document exceptions and assess to determine timeline to remedy exceptions (pre versus Post Go-Live).
e) Upon completion of Functional Test, provide a TCR to Customer for review and approval. Functional Test exceptions will be documented in the TCR. f) Schedule follow-up testing for validation of exceptions after correction and confirm/document the results via TCR.
g) Provide a final TCR to Customer to confirm resolution of all Pre Go-Live exceptions.
4.6.6.2 Customer Responsibilities
a) Complete all predecessor tasks to include the base system installation and code table entry and configuration to conduct the Functional Test. b) Provide adequate environment to conduct the Functional Test. c) Review and signoff on the Functional Test documents no later than one week prior to commencement of the Functional Test via TCR.
d) Lead the Functional Test by providing operational subject matter experts with the authority to provide validation the tests have passed. e) Assist CentralSquare in documenting Functional Test results.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 57
f) Review and approve the applicable TCRs.
4.6.7. Records Enterprise Training
Records Enterprise Training classes are conducted on consecutive weekdays during business hours (Tuesday-Friday). Alternate training schedules (multiple classes per day, evening, and weekend classes) are subject to additional cost.
Training classes are conducted based on the quantities that are specified in the Agreement. The appearance of a course description in this Statement of Work does not mean a course will be conducted – it must be listed in the Agreement.
A maximum of 15 students are allowed in each training class.
Refer to Appendix Y - Workshop and Training Summary
for a complete listing applicable to
this project.
4.6.7.1 CentralSquare Responsibilities (for all Records Enterprise Training) a) Schedule the Records Enterprise Training class(es) in accordance with Customer’s availability and the Project Schedule.
b) Prepare and distribute agendas and documents prior to each meeting. c) Develop and provide the Records Enterprise Training Plan. d) Conduct session(s) per the Schedule.
e) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes.
4.6.7.2 Customer Responsibilities (for all Records Enterprise Training) a) Provide adequate environment for execution of training. b) Provide a Local Records Administrator for each class to answer agency specific questions related to the build of Customer’s system and internal policies or workflow.
c) Conduct Customer led training for remaining staff.
d) Review and approve applicable TCRs.
4.7 Implementation of Common Identity Management (CIM)
Once the Software Installation is complete, the CentralSquare Technical Services Engineer and Consultants will configure a Common Identity Management (CIM) instance in each Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 58
environment that will provide identity management and authentication services for the Enterprise Suite applications.
4.7.1. CIM Configuration
Major Task Description
Overview CentralSquare, with the participation of the Customer, will configure CIM with roles.
Mapping of CAD/Records roles to CIM roles. Linking the role mappings within CIM.
Active Directory integration for each Active Directory domain which is to be integrated with CIM.
Importing/associating CAD/Records users with CIM users.
Customer
Participants
Administrators of the CAD/Records applications. Participants must be able to make decisions regarding configurations in the system for the CAD/Records applications.
Testing of configurations deployed by CentralSquare.
Training CIM Systems Administration Training
Two (2) hour training performed remotely.
Output CAD/Records user management will be centralized to the CIM application.
Users will be able to use one (1) user account to access each of the systems.
4.7.1.1 CentralSquare Responsibilities
a) Configure a Common Identity Management (CIM) instance in each environment. b) Schedule the working sessions in accordance with Customer’s availability and the Project Schedule.
c) Conduct the working sessions based on the schedule and provide assignments as necessary to Customer.
d) Ensure the module is functioning per the configuration. e) Conduct Administrative training.
f) Prepare and submit a TCR upon completion of the deliverable.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 59
4.7.1.2 Customer Responsibilities
a) Ensure participation of appropriate personnel for each scheduled activity. b) Complete all assignments on a timely basis.
c) Review and approve the applicable TCR.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 60
4.8 Implementation of CrimeView Analytics
CrimeView Analytics will be implemented through a series of standard steps and process gates.
4.8.1. CrimeView Analytics Implementation Process Overview
Major Task Description
Discovery Discovery includes the Kickoff meeting and the requirements review & collection required for the implementation.
Mapping and &
Configuration
CentralSquare will map Customer code values to standard categories to enable CrimeView map symbology. The CentralSquare GIS/Analytics Specialist will configure and automate the ETL (Extract, Transform, and Load) process that securely replicates data to the cloud CrimeView environment, and configure the user application.
Demonstration After the completing the Mapping and Configuration, CentralSquare will provide Initial Demonstration, Consultation, and Content Preparation.
Customer assumes ownership of the base system build at the conclusion of the demonstration, consultation & content preparation.
Training As indicated in Appendix Y.
System Review The system review period begins after the Administrator/Designer Training and closes ten (10) business days after Train the Trainer.
Acceptance Application is accepted at conclusion of System Review.
Prerequisite Enterprise applications in production.
4.8.2. Discovery
The Discovery includes a kickoff meeting and the requirements review & collection. The Kickoff meeting provides a review of the application’s functionality and project deliverables, Customer prerequisites, and implementation process. Furthermore, the Customer’s preparation and delivery of prerequisites to the CentralSquare project team is a critical gate for starting implementation work.
4.8.2.1 CentralSquare Responsibilities
a) Schedule and lead the meeting.
b) Provide action items.
c) CentralSquare is responsible for providing Hardware, GIS, and any other requirements details to Customer during and following the kickoff meeting.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 61
4.8.2.2 Customer Responsibilities
a) Configure the CrimeView import server and provide CentralSquare with a local administrator account.
b) Collect and deliver the GIS data to be used for the application to CentralSquare. c) Configure Hardware, including creation of a CentralSquare local administrator account on the import server.
d) Provide required GIS data.
4.8.3. Code Mapping & Application Configuration
CentralSquare will map Customer code values to standard categories to enable CrimeView map symbology. The CentralSquare GIS/Analytics Specialist will configure and automate the ETL (Extract, Transform, and Load) process that securely replicates data to the cloud CrimeView environment, and configure the user application.
4.8.3.1 CentralSquare Responsibilities
a) Extract code tables from Customer’s CAD and/or Records Enterprise system and match to standard code sets.
b) If necessary, provide Customer with an Excel document to review code mapping. c) Configure the ETL process and CrimeView application. d) Prepare standard dashboards for initial demonstration.
4.8.3.2 Customer Responsibilities
a) Review and revise code mapping within ten (10) business days. b) Respond to information, data, and assistance requests. c) Work with the CentralSquare Project Manager to facilitate a date for the Application Review Meeting.
4.8.4. Initial Demonstration, Consultation, and Content Preparation The CentralSquare GIS/Analytics Specialist will provide a short demonstration of the system with Customer’s data and lead a discussion of Customer needs and how the system might meet those needs.
4.8.4.1 CentralSquare Responsibilities
a) Schedule the initial demonstration in accordance with the Customer’s availability and the Project Schedule.
b) Schedule and lead the initial demonstration and collect Customer feedback.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 62
4.8.4.2 Customer Responsibilities
a) Customer is responsible for having the appropriate users and stakeholders attend the initial demonstration and participate in follow-up conversations.
4.8.5. CrimeView Training
Training is conducted on consecutive weekdays during business hours. Alternate training schedules (e.g., Monday class starts for classes that would normally start on a Tuesday, multiple classes per day, evening, and weekend classes) are subject to additional cost.
Training classes are conducted based on the quantities specified in the Agreement. The appearance of a course description in this Statement of Work does not mean a course will be conducted – it must be listed in the Agreement. Refer to Appendix Y - Workshop and
Training Summary f or a complete listing applicable to this project.
4.8.5.1 CentralSquare Responsibilities (for all Search Training) a) Schedule the Search Training class(es) in accordance with Customer’s availability and the Project Schedule.
b) Provide the training materials.
c) Conduct session(s) per the Schedule.
d) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes.
4.8.5.2 Customer Responsibilities (for all Search Training) a) Provide adequate environment for execution of training. b) Provide an Administrator for each class to answer Customer specific questions related to the application’s use, internal policies, or workflow. c) Provide schedule for training remaining end users.
d) Review and approve applicable TCRs.
4.8.6. System Review
The system review period begins after the Administrator/Designer Training and closes ten (10) business days after Train the Trainer. During the System Review, Customer is responsible for reviewing the application and informing the CentralSquare project team of any noticed or potential issues or deficiencies with the configuration or data.
CentralSquare will address the reported items during and following the review period; CentralSquare responses will fall into one of the following categories:
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 63
a) Item refers to something in the application or data import configuration that has been confirmed and fixed/changed.
b) Further information or action from Customer is required to assess the item (a time window for Customer action will be provided).
c) Item is a result of Customer’s source data and requires Customer action to fix (a time window for Customer action will be provided).
d) Item identifies a software bug that has been submitted for review and rectification.
e) Item represents a requested enhancement to the software. Software enhancements are not included in the scope of the project but may be undertaken at CentralSquare’s Product Management discretion.
4.8.6.1 CentralSquare Responsibilities
a) Inform Customer that the System Review period has begun; provide the review items listed above.
b) Receive and address all items/issues submitted by Customer during the System Review.
c) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes.
4.8.6.2 Customer Responsibilities
a) Interact with the system and create new content after the Administrator/Designer Training.
b) Inform the CentralSquare Project Manager of any questions, issues, or requested configuration changes.
c) Review and approve applicable TCRs.
4.8.7. CrimeView Analytics Acceptance
The Crime Analytics Dashboard application will be considered Accepted upon completion of the System Review.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 64
4.9 Implementation of Crimemapping.com
Crimemapping.com will be implemented through a series of standard steps and process gates.
4.9.1. Crimemapping.com Implementation Overview
Major Task Description
Discovery The Customer will be provided a worksheet to match customer offense codes with the Crimemapping Crime Categories.
Configuration Configure data extraction application and deploy customer data.
System Review and
Go-Live
The CentralSquare Project Manager will provide Customer with the Crimemapping Staging Site URL and login information. Customer will have ten (10) days to review the site prior to the data being made available to the public on Crimemapping.com.
4.9.2. Discovery
The CentralSquare GIS/Analytics Specialist will provide Customer with a Crime Categorization Worksheet enabling them to match the Customer’s offense codes to the fifteen (15) Crimemapping Crime Categories. All offense codes not mapped to one of the fifteen (15) categories will be excluded from the site. Customer will complete the worksheet and return it to the CentralSquare Project Manager within ten (10) days.
4.9.2.1 CentralSquare Responsibilities
a) Provide the Crime Categorization Worksheet to the Customer.
4.9.2.2 Customer Responsibilities
a) Complete the Crime Categorization Worksheet within ten (10) days and return it to the CentralSquare Project Manager.
4.9.3. Configuration
Upon receipt of the required worksheet and information, the CentralSquare GIS/Analytics Specialist will configure the data extraction application and deploy the agency’s data to the Crimemapping environment. Site and data specifications are listed in the Crimemapping.com Appendix.
4.9.3.1 CentralSquare Responsibilities
b) Connect to the source server and configure the ETL process. c) Configure the Customer on the Crimemapping.com staging site.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 65
d) Provide Customer with the Crimemapping.com staging site URL and login account.
4.9.3.2 Customer Responsibilities
b) Provide Jurisdiction boundary GIS file (if available) c) Provide the Address of the Customer’s headquarters
d) Provide the Customer website and up to three additional URLs may be provided for reference on Crimemapping.com
4.9.4. System Review & Go-Live
The Crimemapping.com System Review initiates upon CentralSquare’s provision of the Crimemapping staging site URL and login account. The System Review duration is ten (10) days, and upon completion of the review period, the Customer’s data will be released to the publicly available Crimemapping.com site signifying “Go-Live.”
During System Review, Customer is responsible for reviewing the application and informing the CentralSquare Project Manager of any noticed or potential issues or deficiencies. The System Review period will expire in ten (10) business days, at which point, CentralSquare will address all submitted items prior to “Go-Live”.
CentralSquare responses to each submitted item will fall into one of the following categories:
• Item refers to something in the application or data import configuration that has been confirmed and fixed/changed.
• Further information or action from Customer is required in order to assess the item (a time window for Customer action will be provided).
• Item is a result of the source query or GIS data provided by Customer and requires Customer action to fix (a time window for Customer action will be provided).
• Item identifies a software bug that has been submitted for review and rectification.
• Item refers to a function or known limitation of the application that lies in the application code rather than the configuration. Changes to application code are excluded from this project.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 66
4.9.4.1 CentralSquare Responsibilities
a) Connect to the source server and configure the ETL process. b) Configure the agency on the Crimemapping.com staging site. c) Provide Customer with the Crimemapping.com staging site URL and login account.
d) Receive and address all items/issues submitted by Customer during the System Review.
e) Release Customer Customer’s data to the public Crimemapping.com site after the ten (10) day review period.
f) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes.
4.9.4.2 Customer Responsibilities
a) Review the Customer’s data on the Crimemapping Staging Site. b) Provide approval to release the Customer’s data to the public Crimemapping.com site prior to expiration of the ten (10) day review period. c) Review and approve applicable TCRs.
4.10 System Integration Testing
Once the Functional Test is concluded for CAD Enterprise, Mobile Enterprise, Records Enterprise, and interfaces and in preparation for Go-Live, CentralSquare and Customer will conduct System Integration Testing, with CentralSquare assisting remotely.
The System Integration Test will be conducted based on scenarios that test call flow from creation to final disposition in CAD and include CAD and Mobile Enterprise, and Interfaces that can be tested in the pre-production environment and are scheduled to Go-Live at the same time. It is recommended that Customer utilize sample calls from their legacy System.
A small group of Customer staff (1-2 dispatchers and 1-2 Mobile field users) should participate in this test with CentralSquare Consultant. CentralSquare will work with Customer on defining a set of test scenarios to test the system based on Customer’s practices; the scenarios must be signed off prior to commencement of the System Integration Test.
A small group of Customer staff (1-2 Records staff and field users) should participate in this test. CentralSquare will work with Customer to refine the test scenario that test the system based on Customer’s practices and must be signed off prior to commencement of the System Integration Test.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 67
At the completion without critical issues that prevent the System to be taken Live, Customer shall provide TCR approval that the System is ready for Go-Live.
4.10.1. CentralSquare Responsibilities
a) Schedule System Integration Test with Customer.
b) Assist Customer in preparing test scenarios based on Customer’s practices, no later than six (6) weeks prior to conducting the System Integration Test. c) Deliver CentralSquare’s standard System Integration Test document to Customer for review no later than eight (8) weeks prior to conducting the System Integration Test. d) Provide a TCR to Customer to approve receipt of System Integration Test document and content thereof.
e) Assist Customer in conducting the System Integration Test. f) Identify and document exceptions and passes to determine timeline to remedy exceptions (Go-Live versus Post Go Live).
g) Upon completion of System Integration Test, provide a TCR to Customer for review and approval. System Integration Test exceptions will be documented in the TCR. h) Schedule follow-up testing for validation of exceptions after corrections and confirm/document the results via TCR.
i) Provide a final TCR to Customer to confirm resolution of all Go-Live exceptions.
4.10.2. Customer Responsibilities
a) Provide adequate environment to conduct the System Integration Test. b) Provide test systems (or pre-production systems) for all integrations and interfaces. If Customer cannot provide a test system CentralSquare must test using the production system. This testing includes, but is not limited to, test data entry in a production system.
c) Provide test scenarios that closely simulate Customer’s normal call flow no later than six (6) weeks prior to conducting the System Integration Test. d) Review and sign off on the System Integration Test document, via TCR, no later than one (1) week prior to commencement of the System Integration Test. e) Participate in conducting the System Integration Test by providing operational Subject Matter Experts with the authority to provide validation that the tests have passed. . f) Assist CentralSquare in documenting System Integration Test results. g) Review and approve the applicable TCRs.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 68
5 SYSTEM AND SUBSYSTEM PRE GO-LIVE TASKS
5.1 Overview
Preparation for cutover to live operations will be outlined in the weeks leading up to the Go-Live in the Project Schedule and in the Go-Live Plan. The Go-Live plan includes:
a) The overall timeline for the event
b) Products involved
c) Roles and responsibilities
d) Established meeting dates/times
e) Issue reporting and escalation process
f) Transition to support
g) The communication plan
CentralSquare will prepare a Pre Go-Live checklist for each Subsystem and the Interfaces, if applicable, identifying the activities that will ensure preparation. The list will identify both CentralSquare and Customer responsibilities for completing the Pre Go-Live activities. Training data will be purged from the system, and the system itself will be locked down.
CentralSquare will provide the Customer with a Go-Live Authorization Letter. The Go- Live Authorization Letter confirms the system has been installed and tested, and that the Customer agrees to proceed with moving the system to live operation. It acknowledges sufficient user training has been completed, confirms software is functional for a live environment, and that none of the currently identified issues are critical to the Go-Live. This letter will list all the Subsystems and Interfaces, if applicable, scheduled for the Go-Live, as well as any exceptions.
The date and time of the Go-Live is memorialized, along with assurance that the Customer’s technical team and Subject Matter Experts will be available twenty-four (24) hours a day to support the CAD/Mobile Enterprise Go-Live and standard business hours (8:00am – 5pm, Monday – Friday for Records Enterprise unless otherwise noted in the Agreement. The Customer must approve the Go-Live Authorization Letter no later than three (3) weeks prior to Go-Live. Approval of the letter is required.
CentralSquare will invite the Customer to participate in a presentation to gain familiarity with the structure and methodologies of the Support Services Department.
CentralSquare will assist in confirming that representatives designated by Customer needing access to enter and track support cases have credentials for CentralSquare access.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 69
5.1.1. CentralSquare Responsibilities
a) Schedule internal Go-Live readiness checks and internal team planning meetings. b) Prepare the Go-Live Plan for delivery to Customer.
c) Prepare the Pre Go-Live checklist for delivery to Customer. d) Prepare the Go-Live Authorization Letter and deliver to Customer. e) Identify the participants for the Go-Live in accordance with the terms of the Agreement.
f) Coordinate CentralSquare personnel in advance of the Go-Live date to complete final tasks as a part of the Go-Live preparations.
5.1.2. Customer Responsibilities
a) Complete end user training needed to support the live use of Subsystems. b) Participate in review of the Go-Live Plan.
c) Complete prerequisite tasks as directed by CentralSquare. d) Review and approve the Go-Live Authorization Letter no later than three (3) weeks prior to Go-Live.
e) Develop a process for the identification of, research, reporting and resolution of issues.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 70
6 SYSTEM AND SUBSYSTEM GO-LIVE
6.1 Overview
Go-Live of the Enterprise Subsystems and the required Interfaces, if applicable, into a live operational environment (i.e., production use) is a highly orchestrated activity that will require resources from both Customer and CentralSquare teams.
Go Live is conducted on consecutive weekdays (Monday-Friday). A Go Live that requires CentralSquare support that begins before or extends beyond weekdays (unless included in the Agreement) are subject to additional cost.
The system is brought into production per the Go-Live Authorization Letter and the Go-Live Plan.
During Go-Live, issues are reported and managed by CentralSquare with Customer’s assistance.
Upon cessation of Go-Live support by CentralSquare, the issues will be submitted by the Customer using CentralSquare’s on-line support system, Salesforce.
• “Go-Live” means the event that occurs when the Customer first uses a Subsystem in live operations. A separate Go-Live may take place with respect to each Subsystem, each Interface, and each Modification.
• “Go-Live” means “first use in a non-test bed environment”.
6.1.1. CentralSquare Responsibilities
a) Assist Customer in placing the system into production. b) Assist Customer staff in usage of the system as well as documenting, reporting, and researching issues.
c) Provide support during and after system Go-Live as specified within the Agreement. d) Prepare and submit TCR(s) upon first live operation of system in a live environment. e) If applicable, Post Go-Live deliverables will be managed to completion of delivery by the CentralSquare Project Manager per the Agreement.
6.1.2. Customer Responsibilities
a) Place the software into production and begin operational use in accordance with the project schedule, Go-Live Plan, and Go-Live Authorization Letter.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 71
b) Provide adequate persons for the supervision and assistance to end users during Go- Live and beyond the participation of the CentralSquare staff. c) Provide dedicated workstations for CentralSquare support staff use during Go-Live. d) Provide IT support to cover all Customer end user and CentralSquare staff hours of operation.
e) Review and approve the applicable TCR(s).
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 72
7 RELIABILITY PERIOD
7.1 Overview
Upon Go-Live of each Subsystem(s), the Customer shall use the Subsystem(s) for a thirty (30) consecutive day period to verify operational functionality in a live (production) environment.
The Reliability Period is completed when the Customer uses the Subsystem(s) for a thirty (30) consecutive day period without any Priority 1 – Urgent or Priority 2 – Critical software errors (as those terms are defined in the Agreement). In the event that a Priority 1 – Urgent or Priority 2 - Critical software error occurs during the Reliability Period, CentralSquare shall commence actions in accordance with the Agreement to correct the reported error.
Note: If Subsystems do not Go-Live on the same day, or if agencies and/or PSAPs Go-Live in multiple phases, the Reliability Period for each Subsystem will start the first day that Subsystem goes live and is used in a production environment by any agency and/or PSAP. There will not be a separate Reliability Period as subsequent agencies and/or PSAPs Go-Live.
In the event a Priority 1 - Urgent software error occurs between day one (1) and day thirty (30) of the Reliability Period, the Reliability Period will be stopped and restarted at day one (1) once the software error has been resolved in accordance with the Agreement.
In the event a Priority 2 - Critical software error error occurs between day one (1) and day thirty (30) of the Reliability Period, the Reliability Period will be stopped and restarted at day one (1) once the software error has been resolved in accordance with the Agreement.
Priority 1 - Urgent or Priority 2 – Critical software errors caused by factors that are outside of CentralSquare’s control, and/or from variables which are outside the scope of CentralSquare’s responsibilities, will not be counted Priority 1 - Urgent or Priority 2 software errors. Examples of such issues could be, but are not limited to:
• Power failures
• Operator error
• External network failure
• Availability of components that are not provided by CentralSquare but Interface to/from the CentralSquare solution
• Hardware or operating system software
• Non-CentralSquare supplied software components introduced into the working environment
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 73
During the Reliability Period, the Subsystem(s) will be frozen, (i.e., no changes, fixes, and/or updates will be applied, except those that are required to address downtime failures associated with the Reliability Period.).
At the conclusion of the Reliability Period, as further defined in the Agreement, the Subsystem(s) will be deemed reliable by the Customer and CentralSquare.
7.1.1. CentralSquare Responsibilities
a) Provide a TCR to the Customer to document the start of the Reliability Period upon Go-Live of the Subsystem(s).
b) Address issues that are reported during this Reliability Period. c) Provide a TCR to the Customer to document any stops and restarts of the Reliability Period.
d) Document Priority 3 – Non-Critical and Priority 4 – Minor software errors that are not considered “Reliability Period” issues to be addressed as part of the support and maintenance of the Subsystem.
e) Provide the TCR to document completion of the Reliability Period of the Subsystem(s).
7.1.2. Customer Responsibilities
a) Review and sign off on the TCR for documenting the start of the Reliability Period upon Go-Live of the Subsystem(s).
b) Report issues to the CentralSquare Support Portal.
c) Review and sign off on the TCR for documenting any stops and restarts of the Reliability Period.
d) Approve and return the TCR documenting completion of the Reliability Period of the Subsystem(s).
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 74
8 PROJECT CLOSURE
8.1 Overview
Project closure activities commence when all project deliverables have been completed.
Support of systems and subsystems will be transitioned to CentralSquare’s Support and monitored per the Support Agreement.
Major Task Description
Post Go-Live Project
Deliverables
Once complete, ensure CentralSquare Project Manager will provide TCR to 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.
8.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 Customer Support Department.
c) Provide continued support based on terms of Agreement.
8.1.2. Customer Responsibilities
a) Provide approval of final Project TCRs within ten (10) business days. b) Process payment of final invoices.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 75
9 Appendix A - Contracted Modifications to Standard CentralSquare Products
There are no product modifications proposed for this project.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 76
10 Appendix B - Standard CentralSquare Interfaces
The scope of functionality for these standard interfaces is limited to 1) the capability of the CentralSquare System being interfaced and 2) the capabilities of the external system being interfaced.
Descriptions of each of the standard interfaces below will become the basis for the scope of detailed requirements, described in the FDD. Any changes in the requirements documented and approved in the System FDDs are subject to a Change Order.
Standard Interfaces
Standard Interfaces are included in the Agreement and listed in this SOW. If not explicitly listed in the Agreement, the Interface will not be installed and supported.
CAD:
Standard Interface Description
Interface Name Standard ANI/ALI Interface
Interface Description The CAD Enterprise E911, ANI/ALI Interface is a Standard Interface provided and implemented by a CentralSquare
Systems Engineer. This Interface provides a one-way transfer and processing of data from the E911 Controller of the phone system to CAD Enterprise using one of the two available types of package structures: fixed position and delimited fields. The Interface is configurable to process various formats of ANI/ALI data streams—to include certain formats of TTY/TDD
emergency calls.
Vendor VIPER – Intrado
Subsystem CAD
Direction Import
Interface Document Name OSD - Standard ANIALI Interface.pdf Instances Contracted Production\Test
Required for Go Live Yes
Project Management Guidance The CentralSquare 911 Technical Services Team will also need to be scheduled to reconfigure the CentralSquare 911 System for this Interface.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 77
Standard Interface Description
Interface Name Enterprise CAD Axon Evidence.com Data Extract Interface Description CentralSquare will provide a SQL view and login that allows Axon to connect and query that view in order to obtain
incident information such as Event ID, Address, Problem Nature, Responder information, Incident Disposition, and both dispatch and cleared call times.
Vendor Axon
Subsystem CAD
Direction Export
Interface Document Name This interface does not have a customer facing OSD.
Instances Contracted Production (This SQL integration is only available in Production)
Required for Go Live Yes
Standard Interface Description
Interface Name Unify CAD-to-CAD Interface
Interfaced CAD type CentralSquare Cloud Hub (Confire)
Interface Description Unify™ provides real-time information sharing between multiple Computer Aided Dispatch (CAD) systems connected to a CentralSquare Hub by constantly and automatically
updating call and unit information directly in each connected CAD system.
Third Party Vendor CentralSquare
Subsystem CAD
Direction Bi-directional
Interface Document Name n/a
Instances Contracted Production
Required for Go Live Yes
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 78
Standard Interface Description
Interface Name Standard ASAP Interface
Interface Description The Automated Secure Alarm Protocol (ASAP) is an American National Standard developed jointly by APCO and The
Monitoring Association and approved by the American
National Standards Institute. NLETS is a partner in the program and uses its systems to provide a data bridge between both systems. Using ASAP, Central Station alarm companies such as Vector Security, Rapid Response, and ADT can transmit alarm data electronically to Central Square’s Inform CAD, reducing the potential for human error and call volume, and results in a decreased response time for Calls for Service.
Third Party Vendor The Monitoring Association (TMA)
Subsystem CAD
Direction Import
Interface Document Name OSD – ASAP Standard Interface.pdf Instances Contracted Production\Test
Required for Go Live Yes
Standard Interface Description
Interface Name CAD Enterprise API
Interface Description The CAD Enterprise API is built to offer developers at agencies, partners, or approved third parties, the ability to integrate to CAD Enterprise or build custom modules. The API provides direct integrations into all the CAD modules and components utilizing a proprietary solution.
Third Party Vendor N/A
Subsystem CAD
Direction Bidirectional
Interface Document Name N/A
Instances Contracted Production\Test
Required for Go Live Yes
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 79
Standard Interface Description
Interface Name Enterprise CAD RapidSOS Interface
Interface Description The standard RapidSOS interface is a service-based interface which works with the RapidSOS API. The API provides the ability for connecting clients to query the RapidSOS
Clearinghouse server over public networks only when using TLS and tightly controlled API keys. The API keys are used during the query process to authenticate the requestor to an agency that is authorized to retrieve caller location data.
The Clearinghouse contains the information of callers that have:
1. The technical ability to deliver their location information to the Clearinghouse.
2. Placed a 911 call.
The RapidSOS Clearinghouse server interfaces with CAD
through a host server using a REST Web Service (HTTPS). Once an Incident ID is assigned to a call incident that was created using ANI/ALI data, the Interface will query the Clearinghouse using the received ANI and return the location for that caller (if a location is available). Workflows on assigning an Incident ID to a call varies between agencies and will affect how this interface initially queries the Clearinghouse.
Vendor RapidSOS
Subsystem CAD
Direction Import
Interface Document Name OSD - Standard RapidSOS Interface.pdf Instances Contracted Production
Required for Go Live Yes
Records:
Standard Interface Description
Interface Name Standard Axon Evidence.com Integration
Interface Description The CentralSquare Axon Evidence.com integration monitors the Records system for new cases as they are created from a Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 80
CAD Call for Service, and automatically generates hyperlinks to videos in the Evidence.com system. These hyperlinks will appear in the case attachments section in Records. This interface assumes Calls for Services are sent to the Records system and that the CAD system informs the Axon system of the call numbers. If deployed with Enterprise CAD and Records this requires the Enterprise CAD Axon interface to also be deployed.
Vendor Axon
Subsystem Records
Direction Import
Interface Document Name OSD - Axon Evidence.com Interface v1.4.pdf Instances Contracted Production\Test
Required for Go Live Yes
Standard Interface Description
Interface Name Standard LexisNexis DORS Incident Importer (Coplogic)
Interface Description The CentralSquare LexisNexis Desk Officer Reporting System (DORS) Interface receives data from police incident reports publicly submitted using the DORS system, and once approved by DORS, the report data is published to Records.
This is a unidirectional importer interface that receives and ingests data from police incident reports publicly submitted using the DeskOfficer Online Reporting System (DORS)
provided by LexisNexis Coplogic. This is designed to eliminate redundant entry of data from citizen-generated Police Incident Reports.
Once a report is reviewed and approved through DORS, the DORS system will send report data to the CentralSquare API.
The incoming data is consumed and imported into the incident module as an incident report or summary in Records
Enterprise.
Vendor LexisNexis
Subsystem Records
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 81
Direction Import
Interface Document Name OSD - Records Enterprise - Lexis Nexis (Coplogic) Incident Importer Integration v1.1
Instances Contracted Production\Test
Required for Go Live Yes
Standard Interface Description
Interface Name Standard Multi-Module Publisher
Interface Description The CentralSquare Multi-Module Publisher Interface (the “Interface”) is a unidirectional interface. It will publish Incident, Arrest, Citation, Field Interview and Crash data from Records Enterprise via XML files in CentralSquare’s standard format to the network file share.
Vendor LexisNexis AVCC
Subsystem Records
Direction Export
Interface Document Name OSD - Enterprise RMS Multi-Module Publisher Interface v1.2.pdf
Instances Contracted Production\Test
Required for Go Live Yes
Standard Interface Description
Interface Name Standard Crash Publisher
Interface Description The CentralSquare Crash Interface (the “Interface”) is a unidirectional interface. It will publish Crash data from Enterprise RMS via XML files in CentralSquare’s standard format, to the configured network file share.
Vendor Buy Crash
Subsystem Records
Direction Export
Interface Document Name OSD - Standard Crash Publisher.pdf Instances Contracted Production\Test
Required for Go Live Yes
Interface Name Standard Crossroads Citation Importer (CA) Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 82
Interface Description The CentralSquare Crossroads Citation Importer Interface (the “Interface”) is a unidirectional interface. It will import Citation data from the Crossroads system into Records Enterprise.
The Crossroads system will supply data to a network file share formatted as a fully documented XML file that aligns to the CentralSquare Records Enterprise schema format.
Vendor Crossroads
Subsystem Records
Direction Import
Interface Document Name OSD - Crossroads Citation Importer - California v1.1.pdf Instances Contracted Production\Test
Required for Go Live Yes
Interface Name Standard Crossroads Crash Importer (CA)
Interface Description The Crossroads Crash Importer is a unidrectional import of crash data from the Crossroads system into Records
Enterprise. The Crossroads system will supply data to a network file share formatted as a fully documented XML file that aligns to the CentralSquare Records Enterprise schema format. The interface will automatically detect the file in and transform the data and insert it into the Records Enterprise system as a crash record. The interface also includes the import of attachments. The attachment must include a
filename extension and media in order to import.
Vendor Crossroads
Subsystem Records
Direction Import
Interface Document Name OSD - Crossroads Crash Importer Interface - California v1.1.pdf Instances Contracted Production\Test
Required for Go Live Yes
Interface Name Standard CrimeTracer (Coplink) Publisher Interface Description The CentralSquare Publisher Interface (the “Interface”) is a unidirectional interface. It will publish Arrest, Citation, Crash, Field Interview, Incident and Crashdata from Enterprise RMS via XML files to a network file share.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 83
The format of the published XML file will be a CentralSquare designated standard that aligns with the Enterprise RMS Data Model (See Section 4.0 Supplemental Documentation).
Vendor CrimeTracer\Coplink
Subsystem Records
Direction Export
Interface Document Name OSD - Coplink Publisher
Instances Contracted Production\Test
Required for Go Live Yes
Interface Name Standard LinX Publisher
Interface Description The CentralSquare LInX Publisher Interface (the “Interface”) is a unidirectional interface. It will publish Incident, Arrest, Crash, Citation, Field Interview data from Records Enterprise via XML files to the network file share.
If XML output is configured, report attachments will be embedded in the output file. The maximum attachment file size will be configured in the Publisher Framework to ensure optimal operation of the interface.
The format of the published XML file will align with the Records Enterprise. (See Supplemental Documentation).
Vendor LinX
Subsystem Records
Direction Export
Interface Document Name OSD - Law Enforcement Information Exchange (LInX) Publisher v1.2.pdf
Instances Contracted Production\Test
Required for Go Live Yes
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 84
Integrations:
Standard Integration Description
Integration Name CAD/Records Integration - Calls for Service Integration Description CentralSquare’s Calls for Service Integration is included in the engagement when both CAD and Records Enterprise systems are in play. The integration sends CAD calls for service to the Records API, which processes them into the Records calls for Service module.
Vendor CentralSquare
Subsystem CAD\Records
Direction Export\Import (CAD to Records)
Integration Document Name This is CentralSquare default functionality. Documentation on the Calls for Services module is included in the Records Administration and user manuals. Documentation on the
integration is included in the Enterprise Integration User Guide Instances Contracted All
Required for Go Live Yes
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 85
11 Appendix C - Custom CentralSquare Interfaces
The scope of functionality for custom interfaces is limited to 1) the capability of the CentralSquare System being interfaced and 2) the Application Programming Interface (API) capabilities of the external system being interfaced, and 3) what has been defined and approved in the Interface FDD. The approved FDD for each custom Interface is the basis for the scope of detailed requirements as well as testing and acceptance of the Interface. Any subsequent changes to approved FDDs are subject to Change Order and may impact the project timeline.
Any post-approval changes to the requirements documented in the system OSDs or other documents are subject to a Change Order.
Custom Interfaces
Custom Interfaces are included in the Agreement and listed in this SOW. If not explicitly listed in the Agreement, the Interface will not be installed and supported.
No Custom Interfaces are included in this engagement.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 86
12 Appendix D - Message Switch
The CentralSquare Message Switch is a component of the CentralSquare Suite which allows query and response transactions between CentralSquare Suite applications, the State, and some third-party data sources. CentralSquare Message Switch is a standalone application that can be accessed from any web application, or within a CentralSquare products, to centralize inquires to state switch systems, internal systems and/or other providers while reducing user interactions and data entry workflows.
A Message Switch Provider is equivalent to a data source (such as a CentralSquare component like Records Enterprise, the State, or a SQL database).
Message Switch Providers use Transactions to query the data source.
A Message Switch Transaction can be considered the equivalent of an individual query or a combination (combo query which queries multiple Providers). Examples of individual queries would be Person by Name or Driver’s License Number Transaction for the Provider Records Enterprise, or a Message key Transaction to the Provider State Justice Switch, or a Type of SQL Query to an external SQL database for a custom provider). Transactions are rolled up under each Provider. An example of a combination query would be a Transaction defined as a Combination Query of a Person query on both a State Provider and a SQL custom transaction (e.g., a Person by Name query which searches both the State, and an external SQL Data Source).
Standard transactions are included in the project, subject to applicable access. Standard queries can be performed via the Enterprise suite applications graphical user interfaces as documented.
The list of Message Switch Providers and associated Transactions included in this Agreement are as follows:
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 87
Standard Providers:
Provider: Records Enterprise
Standard Records Enterprise Transactions:
Category Transaction Name
Admin\Other Free Form
Gun Gun Inquiry
Vehicle Vehicle Inquiry
Admin\Other Location Inquiry
Person Person Inquiry
Article Property Inquiry
Provider: CAD Enterprise
Standard CAD Enterprise Transactions:
Category Transaction Name
Admin\Other CAD Incident Inquiry
Person CAD Person Inquiry
Article CAD Property Inquiry
Vehicle CAD Vehicle Inquiry
Gun CAD Weapon Inquiry
Vehicle Query Tow Request
Person Query BOLO Person
Vehicle Query BOLO Vehicle
Provider: State Justice Switch (ASAFE) via San Bernardino County Standard State Justice Switch Transactions (State/NLETS/NCIC transactions)
For new State implementations where CentralSquare has not yet developed standard transactions, the Customer is responsible for providing State documentation for review by CentralSquare Product Management to identify standard state transactions.
Transactions do not by default include record entry, modification, or update (Cancel, Clear, Locate) functionality. This functionality is available only if CentralSquare develops the queries as custom transactions as part of the Agreement.
Note: If at any time San Bernardino replaces their Tiburon CAD system, a replacement State CLETS connection will need to be purchased.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 88
Standard State Justice Switch Transactions
Category Message Key Transaction Name
Person SNM2 San Bernardino County Person Query by Number Person SNM1 San Bernardino County Person Query by Name
Person SNS1 San Bernardino County Person Query
AdminOther Free Form Clets Transaction
AdminOther E CLETS Emergency Administrative Message
AdminOther N CLETS Administrative Message
AdminOther TQ ORION File Query
AdminOther LEOFA Law Enforcement Officer Flying Armed NLETS Message AdminOther Free Form NLETS Transaction
AdminOther Free Form NCIC Transaction
Article TCAA Test Clear Property - Group Record
Article CAA Clear Property - Group Record
Article EAA Enter Property - Group Record
Article CSS Serialized Security Clear
Article EPN Enter Non-Serialized Pawn Property
Article EP Enter Pawn Property
Article ESS Serialized Security Entry
Article ES Single Security Entry
Article LSS Serialized Security Locate
Article MSS Serialized Security Modify
Article MS Single Security Modify
Article XSS Serialized Securities Cancel
Article XS Single Security Cancel
Article LS Single Security Locate
Article CS Single Security Clear
Article QAK Single Article Inquiry - With Routing Indicator Article QAH Single Article Inquiry - With Pawn Records
Article QAM Single Article Inquiry with Mailed Printout Article TCA Test Clear Property - Single Record
Article TEA Test Enter Property
Article YRSA CLETS Hit Confirmation Response For Stolen Article Article YQSA CLETS Hit Confirmation Request For Stolen Article Article TLAA Test CLETS Locate Property with AID
Article TLA Test CLETS Locate Property
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 89
Article TMAA Test CLETS Modify Property With AID
Article TMA Test CLETS Modify Property
Article TQAB Test Single Article Inquiry - All Records
Article TQAN Test Single Article Inquiry By Name
Article TQA Test Single Article Inquiry
Article TQS Test Single Security Inquiry
Article TRLAA Test CLETS Locate Property NCIC With Modifier Article TRLA Test CLETS Locate Property NCIC
Article LAA Locate Property - Group Record
Article MAA Modify Property - Group Record
Article CA Clear Property - Single Record
Article EA Enter Property - Single Record
Article LA Locate Property - Single Record
Article QAN Single Article Inquiry By Name
Article QA Single Article Inquiry
Article QS Single Security Inquiry
Article R.LAA NCIC Locate Property - Group Record
Article MA Modify Property - Single Record
Article QAB Single Article Inquiry - All Records
Article R.LA NCIC Locate Property - Single Record
Article YQSA NLETS Hit Confirmation Request For Stolen Article Article YRSA NLETS Hit Confirmation Response For Stolen Article Gun TEG Test Enter Historical Firearm Record
Gun TEG Test Enter Evidence And Crime Firearm
Gun EG Enter Evidence And Crime Firearm
Gun EG Enter Historical Firearm Record
Gun FQN Mental Health Firearm Prohibition Inquiry By Number Gun FQP Mental Health Firearm Prohibition Inquiry By Record Number Gun FQA Mental Health Firearm Prohibition Inquiry By Name Gun CG Clear Firearm
Gun QPO Query NCIC Protection Order File
Gun R.QG Gun Inquiry NCIC Only
Gun QGMX Gun Inquiry with Mailed Printout Exact Spelling Gun QGM Gun Inquiry with Mailed Printout
Gun QGK Gun Inquiry with Routing Indicator
Gun TEG Test Enter Law Enforcement Firearm
Gun YRSG CLETS Hit Confirmation Response For Stolen Gun Gun YQSG CLETS Hit Confirmation Request For Stolen Gun
Gun TLG Test CLETS Locate Firearm
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 90
Gun TMG Test Modify Firearm
Gun TRLG Test CLETS Locate Firearm NCIC Only
Gun TXG Test CLETS Cancel Firearm
Gun EG Enter Law Enforcement Firearm
Gun LG CLETS Locate Firearm
Gun QGHX Gun Inquiry with History Exact Spelling
Gun QG Gun Inquiry
Gun MG Modify Firearm
Gun QGB Gun Inquiry with LE and History
Gun R.LG CLETS Locate Firearm NCIC Only
Gun XG CLETS Cancel Firearm
Gun YRSG NLETS Hit Confirmation Response For Stolen Gun Person EMP CLETS Enter Missing Persons
Person MMP CLETS Modify Missing Persons
Person EGVO CLETS Enter Gun Violence Restraining Order
Person IN DMV Query Name Index
Person QRP Query CARPOS Restrained Person
Person QRRK Query CARPOS Abbreviated Response
Person QRRH Query CARPOS History
Person QRR1 Query CARPOS Violation Messages
Person QWK Wanted Person Inquiry with Routing Indicator Person R.QM Query Missing Person NCIC Only
Person QWA Wanted Person Inquiry Abbreviated Response
Person TEMP Test CLETS Enter Missing Persons
Person YRWP CLETS Hit Confirmation Response For Wanted Person Person YRMP CLETS Hit Confirmation Response For Missing Person Person YQWP CLETS Hit Confirmation Request For Wanted Person Person YQMP CLETS Hit Confirmation Request For Missing Person Person TEWR Test CLETS Enter Wanted Person Warrant Issued Person TLMP Test CLETS Locate Missing Person
Person TMMSD Test CLETS Modify Missing Person Suspect Description Person TQHA Test CLETS Query Criminal History By Alpha
Person TQHC Test CLETS Query Criminal History By CII
Person TQHN Test CLETS Query Criminal History By Number Person TQM Test CLETS Query Missing Person
Person TQRR Test Query CARPOS Full Response
Person TRLM Test CLETS Locate Missing Person NCIC Only
Person EUP Unidentified Person Entry
Person QW Wanted Person Inquiry
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 91
Person EWR Enter Wanted Person
Person IN DMV Query Drivers License By Name
Person ID DMV Query Drivers License By Number
Person LCA Supervised Release File Contact Message
Person LMP CLETS Locate Missing Person
Person MMSD CLETS Modify Missing Person Suspect Description Person MWR Modify Wanted Person
Person QAR SRF Individual Record Inquiry - Arson Registrant Person QCA SRF Individual Record Inquiry - CDC Parole
Person QCR SRF Individual Record Inquiry - Career Criminal Person QFR SRF Individual Record Inquiry - Federal Probation Person QHA CLETS Query Criminal History By Alpha
Person QHC CLETS Query Criminal History By CII
Person QHN CLETS Query Criminal History By Number
Person QPR SRF Individual Record Inquiry - County Probation Person QRR Query CARPOS Full Response
Person QSR SRF Individual Record Inquiry - Sex Registrant Person QVCK SRF Inquiry - Abbreviated Response
Person QYA SRF Individual Record Inquiry - CYA Parole
Person QM CLETS Query Missing Person
Person QVC SRF Inquiry - Full Response
Person R.LM CLETS Locate Missing Person NCIC Only
Person R.QR Full III Criminal History Record Inquiry
Person KQ NLETS Driver History Query
Person DQ NLETS Driver Record Query
Person DNQ NLETS Driver History Query By Name Only
Person UQ NLETS Canadian Driver Record Query
Person WQ NLETS Canadian Person File Query
Person IQ NLETS Criminal History Identity Query
Person FQ NLETS Full Criminal History Query
Person YQMP NLETS Hit Confirmation Request For Missing Person Person YQPO NLETS Hit Confirmation Request For Protective Order Person YQWP NLETS Hit Confirmation Request For Wanted Person Person YRWP NLETS Hit Confirmation Response For Wanted Person Vehicle BQ Query Boat Registration
Vehicle IN DMV Query Vehicle Registration By Owner
Vehicle QBK Boat Inquiry with Routing Indicator
Vehicle R.QB Boat Inquiry NCIC Only
Vehicle TCBA Test CLETS Clear Boat with AID
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 92
Vehicle TCB Test CLETS Clear Boat
Vehicle TCVA Test CLETS Clear Vehicle with AID
Vehicle TCV Test CLETS Clear Vehicle
Vehicle YRSV CLETS Hit Confirmation Response For Stolen Or Felony Vehicle Vehicle YRSP CLETS Hit Confirmation Response For Stolen Part Vehicle YRSL CLETS Hit Confirmation Response For Stolen License Plate Vehicle YRSB CLETS Hit Confirmation Response For Stolen Boat Vehicle YQSP CLETS Hit Confirmation Request For Stolen Part Vehicle YQSL CLETS Hit Confirmation Request For Stolen License Plate Vehicle YQSV CLETS Hit Confirmation Request For Stolen Or Felony Vehicle Vehicle YQSB CLETS Hit Confirmation Request For Stolen Boat Vehicle TEVPR Test CLETS Enter Vehicle Part Stolen
Vehicle TLBA Test CLETS Locate Boat with AID
Vehicle TLB Test CLETS Locate Boat
Vehicle TQB Test QB - Boat Inquiry
Vehicle TQV Test CLETS Stolen or Felony Vehicle Inquiry Vehicle TRLB Test CLETS Locate Boat NCIC
Vehicle TRLL Test CLETS Locate License Plate NCIC
Vehicle CBA CLETS Clear Boat with AID
Vehicle CVA CLETS Clear Vehicle with AID
Vehicle LBA CLETS Locate Boat with AID
Vehicle R.QV Stolen or Felony Vehicle Inquiry NCIC Only Vehicle CB CLETS Clear Boat
Vehicle CV Clear Vehicle
Vehicle EVPR CLETS Enter Vehicle Part Stolen
Vehicle IV DMV Query Vehicle Registration
Vehicle LB CLETS Locate Boat
Vehicle QB Boat Inquiry
Vehicle QV Stolen or Felony Vehicle Inquiry
Vehicle R.LB CLETS Locate Boat NCIC
Vehicle R.LL CLETS Locate License Plate NCIC
Vehicle GQ Query Aircraft Registration
Vehicle RNQ NLETS Vehicle Registration Query By Name Only Vehicle RQ NLETS Vehicle Registration Query
Vehicle RQG NLETS Regional Vehicle Registration Query
Vehicle SQ NLETS Snowmobile Registration Query
Vehicle XQ NLETS Canadian Vehicle Registration Query
Vehicle VQ NLETS Canadian Vehicle File Query
Vehicle MQ Hazardous Materials Query
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 93
Vehicle YQSB NLETS Hit Confirmation Request For Stolen Boat Vehicle YQSL NLETS Hit Confirmation Request For Stolen License Plate Vehicle YQSP NLETS Hit Confirmation Request For Stolen Part Vehicle YQSV NLETS Hit Confirmation Request For Stolen Or Felony Vehicle Vehicle YRSB NLETS Hit Confirmation Response For Stolen Boat Vehicle YRSL NLETS Hit Confirmation Response For Stolen License Plate Vehicle YRSP NLETS Hit Confirmation Response For Stolen Part Vehicle YRSV NLETS Hit Confirmation Response For Stolen Or Felony Vehicle
Provider: State Justice Switch (CLETS)
Standard State Justice Switch Transactions (State/NLETS/NCIC transactions)
For new State implementations where CentralSquare has not yet developed standard transactions, the Customer is responsible for providing State documentation for review by CentralSquare Product Management to identify standard state transactions.
Transactions do not by default include record entry, modification, or update (Cancel, Clear, Locate) functionality. This functionality is available only if CentralSquare develops the queries as custom transactions as part of the Agreement.
Category Message Key Transaction Name
AdminOther Free Form NLETS Transaction
AdminOther Free Form NCIC Transaction
AdminOther E CLETS Emergency Administrative Message
AdminOther LEOFA Law Enforcement Officer Flying Armed NLETS Message AdminOther N CLETS Administrative Message
AdminOther TQ ORION File Query
AdminOther Free Form Clets Transaction
Article CA Clear Property - Single Record
Article CAA Clear Property - Group Record
Article CS Single Security Clear
Article CSS Serialized Security Clear
Article EA Enter Property - Single Record
Article EAA Enter Property - Group Record
Article EP Enter Pawn Property
Article EPN Enter Non-Serialized Pawn Property
Article ES Single Security Entry
Article ESS Serialized Security Entry
Article LA Locate Property - Single Record
Article LAA Locate Property - Group Record
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 94
Article LS Single Security Locate
Article LSS Serialized Security Locate
Article MA Modify Property - Single Record
Article MAA Modify Property - Group Record
Article MS Single Security Modify
Article MSS Serialized Security Modify
Article QA Single Article Inquiry
Article QAB Single Article Inquiry - All Records
Article QAH Single Article Inquiry - With Pawn Records
Article QAK Single Article Inquiry - With Routing Indicator Article QAM Single Article Inquiry with Mailed Printout Article QAN Single Article Inquiry By Name
Article QS Single Security Inquiry
Article R.LA NCIC Locate Property - Single Record
Article R.LAA NCIC Locate Property - Group Record
Article TCA Test Clear Property - Single Record
Article TCAA Test Clear Property - Group Record
Article TEA Test Enter Property
Article TLA Test CLETS Locate Property
Article TLAA Test CLETS Locate Property with AID
Article TMA Test CLETS Modify Property
Article TMAA Test CLETS Modify Property With AID
Article TQA Test Single Article Inquiry
Article TQAB Test Single Article Inquiry - All Records
Article TQAN Test Single Article Inquiry By Name
Article TQS Test Single Security Inquiry
Article TRLA Test CLETS Locate Property NCIC
Article TRLAA Test CLETS Locate Property NCIC With Modifier Article XS Single Security Cancel
Article XSS Serialized Securities Cancel
Article YQSA CLETS Hit Confirmation Request For Stolen Article Article YQSA NLETS Hit Confirmation Request For Stolen Article Article YRSA CLETS Hit Confirmation Response For Stolen Article Article YRSA NLETS Hit Confirmation Response For Stolen Article Gun CG Clear Firearm
Gun EG Enter Evidence And Crime Firearm
Gun EG Enter Historical Firearm Record
Gun EG Enter Law Enforcement Firearm
Gun FQA Mental Health Firearm Prohibition Inquiry By Name Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 95
Gun FQN Mental Health Firearm Prohibition Inquiry By Number Gun FQP
Mental Health Firearm Prohibition Inquiry By Record
Number
Gun LG CLETS Locate Firearm
Gun MG Modify Firearm
Gun QG Gun Inquiry
Gun QGB Gun Inquiry with LE and History
Gun QGHX Gun Inquiry with History Exact Spelling
Gun QGK Gun Inquiry with Routing Indicator
Gun QGM Gun Inquiry with Mailed Printout
Gun QGMX Gun Inquiry with Mailed Printout Exact Spelling Gun QPO Query NCIC Protection Order File
Gun R.LG CLETS Locate Firearm NCIC Only
Gun R.QG Gun Inquiry NCIC Only
Gun TEG Test Enter Historical Firearm Record
Gun TEG Test Enter Evidence And Crime Firearm
Gun TEG Test Enter Law Enforcement Firearm
Gun TLG Test CLETS Locate Firearm
Gun TMG Test Modify Firearm
Gun TRLG Test CLETS Locate Firearm NCIC Only
Gun TXG Test CLETS Cancel Firearm
Gun XG CLETS Cancel Firearm
Gun YQSG CLETS Hit Confirmation Request For Stolen Gun
Gun YRSG CLETS Hit Confirmation Response For Stolen Gun Gun YRSG NLETS Hit Confirmation Response For Stolen Gun Person DNQ NLETS Driver History Query By Name Only
Person DQ NLETS Driver Record Query
Person EGVO CLETS Enter Gun Violence Restraining Order
Person EMP CLETS Enter Missing Persons
Person EUP Unidentified Person Entry
Person EWR Enter Wanted Person
Person FQ NLETS Full Criminal History Query
Person ID DMV Query Drivers License By Number
Person IN DMV Query Name Index
Person IN DMV Query Drivers License By Name
Person IQ NLETS Criminal History Identity Query
Person KQ NLETS Driver History Query
Person LCA Supervised Release File Contact Message
Person LMP CLETS Locate Missing Person
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 96
Person MMP CLETS Modify Missing Persons
Person MMSD CLETS Modify Missing Person Suspect Description Person MWR Modify Wanted Person
Person QAR SRF Individual Record Inquiry - Arson Registrant Person QCA SRF Individual Record Inquiry - CDC Parole
Person QCR SRF Individual Record Inquiry - Career Criminal Person QFR SRF Individual Record Inquiry - Federal Probation Person QHA CLETS Query Criminal History By Alpha
Person QHC CLETS Query Criminal History By CII
Person QHN CLETS Query Criminal History By Number
Person QM CLETS Query Missing Person
Person QPR SRF Individual Record Inquiry - County Probation Person QRP Query CARPOS Restrained Person
Person QRR Query CARPOS Full Response
Person QRR1 Query CARPOS Violation Messages
Person QRRH Query CARPOS History
Person QRRK Query CARPOS Abbreviated Response
Person QSR SRF Individual Record Inquiry - Sex Registrant Person QVC SRF Inquiry - Full Response
Person QVCK SRF Inquiry - Abbreviated Response
Person QW Wanted Person Inquiry
Person QWA Wanted Person Inquiry Abbreviated Response
Person QWK Wanted Person Inquiry with Routing Indicator Person QYA SRF Individual Record Inquiry - CYA Parole
Person R.LM CLETS Locate Missing Person NCIC Only
Person R.QM Query Missing Person NCIC Only
Person R.QR Full III Criminal History Record Inquiry
Person TEMP Test CLETS Enter Missing Persons
Person TEWR Test CLETS Enter Wanted Person Warrant Issued Person TLMP Test CLETS Locate Missing Person
Person TMMSD Test CLETS Modify Missing Person Suspect Description Person TQHA Test CLETS Query Criminal History By Alpha
Person TQHC Test CLETS Query Criminal History By CII
Person TQHN Test CLETS Query Criminal History By Number Person TQM Test CLETS Query Missing Person
Person TQRR Test Query CARPOS Full Response
Person TRLM Test CLETS Locate Missing Person NCIC Only
Person UQ NLETS Canadian Driver Record Query
Person WQ NLETS Canadian Person File Query
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 97
Person YQMP CLETS Hit Confirmation Request For Missing Person Person YQMP NLETS Hit Confirmation Request For Missing Person Person YQPO NLETS Hit Confirmation Request For Protective Order Person YQWP CLETS Hit Confirmation Request For Wanted Person Person YQWP NLETS Hit Confirmation Request For Wanted Person Person YRMP CLETS Hit Confirmation Response For Missing Person Person YRWP CLETS Hit Confirmation Response For Wanted Person Person YRWP NLETS Hit Confirmation Response For Wanted Person Vehicle BQ Query Boat Registration
Vehicle CB CLETS Clear Boat
Vehicle CBA CLETS Clear Boat with AID
Vehicle CV Clear Vehicle
Vehicle CVA CLETS Clear Vehicle with AID
Vehicle EVPR CLETS Enter Vehicle Part Stolen
Vehicle GQ Query Aircraft Registration
Vehicle IN DMV Query Vehicle Registration By Owner
Vehicle IV DMV Query Vehicle Registration
Vehicle LB CLETS Locate Boat
Vehicle LBA CLETS Locate Boat with AID
Vehicle MQ Hazardous Materials Query
Vehicle QB Boat Inquiry
Vehicle QBK Boat Inquiry with Routing Indicator
Vehicle QV Stolen or Felony Vehicle Inquiry
Vehicle R.LB CLETS Locate Boat NCIC
Vehicle R.LL CLETS Locate License Plate NCIC
Vehicle R.QB Boat Inquiry NCIC Only
Vehicle R.QV Stolen or Felony Vehicle Inquiry NCIC Only Vehicle RNQ NLETS Vehicle Registration Query By Name Only Vehicle RQ NLETS Vehicle Registration Query
Vehicle RQG NLETS Regional Vehicle Registration Query
Vehicle SQ NLETS Snowmobile Registration Query
Vehicle TCB Test CLETS Clear Boat
Vehicle TCBA Test CLETS Clear Boat with AID
Vehicle TCV Test CLETS Clear Vehicle
Vehicle TCVA Test CLETS Clear Vehicle with AID
Vehicle TEVPR Test CLETS Enter Vehicle Part Stolen
Vehicle TLB Test CLETS Locate Boat
Vehicle TLBA Test CLETS Locate Boat with AID
Vehicle TQB Test QB - Boat Inquiry
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 98
Vehicle TQV Test CLETS Stolen or Felony Vehicle Inquiry Vehicle TRLB Test CLETS Locate Boat NCIC
Vehicle TRLL Test CLETS Locate License Plate NCIC
Vehicle VQ NLETS Canadian Vehicle File Query
Vehicle XQ NLETS Canadian Vehicle Registration Query
Vehicle YQSB CLETS Hit Confirmation Request For Stolen Boat Vehicle YQSB NLETS Hit Confirmation Request For Stolen Boat Vehicle YQSL CLETS Hit Confirmation Request For Stolen License Plate Vehicle YQSL NLETS Hit Confirmation Request For Stolen License Plate Vehicle YQSP CLETS Hit Confirmation Request For Stolen Part Vehicle YQSP NLETS Hit Confirmation Request For Stolen Part Vehicle YQSV CLETS Hit Confirmation Request For Stolen Or Felony Vehicle Vehicle YQSV
NLETS Hit Confirmation Request For Stolen Or Felony
Vehicle
Vehicle YRSB CLETS Hit Confirmation Response For Stolen Boat Vehicle YRSB NLETS Hit Confirmation Response For Stolen Boat Vehicle YRSL CLETS Hit Confirmation Response For Stolen License Plate Vehicle YRSL NLETS Hit Confirmation Response For Stolen License Plate Vehicle YRSP CLETS Hit Confirmation Response For Stolen Part Vehicle YRSP NLETS Hit Confirmation Response For Stolen Part Vehicle YRSV
CLETS Hit Confirmation Response For Stolen Or Felony
Vehicle
Vehicle YRSV
NLETS Hit Confirmation Response For Stolen Or Felony
Vehicle
Custom Transactions:
No custom Transactions are scoped.
Custom Providers:
Custom Providers allow the ability to access additional records management systems, warrant/court systems, or other accessible external databases. It is a requirement to have connectivity from the CentralSquare Message Switch to the RDBMS system and at least a login with Read access to the schema. A Subject Matter Expert in the schema will be required to either provide the SQL queries needed, and preferably design Stored Procedures on the third-party database to be used for the Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 99
Transactions. If CentralSquare is contracted to write the queries or design Stored Procedures additional service hours will be needed.
Custom Provider: White Box Archive Reporting Tool (ART) Legacy Vision RMS database with ART Message Switch queries
NOTE: Additional White Box services included in the quote for Message Switch Transactions to the ART database will be defined as part of a Change Order to amend the provider table directly below.
Provider White Box ART (Legacy Vision RMS)
Type SQL
Database Type SQL Server
Transactions Description
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 100
13 Appendix E - Subcontractor Statement of Work
White Box Technologies will be the only subcontractor for this project. Details included in Appendix Z.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 101
14 Appendix J – CentralSquare Connectivity to Enterprise On-Premise systems
Policy
Customer Managed On-Premise Systems
The BeyondTrust/Bomgar and/or SecureLink 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 Section 5.5.6 of the FBI CJIS Security Policy (Remote Access). Use of either of these solutions enable Customer agencies to remain CJIS compliant for purposes of FBI and/or state regulatory agency audits.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 102
15 Appendix Y – Workshop and Training Summary
Training/Go-Live Deliverable Quantity Training(s)/Workshop(s) Included Remote/Onsite CAD Enterprise System Orientation 1 Three (3) day workshop Onsite CAD Enterprise Operational and
Administrative Review (OAR) 1 Three (3) day workshop Onsite CAD Enterprise Administration (CAD
Codefile Management) Training 1 Three (3) day workshop Onsite GIS Link Training 1 Three (3) day training class for a
maximum of four (4) participants. Onsite
CAD Enterprise Response Plan
Workshop 1 Three (3) day workshop Onsite
CAD Enterprise Validation & Readiness
Workshop 1 Three (3) day workshop Onsite
CAD Enterprise SSRS Report Writing 1 Three (3) day workshop Onsite CAD Enterprise Functional Acceptance
Testing 1 Four (4) hour testing event Onsite
CAD Enterprise System Administration
Training 1 Five (5) day workshop Remote
CAD Enterprise Dispatch Supervisor
Training 1 Three (3) day training class Onsite
CAD Enterprise Call Taker/Dispatcher
User Training 2 Two (2) day training class Onsite
CAD/Mobile Enterprise Onsite Go-Live
Support Services 1
Four (4) day Go-Live Support - 2
CentralSquare Consultant(s) per 12-
hour shift. Mon-Thurs | 10am Go-Live
Onsite
CAD Enterprise Post Go-Live
Optimization and Advance
Configuration Workshop
1 Three (3) day training class Onsite
Mobile Enterprise Functional
Acceptance Testing 1 Four (4) hour testing event Onsite Mobile Enterprise Administration
Training 1 Three (3) day training class for a
maximum of three (3) participants. Onsite
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 103
Mobile Enterprise Train-the-Trainer
Training 1 Four (4) hour training class Onsite
Records Enterprise Administration
Review and Training Workshop 1 Three (3) day workshop Onsite Workshop – Incident, Arrest, and Case
Management 1 Three (3) day workshop Onsite
Workshop – Crash, Citation, Other
Events, Field Interview 1 Three (3) day workshop Onsite Workshop – Records
Administration/State Reporting 1 Three (3) day workshop Onsite Workshop – P&E Workshop 1 Three (3) day workshop Onsite Records Enterprise Output Designer
Workshop 1 Three (3) day workshop Onsite
Records Enterprise Report Writing
Training 1 Three (3) day workshop Onsite
Records Enterprise Validation &
Readiness Workshop 1 Three (3) day workshop Onsite
Records Enterprise Functional
Acceptance Testing 1 Three (3) day workshop Onsite
Records Enterprise Train the Trainer -
Field Officers 1 Three (3) day training class Onsite
Records Enterprise End User Training -
Investigations 1 Two (2) day training class Onsite
Records Enterprise End User Training -
Records & State Reporting 2 Two (2) day training class Onsite Records Enterprise Onsite Go-Live
Support Services 1
Four (4) day Go-Live Support - 1
CentralSquare Consultant(s) per 8-
hour shift. Mon-Thurs | 10am Go-Live
Onsite
Records Enterprise Post Go-Live
Optimization and Advance
Configuration Workshop
1 Three (3) day workshop Onsite
System Integration Testing (SIT) 1 Two (2) hour testing event Remote CrimeView Analytics
Administrator/Designer Training 1 Six (6) hour training class Remote Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 104
CrimeView Analytics Train-the-Trainer 1 Two (2) hour training class Remote
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 105
16 Appendix Z – Data Conversions
16.1 CentralSquare CAD Enterprise Data Conversion
16.1.1. Data Conversion Overview
Data conversion is the implementation process of moving data from a legacy system or data files into your CentralSquare software product. Data conversion is a highly collaborative process between Customer and CentralSquare Technologies.
The listed data conversion services and their associated costs are based on CentralSquare’s understanding of Customer's needs and current system. Any modules not explicitly listed in this section are not part of the current project scope and will not be included in implementation. If additional module conversions are required, each one will come at an additional cost based on the scope of the work required for each.
CentralSquare will implement a structured methodology for CAD Enterprise data conversion. Customer is responsible for providing CentralSquare with extracted data in a format that can be used by CentralSquare for import. Formats suitable for import into can include Excel, MDB, CSV, and ODBC access from MS SQL; however, the specific format to be used for this Project should be reviewed between the respective CentralSquare and Customer teams.
The conversion of prior CAD data is a process that involves several steps. CentralSquare develops a data conversion plan to the Customer detailing the data mapping between the legacy System and CentralSquare CAD Enterprise. During this phase of work, CentralSquare will work closely with the appropriate individuals from Customer to map each data element in each legacy application to the appropriate target data element in the CAD Enterprise databases and reflect this information in the data conversion plan.
Generally, there is an initial conversion to bring the data set close to Go-Live, a second conversion just before Go-Live and a last conversion after Go-Live. Each step does not involve a re-conversion of previously converted data. These steps do not include ongoing maintenance of imported data. If the legacy data elements have a relevant counterpart in the target CAD Enterprise databases, CentralSquare can map the data and import it into the CAD Enterprise database structure.
Conversion of Premise and Caution notes can be performed independent from the Prior Incident data. A small sub-set of the data will be initially converted and loaded to validate the process. Upon completion of this test, the Premise and Caution notes data will be converted and imported to the system close to Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 106
Go-Live, as a onetime process. Additions to Premises and Caution notes in the old system, between the time of data conversion and Go-Live will require manually entry by Customer to the new system.
It is imperative that a member of the Customer’s staff be available to support the data conversion effort.
Many operational questions will arise that depend on the data and operational expertise of Customer’s staff.
This process is considered complete once the last set of data has been converted for the new CAD Enterprise system. The Customer is responsible for the validation of the data.
Due to the need for specific knowledge of the Customer’s area, the geo validation process for the converted data is the responsibility of the Customer.
Legacy data conversion will not include conversion of attachments to Premises or Historical Incidents into CentralSquare databases.
CAD Enterprise Data Conversions are scoped per source. Sources and modules within each source are documented below.
Upon Selection CAD Data Conversion will be reviewed and the scope finalized and documented below.
16.1.2. Data Conversion Modules
Modules for conversion are defined in the Sales Order and this Appendix:
Source 1: Rialto Police Department
Source Vendor: VisionAir
Source Database Type: SQL
Module to be Converted Definition of Module
Premise and Caution Notes CAD Premise Info and Caution Notes Incidents Up to Ten (10) years of historical incident data Additional Incidents X Additional years of Incident Data
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 107
16.1.3. Data Conversion Process
The Data Conversion process is the work that drives the configuration and implementation process.
Below are the significant tasks included in this project:
Major Task Description
Schedule CentralSquare and Customer will schedule the Data Conversion Tasks as part of the overall Project Schedule. CentralSquare CAD GIS training and build out of CAD Code Tables are prerequisites to any conversion mapping exercise.
Extraction Customer will extract sample data in a format compatible with conversion and provide to CentralSquare
Configuration
Documentation
CentralSquare will provide a configuration document to the Customer for the Incident Data Conversion Plan.
Review An in-depth review between CentralSquare and Customer SME will be held. This meeting will be recorded, and Customer should be prepared to operate within the UI of the old system to provide examples and context Setup CentralSquare will configure servers and systems needed for the Data Conversion.
Premise and Caution
Note Sample
Conversion
A Small Premise and Caution Note conversion sample will be run to validate the mapping and the conversion process.
Review and Validation A second in-depth review between CentralSquare and Customer SME will be held to review changes to the Incident Data Conversion Plan and validate Premise and Caution sample data.
Bulk Incident Data
Conversion
CentralSquare will bulk convert data into Customer’s Pre-production Archive system approximately two months prior to Go-Live.
Premise and Caution
Note Conversion
Approximately one month prior to Go-Live the Premise and Caution Note conversion is run into Customer’s pre-production system. From this time onward Customer must maintain Premise and Caution notes in their existing production System and the CentralSquare pre-production system Sign Off Customer Signs off on Data Conversion
Go-Live The Final extraction of Incident data and the final Incident delta Data Conversion is run as part of the Go-Live
Final Sign Off Customer signs off on the Final Data conversion
Note: Customer must review and sign off at different intervals to continue the process.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 108
16.1.3.1 CentralSquare Responsibilities
a) Work with Customer to identify, document and implement a comprehensive data conversion. b) Advise on possible conversion options.
c) Advise on project milestone dates and Customer expectations. d) Provide training for Customer on using CentralSquare data mapping tools. e) Work with Customer to limit the number of Go-Live conversion events. f) Perform one or more sample conversions.
g) Provide training for Customer on validating the data conversion for completeness and accuracy. h) Convert legacy data into corresponding elements in the CentralSquare system. (Modifications to the CentralSquare system or database for the purposes of data conversion will be limited or unavailable).
i) Perform final delivery of data conversion.
16.1.3.2 Customer Responsibilities
a) Provide subject matter experts to complete data conversion tasks, including providing expertise in third-party data architecture, providing business processing logic for addressing data conversion and identifying and scheduling appropriate personnel to attend training. b) Provide data dumps in the prescribed format within thirty (30) days of Agreement signing. c) Provide routine data dumps throughout the implementation process. d) If needed, provide a temporary workstation for data conversion personnel. e) If needed, provide UI access to the legacy system or test system for data conversion personnel. f) Ensure the legacy data is “conversion ready,” meaning it is clean (duplicates, typos, missing information, etc. have been corrected).
g) .
h) Configure code values as part of the system build.
i) Take responsibility for costs assessed by the legacy system or any other third party for performing the data extraction as described.
j) Configure code value and complete code value data mapping prior to data conversion processing.
k) Use provided tools to translate (map) code values between your legacy system and your CentralSquare.
l) Manual adjustments by Customer may be required on converted data to make it eligible for state submissions, reports, or to align with new workflow processes. m) Perform manual back entry of data saved after the final data cut if necessary.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 109
n) Perform data validation. Validate data converted is both complete and accurate. Report discrepancies during the implementation process. (System downtime may be required to complete the data conversion process).
o) Use provided tools to report data conversion issues. p) Provide sign off of the converted data in a non-production environment. q) Provide sign off of the converted data set into the production environment.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 110
16.2 CentralSquare Records Enterprise Data Conversion – White Box NOTE: Additional White Box services included in the quote for data conversion will be defined as part of a Change Order.
16.2.1. Property & Evidence Data Conversion
SUMMARY: Conversion of source legacy Property and Evidence data for use in Central Square Enterprise Property and Evidence Modules. According to the availability and completeness of the source data and target modules, all of the fields and tables within the various functional areas will be populated to the fullest extent possible within the parameters outlined below. Where Agency/Rialto Police (Rialto) is referenced below, Central Square will assume the responsibility to work with Rialto to complete the task.
Roles and responsibilities:
Central Square
• Project Manager and System Engineer
o Manage project scope, schedule and performance, coordinate conversion activities with White Box
o Assist with adherence to schedule, and issue resolution. o Inform White Box of issues impacting conversion.
o Report conversion issues to White Box in a timely manner following a delivery, including necessary details to research and resolve.
o Coordinate access for Whitebox to access customer’s environment o Facilitate Task Completion Reports and signatures for each of the billing milestones listed in the payment terms of this agreement.
Rialto Police
• Central Square to facilitate access to Agency Legacy System Subject Matter Expert and IT Support to:
o Provide legacy data files to White Box
o Work with White Box to retrieve data and layout information from legacy system in either CSV, Flat Files with table header layouts or in a portable (e.g. SQL) format o Inform White Box of issues impacting conversion, promptly answer technical and/or business operation questions.
o Review, provide feedback and approve Table Mapping, Field and Code Documents o With WB assistance (if needed) thoroughly review mock conversions per schedule.
Mandatory scheduled review sessions with White Box are required between the first and second iterations that will include all data being populated into the target modules o Provide, generate, and validate source codes to target codes using the White Box online code mapper utility.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 111
White Box
• Project Manager
o Manage project scope, schedule, and performance, coordinate conversion activities with Central Square.
• Data Analyst
o Prepare Table Mapping, Field and Code Documents; deliver to Rialto for review. o Work with Central Square and (as requested by Central Square) to develop the conversion rules and resolve issues identified during mock(s) and final conversion. o Schedule and conduct dedicated screen shares to assist Rialto with code mapping and reviewing of mock data.
• Engineer
o Retrieve and prepare source data and set up other applicable systems. o Build, test, run conversion and deliver converted data to Central Square o Load Converted data into target database for customer testing. Central Square to assist with sync tools/utilities. If Rialto does not agree to White Box access, this responsibility will be for Central Square Data Conversion Engineer.
o Remove Rialto data from White Box Systems 45 days after Go Live.
Assumptions and Constraints:
• This project includes up to three mock iterations and a final go live conversion for RMS Property/Evidence (P/E) consisting of the source data provided to White Box Technologies.
Rialto/Central Square will provide no more than two source data dumps/backups consisting of:
the initial RMS P/E data backups used for building and reviewing the converted data, and a backup used for RMS P/E go live. Any additional backups requested by Central Square/Rialto to be restored will result in a change request. Data must be in either a CSV, flat files with table header layouts or in a portable (e.g. SQL) format
• Data may be provided by Central Square/Rialto using any of the following methods:
Deliver to a secure FTP site, provided by White Box,
Save the files to a file location provided by Central Square or Rialto; provide access for WB to access and retrieve, or Save the files on a hard drive and deliver to White Box • Central Square will provide the code tables populated with Rialto data prior to the 1st iteration to support the data mapping and conversion. White Box will not be creating or building codes or any code tables and is the responsibility of the Agency to validate their codes. All necessary code mapping must be completed prior to the first iteration delivery. If new codes are needed to be added to the target system, these will be identified during the code mapping validation process.
• Images (mugshots/file attachments) included
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 112
• A project schedule will be developed and mutually agreed to during the initiation of this project.
Any delay in the delivery of milestones or related sub-steps to the schedule, which is the responsibility of Central Square or Rialto, can result in a day-for-day delay in subsequent milestones that White Box is responsible for. The period of performance begins from contract signing or a later date specified in the schedule to 30 days after the final scheduled go live. • Following a White Box deliverable, unless otherwise specified, Central Square or Rialto (per schedule) has a set number of business days to report any issues. If White Box receives no response within that time, the deliverable will be considered accepted as delivered and if tied to a billable milestone, deliverable will be invoiced to Central Square. Issues reported after that period of time will be resolved on a case-by-case basis and may or may not be subject to additional charges and / or a change request. Requested changes or issues found after the go live that were the result of not properly reviewing the converted data, will be subject to a change request.
• White Box will not be responsible for de-duplication of legacy data with in-service data, although a Standard Name merge utility can be applied to the conversion. If it is decided that Rialto does want a Name Merge to be done, White box will need the decision in writing signed by both Rialto and Central Square. 100% success rate of duplicate records is not guaranteed. • Addresses that are part of the data conversion cannot be geo verified by White Box. If Geo verification is a requirement for Rialto, Rialto will need to conduct their own Geo verification testing.
• Code, configuration, and maintenance tables will not be populated in the target system by White Box. White Box will not be responsible for deleting any existing data in the configuration database. Any upgrades made to the target database during implementation will be a change request. Any new fields requested to be added after the last mock iteration that have not been reported previously will be a change request.
• Work performed under this Statement of Work is under warranty by White Box for thirty (30) days following delivery of the final conversion. For any issues that are the direct result of a White Box error and found within the 30-day warranty period, WB will fix those errors. Errors or omissions in converted data that result from application, database, source data changes or requested changes to the conversion logic made by Central Square or Rialto following acceptance of any Spec Document, mock conversions, including not properly reviewing the data during the mock iterations or only reviewing partial data, the final go live and found after the 30-day warranty period are not included in this Statement of Work and will be subject to a change
request.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 113
Estimated Key project milestones:
Milestone Responsibility
Deliver Source data and code tables to White Box. Rialto/Central Square Deliver Table Mapping Document White Box
Deliver Code Mapping Utility White Box
Validate Source Codes to Target Codes Rialto
Deliver first mock converted data White Box
Review of Mock Converted data Rialto/Central Square
Deliver second mock converted data White Box
Review of mock converted data Rialto/Central Square
Deliver third mock converted data White Box
Review of mock converted data Rialto/Central Square
Deliver source data for go live Rialto/Central Square Deliver final converted RMS/CAD/JMS data White Box
Cut off for reporting post conversion issues (30 day Warranty Period, after delivery of data for go live) Rialto/Central Square
Source System(s):
• Visionair Property and Evidence Only
• Number of Source Data Tables needing Analysis and Conversion: Up to 12 total source data tables for Property/Evidence, only the most heavily used data tables containing over 1000 records per table are converted. (Lookup tables, code tables, and other source database tables that contain a minimal number of data fields and primarily exist for database normalization purposes do not count against this limit).
• Source data delivered to White Box Technologies: Not received. Other similar project information was used to estimate scope. All assumptions on number of tables being converted from the source databases will need to be verified once receiving copy of source database.
Upon selection, a review of the data and scope will be confirmed to finalize the data conversion deliverable. If any additional data needs to be converted beyond the specified source data table count listed above, additional charges will apply.
Target System (s):
• Target Modules in scope: Enterprise RMS that includes; Property and Evidence. • Modules out of scope: Any others not listed above, including any additional Target modules.
Any additional source tables needed beyond the source tables listed above, or any additional data being populated into any other module will result in a change request for both time and cost.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 114
In Scope Service:
The following outlines the services that are considered within the scope of this Statement of Work.
Baseline Services
Service Definition
Data Conversion Changing digital data from one format to another so it can be used in another software application. Converted data is delivered in the form of Mock/Test iterations, go live converted data and potential GAP conversions as per the scope above.
Data Standardization Converting accepted (not misspellings) data values that represent the same information into a single unified, recognized, and accepted structure as required by the target system.
Data Defaulting Based on predefined business rules, assigning a specific value to a field in the target database that is different than the corresponding value in the source database.
Release Notes Report developed at the time of conversion data delivery that outlines mapping document version, the source and target database and application version, the tables and modules populated, and any known issues.
Data Alteration Report Report to indicate records that have been truncated in order to insert into the database. The records are logged with the table, field, and primary key of the target record so that the full original value is not lost.
Standard Name Merge White Box will perform a Standard Name Merge consisting of merging the data based on the following criteria: DOB; with One of the following unique identifiers, SSN, DL Number/DL State, FBI #, or State ID #.
Image Conversion Converting digital images that were used in one application, for use in another software application. May also require changing the format of the images so that they function in the new application
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 115
Out of Scope
The following outlines the services that are considered outside the scope of this Statement of Work.
Central Square/Rialto is requested to submit a Change Request in order to include any of these optional services within the scope of this Statement of Work. Note that additional services may result in added cost and/or schedule delay.
Optional Services
Service Definition
Additional Conversions/Go Lives Re-run of the conversion process above and beyond those agreed to be within scope.
Address Validation Validates and standardizes address against USPS database Custom Reports Reports to indicate data that meets a certain criterion provided by Central Square / Rialto
Additional 3rd party Validation Review and correction of legacy data through use of third party commercially available reference applications to provide assurance that data is adequate for its intended use
Data Cleansing Amending, correcting, removing, or defaulting inaccurate, incomplete, duplicated, or improperly formatted source data beyond that which is required to load the data properly in the target application
Data Augmentation Adding new or derived data necessary or desired in the target system but not available in the source. (Also called data enrichment). This includes changing the intent of the source data
Enhanced Name Merge Any name merge applied that is outside of the Standard Name Merge criteria.
Convert to multiple databases Option to convert data to more than one target database.
Financial Conversion Any data that has financial components (fees, obligations, payments. interest etc). that needs to be calculated, converted and populated into the target application.
Preliminary Run of Converted Data Option to analyze and run the Names section only before full conversion run to validate cleanliness and number of potential duplicates.
This Statement of Work is Valid from 120 days from date of issuance.
16.2.2. White Box – ART Solution
SUMMARY: Convert legacy access data to a readable portable format and provide a searchable solution and reporting tool to access legacy source data with an interface for queries and data lookups to the historical source information within the parameters specified below. Where Agency/Rialto is referenced below, Central Square will assume the responsibility to work with Rialto to complete the task.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 116
Roles and responsibilities:
Central Square
Project Manager and System Engineer
o Manage project scope, schedule and performance, coordinate activities with White Box o Assist with adherence to schedule, and issue resolution. o Inform White Box of any issues with plan to resolve
Rialto
Central Square to facilitate access to Agency Legacy System Subject Matter Expert and IT Support to:
o Provide legacy data files to White Box
o Work with White Box to retrieve data and layout information from legacy system in either CSV, Flat Files with table header layouts or in a portable (e.g. SQL) format o Ensure prompt and accurate delivery of source data for mock and final data extraction o Review, provide feedback and approve any mapping Document and iterations per schedule
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 117
White Box
Project Manager
o Manage project scope, schedule, and performance, coordinate activities with Central Square.
Data Analyst/Engineer
o Retrieve and prepare source data and setup other applicable systems o Build, test, and run application interface and deliver converted data
Assumptions and Constraints:
• This project includes one test iteration and the final “go live”, consisting of the source data provided to White Box Technologies. Data must be in either a CSV, flat files with table header layouts or in a portable (e.g. SQL) format. And must match the same layout as previously provided.
• White Box will not be analyzing, populating, migrating, cleansing or manipulating any legacy data into any Rialto production RMS, CAD or JMS system. Legacy data is static, no new data can be added to the Archive Report Tool Solution.
• White Box will deliver the converted data either via FTP or Hard Drive via mail • If hosting the solution on premise, Rialto is responsible to acquire the hardware and any software licenses to house the converted data, SQL Database(s) and the ART application. (If database size is under 10GIG then the free version of SQL Express can be utilized). Hardware for the Application is minimal-any modern processor with approximately 100 MB of free space needed for the ART Solution. Hosted solutions are available as a separate option • Work performed under this SOW is under warranty by White Box for thirty (30) days following delivery of any converted data and the Archive Report Tool Solution. White Box is not responsible for any source data issues and since no cleansing of data is included with this SOW, the source data will only be searchable in its existing form. White Box is not responsible for the integrity or cleanliness of the source data. Errors or omissions in converted data that result from application, database, or source data changes by Rialto are not covered by this warranty.
No ongoing support is included with this SOW beyond the 30-day warranty period. This SOW grants Rialto a 10 user, one-year license after the final delivery of the ART installation. Ongoing support will need to be added after the first year of use. Support, additional licensing as well as other hosting solutions will be in a separate quote. (As of the date of this agreement, annual licensing is 15% year of total White Box price per ART installation). • Rialto will set up a test environment that White Box can utilize for testing purposes, as well as access to any required hardware or software, prior to production • A project schedule will be developed and mutually agreed to during the initiation of this project.
Any delay in the delivery of milestones or related sub-steps to the schedule, which is the responsibility of Rialto, can result in a day-for-day delay in subsequent milestones that White Box is responsible for.
Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 118
• Following a White Box deliverable, unless otherwise specified Rialto has a set number of business days to report any issues. If White Box receives no response within that time, the deliverable will be considered accepted as delivered and if tied to a billable milestone, the deliverable will be invoiced. Issues reported after that period of time will be resolved on a case- by-case basis and may or may not be subject to additional charges and / or a change request.
Estimated Key project milestones:
Milestone Responsibility
Deliver Source data and code tables to White Box. Central Square/Rialto Develop Technical Specs and fields to be queried White Box/Rialto Deliver first iteration ART Solution White Box
Review of test iteration Central Square/Rialto
Deliver source data for go live Rialto
Deliver final ART Solution White Box
Cut off for reporting post implementation issues (30 day Warranty Period, after final delivery) Central Square/Rialto
Source System(s):
• Visionair
Work Scope:
The base app is a tool for allowing staff without database or technical programming experience to search for and view legacy historical data.
Once getting the data the first step is to convert the legacy data to a SQL format. Then, the application will be built to query data from that SQL database converted from the legacy database. Data can be queried by name, case name/number, cad call, booking, incident, warrant, citation, and/or any event.
The base app allows for records to be deleted (expunged) by a specified user. All queries or lookups and/or expungements will need to be done through the base application with a customizable report.
Rialto may choose any existing hardware to house the data and the query application if no hosted solution is chosen.
Customizable reports provide an efficient and easy way to view the data that’s based on an event and present that in a searchable, human readable format. Report(s) will have the capability to print, save, and save as and show attachments/images (if applicable) that are linked to the selected record. The customizable report(s) have the capability to present all applicable data for a selected record.
One Incident/Case report from the Visionair source system database is included with this SOW and includes up to 80 total fields pulling data from up to 9 main sections*. The first step of the kickoff meeting will be to refine those data elements/sections to be included within the report as well as the Rialto Police, CA
Vision to Enterprise Migration
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.
©2024 CentralSquare Technologies, LLC Page 119
report format. (*A section is a logical main header of data e.g. a general details section, involvement section etc.)
This SOW assumes that all report values from the source data are static values stored in a database table and that there are no values in the report that are generated that White Box would have to spend time and effort to re-create the logic from the app, to generate those values for the report. It also assumes that the sample report(s) don’t have additional sections that were excluded due to the source tables being empty.
Any Word doc attachments converted to PDF for embedding will be a change request for time and cost.
New custom interfaces, unique customizations, additional reports and enhancements can be developed if needed to perform searches, views and expungements and any other potential functionality, which will also require a separate Change Order for both time and cost.
Rialto Police, CA
____
Version 1.3
1000 Business Center Drive, Lake Mary, FL 32746
407.304.3235 l Fax: 407.304.3301 l www.centralsquare.com
STATEMENT OF WORK
UNIFY (CLOUD)
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. ©2024 CentralSquare Technologies, LLC Page ii
© 2024 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
07.08.24 1.0 *Initial draft M. Harbin
09.06.24 1.1 *Section 2.5: Portal access is not available until the Unify configuration is completed. Portal access is included with Unify at no additional cost.
*Section 2.6: Comment can be resolved, other agencies are charged.
*Section 2.8.1: External System Adapters Comment: This
paragraph is in reference to an external system provider (i.e. a CAD vendor outside of CentralSquare). If there were any participating agencies that were part of the Rialto contract and they had a different CAD vendor that did not have an adapter available, that agency would need to contract with their vendor for the development of the adapter in order to connect to the Hub. The paragraph is stating that those costs are not included in this contract. For Rialto, the licensing, implementation costs, etc are included in this contract (the CentralSquare Solutions Agreement). This paragraph is N/A for Rialto and can be removed from the SOW, if desired.
Ann Marie Newton
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. ©2024 CentralSquare Technologies, LLC Page iii
*Section 3.1.1, Business Rules: CentralSquare can provide optional pricing for assistance in the creation of additional business rules, if desired.
*Section 3.1.1, Code Mappings/Translations: Answer 1: The common code set list can be provided upon contract signing.
Answer 2: Yes, updates will be shared. See Section 3.1.2, Updates and Synchronization of Shared Incident Data.
*Section 3.1.1, Custom Scripts: The request for custom scripts is very rare as most functions can be/are handled via business rules, filters, and code mappings, not a custom script. Custom example- based on 'x' you need to have some other type of action or trigger that is not part of the standardized business rules. Items such as this are usually identified after you have tested or after you have been using the system a while. Costs for customization would be determined by the level of effort for the change that is being requested.
*Section 3.1.2, Address Validation: The Hub does not geo validate addresses, the CAD systems on each end of the Hub are responsible for address validation. If the CAD system cannot validate on their own, the Hub can pass lat/long information to the other systems, if needed.
*Section 3.1.2, Sharing Comments: There are 4 bi-directional options for sharing comments between agencies. The
recommendation to start with is after you share the initial call which is going to have whatever you define (the location information, nature, etc) and you want to share out additional comments, it is probably best done with the deliberate code (the hashtag code). This is one of those items that the agencies will work out once you start using the system. What we typically see is most start as restrictive as possible and then work from there.
That way, you are not oversharing, but you are also getting what you need.
*Sections 4.1.2, 4.3.2, 4.4, 4.4.4, 5.1.2, 11.1.2 for customer TCR approval: Changed this from 5 to 10 business days.
*Section 5.2: Typically most clients start the Unify
implementation after the CAD Enterprise go-live.
*Section 6.2.1- Cloud Components: CentralSquare will provide the needed DOJ documentation.
09.09.24 1.2 *Section 3.1.6: Toast notifications can be configured to display on a different screen, but they will still appear in the lower-right corner of the screen. The notifications can be configured to allow an audible notification. The Toast Notifications are uniform across the platform.
Ann Marie Newton
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. ©2024 CentralSquare Technologies, LLC Page iv
*Section 6.2.1- Cloud Components: added in the body of the SOW: “CentralSquare will provide the needed DOJ
documentation for the project”.
*Call with client and reviewed Sections 3.1.1- Business Rules and
3.1.6 Toast Notifications.
*Resolved all comments and accepted all CST redline inserts.
09.09.24 1.3 *Deleted all comments, clean copy of the SOW for CST legal team- FINAL SOW.
Ann Marie Newton
Internal Document Control
Date Version Details/Changes Author
05.15.24 1.0 Updated for Cloud Only
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. ©2024 CentralSquare Technologies, LLC Page v
Rialto Police, CA
Unify CAD-to-CAD
Table of Contents
Document Control................................ ................................ ................................ .............................. ii Internal Document Control ................................ ................................ ................................ ................ iv
1. CENTRALSQUARE UNIFY ................................ ................................ ................................ .............1
1.1. Statement 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 CentralSquare Deliverables ............................................................................. 5
2.3. Contracted Modifications to Standard CentralSquare Products .................................... 6
2.4. CentralSquare Unify Overview ....................................................................................... 6
2.5. Solution Overview........................................................................................................... 7
2.6. Deliverable System Connections on CentralSquare Unify Hub ...................................... 8
2.7. Modifications .................................................................................................................. 8
2.8. CentralSquare Unify Customer Deliverables .................................................................. 8
3. STANDARD FUNCTIONALITY CENTRALSQUARE UNIFY ................................ ................................ 12
3.1. Overview ....................................................................................................................... 12
3.2. CentralSquare Unify External System Dependencies ................................................... 23
4. PROJECT CONTROLLING PROCESS................................ ................................ ............................. 25
4.1. Overview ....................................................................................................................... 25
4.2. Change Management Process ...................................................................................... 27
4.3. Project Reporting .......................................................................................................... 28
4.4. Document Review ......................................................................................................... 29
4.5. Third-Party Management ............................................................................................. 30
5. PROJECT INITIATION AND PLANNING ................................ ................................ ........................ 32
5.1. Overview ....................................................................................................................... 32
5.2. Project Kickoff ............................................................................................................... 33
6. PROJECT EXECUTION ................................ ................................ ................................ .................. 35
6.1. Overview ....................................................................................................................... 35
6.2. System Installation ....................................................................................................... 35 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. ©2024 CentralSquare Technologies, LLC Page vi
Rialto Police, CA
Unify CAD-to-CAD
7. CENTRALSQUARE UNIFY TESTING ................................ ................................ .............................. 39
7.1. Isolated CAD Adapter Testing ....................................................................................... 39
7.2. Provider End-to-End Testing ......................................................................................... 39
7.3. Functional Acceptance Testing (Customer End-to-End Testing) .................................. 40
8. CENTRALSQUARE UNIFY TRAINING ................................ ................................ ........................... 42
8.1. Training ......................................................................................................................... 42
9. CONDUCT CENTRALSQUARE UNIFY PRE-GO-LIVE TASKS ................................ ............................. 43
9.1. Pre-Go-Live ................................................................................................................... 43
10. CONDUCT CENTRALSQUARE UNIFY GO-LIVE ................................ ................................ .............. 45
10.1. Go-Live .......................................................................................................................... 45
11. PROJECT CLOSURE ................................ ................................ ................................ .................... 46
11.1. Project Closure .............................................................................................................. 46
12. Appendix A – Contracted Modifications to Standard CentralSquare Products ............................. 47
13. Appendix J – CentralSquare Connectivity to Enterprise On-Premise Systems Policy .................... 48
14. Appendix Y – Workshop and Training Summary ................................ ................................ ........ 49
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 1
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 Rialto Police, CA (“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 the Customer and other participating agency members of the CentralSquare Unify implementation, the 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 2
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 3rd 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) CJIS Security Policy means the Federal Bureau of Investigations Criminal Justice Information System Security Policy. The essential premise of the CJIS Security Policy is to provide appropriate controls to protect the full lifecycle of criminal justice information (CJI), whether at rest or in transit. The CJIS 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) Cloud means a remote hosted server infrastructure.
l) Codefiles are the component fields within each product that define the data to be contained within each table.
m) 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. n) COTS means “Commercial Off the Shelf” software packages provided by CentralSquare. o) Functional Acceptance Test (FAT) is a test of specific functionality of the CentralSquare Unify solution.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 3
p) Go-Live means the event that occurs when Customer first uses the CentralSquare Unify solution for Live Operations in a non-test environment. q) GIS is an acronym for Geographic Information System, which is a system for storing and manipulating geographical information on a computer.
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 3rd 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) Task Completion Reports (TCR) is a formal document presented to the Customer that acknowledges completion of a major task or event.
bb) Third-Party Software or Systems are software and systems that are proprietary to a Third- Party, not CentralSquare, which may be used for the purposes of providing services or deliverables.
cc) Work Hours:
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 4
a. Business hours are defined as Monday – Friday, 8:00am - 5:00pm local time. b. Training hours are defined as:
i. Remote Training: Monday - Friday, between 8:00am – 5:00pm as determined by the Customer’s time zone based on the actual duration of the class.
ii. Onsite Training: Tuesday – Friday, between 7:00am – 10:00pm as determined by the Customer’s time zone based on the actual duration of the class.
c. Alternate training schedules (e.g., Monday class starts for classes that would normally start on a Tuesday, multiple classes per day, evening, and weekend classes) are subject to additional cost.
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 5
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 8 - 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 6
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 6.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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 7
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 a CentralSquare Hub in the AWS GovCloud 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).
The participating agencies will be connected to the CentralSquare Hub using the method(s) below.
• Unify: Bidirectional solution, enable sharing of incidents, unit updates, and unit locations.
• Portal Access only (for situational awareness and is included with Unify, Notify, and Aware).
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 8
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.
This project includes connecting to the Confire Hub.
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.
• 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.
# Agency Connecting System
(Vendor/Description)
Connection
Type
Product
Package
Adapter Status
1 Rialto Police CentralSquare
Enterprise CAD
Bi-directional Unify Adapter Available for
deployment
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.
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:
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 9
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 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 collaborative documentation.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 10
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.
Note: CentralSquare recommends a high-speed internet connection greater than 10 MBps bi- directional. To improve reliability, it is recommended for the Customer to have a second redundant internet connection that uses a different ISP provider (utilizing a different trunk line) available for failover of the primary Internet connection.
Equipment required to connect the redundant ISP provider is the responsibility of the Customer. All connections to the Hub require IP whitelisting for an additional level of security.
Note: The connection recommendation between the Customer site and the Hub is established using a dedicated VPN appliance. In addition to the VPN option, Customers can also use Tunnel which is a soft VPN. This option requires that the Customer maintain a security certificate.
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
CentralSquare will provide training related to the Hub Portal console and administrator user training. 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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 11
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.
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 12
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 Call 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 13
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 not a limit on the number of business rules or User Groups that can be created by the agency.
Configuration Count
Business rules with associated filters 5
User groups with associated filters 5
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 14
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 may be 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
l) Unit Status
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 15
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) l) 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)
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 16
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,
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 17
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 may be 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)
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 18
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
l) 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 AVL 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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 19
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.
a) 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 20
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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 21
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 Date 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 in the Cloud are the responsibility of CentralSquare.
3.1.6. 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.
Call and Unity 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,
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 22
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 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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 23
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:
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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 24
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 25
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 OSDs 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 training and Go-Lives.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 26
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 ten (10) 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 ten (10) business days of receipt of the TCR.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 27
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 in terms of costs, risks, and
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 28
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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 29
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 ten (10) 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 30
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 ten (10) 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 to Customer 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 ten(10) 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 ten (10) 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 31
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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 32
5. 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. c) Identify and engage the CentralSquare Project team responsible for carrying out Project Execution.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 33
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 as defined 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 ten (10) 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 34
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- visual equipment including a projector(s), screen, and whiteboard.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 35
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.
Cloud virtual provisioning will be the responsibility of CentralSquare.
6.2.1. Cloud Components
The CentralSquare Cloud Team will provision the CentralSquare software in the Cloud. This will entail a planning meeting with the Customer System/Network Administrator and other CentralSquare staff (Project Manager, Technical Services), configuration of the VPN, advising on network communications, and configuring access to the provisioned system.
CentralSquare will provide the needed DOJ documentation for the project.
The administration services of the Cloud environment are the responsibility of CentralSquare, including support, operation, and maintenance of the underlying infrastructure. Access to any resources by the Customer will not be allowed except through the applications and programmatic connections.
6.2.1.1. CentralSquare Responsibilities
a) Host Technical meeting with Customer network\systems administration staff.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 36
b) Provide port, protocol information to Customer for firewall rules. c) Provide guidance on routing needed from Customer networks to Cloud environment.
d) Provision Cloud system as necessary.
e) Provide URLs and any other paths for Customer connectivity. f) 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) Open firewall as directed by CentralSquare Technical staff. d) Provide routing rules to route traffic through the VPN tunnel as advised by CentralSquare technical staff.
e) 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 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 37
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.
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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 38
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. These test scenarios will form the basis of training documentation.
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.
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 39
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 (5) 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 9.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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 40
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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 41
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 42
8. CENTRALSQUARE UNIFY TRAINING
8.1. Training
Upon completion of the Functional Acceptance Testing, CentralSquare will conduct CentralSquare Unify Hub Administrator training on consecutive weekdays during remote training hours (Monday – Friday, between 8:00am – 5:00pm as determined by the Customer’s time zone based on the actual duration of the class) or on consecutive weekdays during onsite training hours (Tuesday – Friday, between 7:00am – 10:00pm as determined by the Customer’s time zone based on the actual duration of the class).
Alternate training schedules (e.g., Monday class starts for classes that would normally start on a Tuesday, multiple classes per day, evening, and weekend classes) are subject to additional cost.
Training classes are conducted based on the quantities specified in the Agreement. Refer to SOW, Appendix Y – Workshop and Training Summary for a complete listing applicable to this project. CentralSquare and the Customer will develop a mutually agreed upon training schedule for the agencies.
CentralSquare follows a “Train-the-Trainer” approach to training. This method allows in- depth training for key individuals at each agency who will then provide training to the remainder of the users.
a) CentralSquare Unify Hub Administrator Training: CentralSquare will provide Portal Administrator training on how to monitor system health, manage groups and users, and make basic configuration changes. This training will be conducted remotely through a webinar. Participants should not exceed ten (10) per class. b) Unify User Training: CentralSquare will work with the Customer and agency trainers to advise them on incorporating CAD-to-CAD concepts into their training courses for dispatchers and call takers. However, since the methods for interacting with CAD incident and resource sharing are dependent upon their configuration, training for the End Users is the responsibility of the Customer and the participating agencies. It is expected that Subject Matter Experts (SME’s) will be sufficiently familiar with their operational procedures and their CAD configuration to conduct this training for their respective agency.
c) Hub Portal Training Videos: CentralSquare will provide the Customer and the participating agencies with access to training videos on essential Portal features. d) Training Documentation: Agency specific documentation of local sharing use cases and rules is the responsibility of the Customer and the participating agencies.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 43
9. CONDUCT CENTRALSQUARE UNIFY PRE-GO-LIVE TASKS
9.1. Pre-Go-Live
After the Customer-led User training is complete, the system is ready for deployment.
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 all end user training has been completed, and 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 acknowledges sufficient user training has been completed, 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
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 44
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-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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 45
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 (trainer), 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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 46
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
Deliverables
Once complete, ensure CentralSquare project manager will provide TCR to 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 ten (10) business days. b) Process payment of final invoices.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 47
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.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 48
13. Appendix J – CentralSquare Connectivity to Enterprise On- Premise Systems Policy
Customer Managed On-Premise Systems
The BeyondTrust/Bomgar and/or SecureLink 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 Section AC-17 and control enhancements of the FBI CJIS Security Policy (Remote Access).
Use of either of these solutions enables customer agencies to remain CJIS compliant for purposes of FBI and/or state regulatory agency audits.
Rialto Police, CA
Unify CAD-to-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.
©2024 CentralSquare Technologies, LLC Page 49
14. Appendix Y – Workshop and Training Summary
Training/Go-Live Deliverable Quantity Training(s)/Workshop(s) Included Remote/Onsite Initial Discovery, Configuration:
Workshop #1: Kickoff, SMS &
Questionnaire (one hour, all
agencies need to attend the
workshop)
1 One (1) hour workshop Remote
Initial Discovery, Configuration:
Workshop #2: Code-Mapping
(one hour, all agencies need to
attend the workshop)
1 One (1) hour workshop Remote
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
(Customer End-to-End Testing)
1 Sixteen (16) hour testing event per
agency Remote
CAD-to-CAD Hub Portal Console
and Administrator Training (all
agencies need to attend this
training session)
1 Two (2) hour training session Remote
CentralSquare Unify Go-Live
Support Services 1
Three (3) days Go-Live Support - one
(1) Consultant, eight (8) hours each
day, during normal business hours.
Remote
CST-2024-101804
EXHIBIT 6
Service Level Commitments
The following applies to the cloud based products of Field Training Online, CrimeView, and Unify as included on Exhibit 1.
1. Service Level Commitments
A. Availability. During any calendar month, the availability of the Solution shall be no less than 99.9%, excluding scheduled maintenance. CentralSquare shall provide Customer with prompt notification as soon as it becomes aware of any actual or potential unscheduled downtime of the Solution, as well as continual periodic updates during the unscheduled downtime regarding CentralSquare’s progress in remedying the unavailability and estimated time at which the Solution shall be available.
B. Measurement. Service availability is measured as the total time that the solutions are available during each calendar month for access by Customer (“Service Availability”). Service Availability measurement shall be applied to the production environment only, and the points of measurement for all monitoring shall be the servers and the internet connections at CentralSquare’s hosted environment.
C. Calculation. Service availability for a given month shall be calculated using the following calculation:
I. The total number of minutes which the service was not available in a given month shall be subtracted from the total number of minutes available in the given month. The resulting figure is divided by the total number of minutes available in the given month.
II. Service availability targets are subject to change due to the variance of the number of days in a month.
III. The total number of minutes which the service was not available in a given month shall exclude minutes associated with scheduled or emergency maintenance.
D. Remedy. If the service period target measurement is not met, then the customer shall be entitled to a credit calculated as follows:
Service availability Credit percentage
Less than 99.9% but greater than or equal to 99.0% 5%
Less than 99.0% but greater than or equal to 95.0% 10%
Less than 95% 20%
Service Availability in the relevant
Service Period
Percentage Reduction in Monthly Fee for the
Subsequent Service Period
Less than 99.9% but greater than or equal to 99.0% 5%
Less than 99.0% but greater than or equal to 95.0% 10%
Less than 95% 20%
E. Credit must be requested by the customer within sixty (60) days of the failed target. Any credit awarded shall be applied to the next applicable invoice. Customer shall not be eligible for credits where customer is more than thirty (30) days past due on their account.
2. Exceptions. The Service Level Commitments and availability stated in this Exhibit do not cover services interruptions or performance issues that are caused by factors outside of CentralSquare or it’s hosting partner’s control. Such factors may include, but are not limited to:
A. Internet Access. Issues relating to Customer’s internet access. Any outages, slowdowns, or other problems related to the internet connection are explicitly disclaimed;
B. Customer’s Internal Network Issues. Issues originating from Customer’s internal network such as network congestion, network equipment failure, or misconfigurations are explicitly disclaimed;
CST-2024-101804
C. Third-Party Acts. Issues caused by the acts or omissions of third-parties, including providers of internet services, or for issues arising from third-party software or hardware that is not provided by CentralSquare is explicitly disclaimed;
D. Gross Negligence or Willful Misconduct. Issues relating to the failure or delay in performance to the extent caused by the acts or omissions of Customer or its agents constituting gross negligence or willful misconduct are explicitly disclaimed; and,
E. Force Majeure. A force majeure event such as natural disasters, acts of God, or any other cause constituting force majeure are explicitly disclaimed.
3. Server Performance & Capacity. The standard provisioning of storage for the cloud solutions is 1 terabyte.
If Customer requests to add additional Software, increase storage or processing requirements, and/or request additional environments, these requests will be evaluated and if additional resources are required to support modifications, additional fees may apply at per unit (gigabyte, hour, license, etc).
4. Non-Production Environments. Included in the subscription fee is access to the training environment during the hours of 8:00am – 4:00pm EST, Monday through Friday. Should the Customer require extended access for items such as internal training, CentralSquare can make exceptions provided that Customer provide reasonable advance written notice. CentralSquare will then work with the Customer to enable access in accordance with an agreed upon schedule.