Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
2024-566-E-Emergency Svc-Hexagon Safety, Infrastructure, & Geospatial-CAD Replacement
Orange County, NC Statement of Work for HxGN OnCall Dispatch On-Premise Implementation PRESENTED BY: Michael Dunkwu Regional Sales Manager Hexagon Safety, Infrastructure, & Geospatial 305 Intergraph Way Madison, AL 35758 USA 571-368-8328 Michael.dunkwu@hexagon.com July 25, 2024 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Statement of Work Table of Contents Introduction ......................................................................................................................... 1 Purpose ............................................................................................................................... 1 Software Functionality and Support ................................................................................. 2 Project Governance ............................................................................................................ 2 Customer Core Team(s) ..................................................................................................... 3 Core Team Roles and Responsibilities ...................................................................... 3 Dispatch Core Team ................................................................................ 3 Mobile Core Team .................................................................................... 3 Project Assumptions .......................................................................................................... 4 Project Tasks ...................................................................................................................... 8 Project Initiation ......................................................................................................... 8 Planning Phase .......................................................................................................... 9 1. Project Kickoff Meeting ..................................................................... 9 2. COTS Interface Questionnaire Completion ..................................... 12 3. OnCall Dispatch & Mobile Unit Launch ........................................... 14 4. OnCall Dispatch GIS Requirements Review – Web Conference ..... 16 5. Custom Interface Requirements Gathering ..................................... 17 6. Custom Interface Development ....................................................... 19 7. Load Balancer Equipment Ordering ................................................ 20 Staging Phase ......................................................................................................... 21 8. Physical Infrastructure Installation ................................................... 21 9. Virtual Server and OnCall Software Staging ................................... 23 10. OnCall Dispatch GIS Consulting .................................................... 26 11. OnCall Dispatch System Build 1 .................................................... 27 12. OnCall Dispatch Deployment & Response Planning Workshop ..... 29 13. OnCall Dispatch System Build 2 .................................................... 31 Configuration Phase ................................................................................................ 33 14. OnCall Dispatch Fundamentals for Core Team ............................. 33 15. COTS Interface Product Installation and Configuration ................. 35 16. CommSys ConnectCIC Installation ................................................ 37 17. OnCall Dispatch Configuration Consulting 1 .................................. 39 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation 18. OnCall Dispatch Configuration Consulting 2 .................................. 42 19. OnCall Dispatch Configuration Consulting 3 .................................. 44 20. OnCall Dispatch | Mobile Unit Configuration Consulting Session – Law 46 21. OnCall Dispatch | Mobile Unit Configuration Consulting Session – Fire 48 22. OnCall Dispatch | Mobile Responder Configuration – Law ............ 50 23. OnCall Dispatch | Mobile Responder Configuration – Fire ............. 51 24. OnCall Dispatch Archive Database Staging ................................... 52 25. OnCall Analytics | Dispatch Configuration ..................................... 53 26. Custom Interface Product Installation and Configuration ............... 55 27. Standard Interface Product Installation and Configuration ............. 56 28. Sustaining Coordination Services for the CommSys ConnectCIC ASAP Interface ....................................................................................... 57 Testing Phase .......................................................................................................... 59 29. Test Plan and Test Cases Development ....................................... 59 30. Customer Functional Testing ......................................................... 60 Training Phase......................................................................................................... 62 31. Hexagon-Led Training ................................................................... 62 32. Test and Training Environment Creation ....................................... 64 Cutover Phase ......................................................................................................... 65 33. Cutover Plan .................................................................................. 65 34. System Readiness Review ............................................................ 66 35. Cutover to Production Use ............................................................. 67 36. Post-Cutover Support .................................................................... 69 Final Acceptance .............................................................................................................. 71 Approval Signatures ......................................................................................................... 72 Attachment A – Pricing Summary ................................................................................... 73 Pricing Summary Table............................................................................................ 85 Pricing Assumptions ................................................................................................ 85 Attachment B – Payment Schedule ................................................................................. 87 Attachment C – Initial Project Schedule ......................................................................... 88 Attachment D – Training Curriculum .............................................................................. 90 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation HxGN OnCall Dispatch | Advantage System Administrator Training (Qty: 1) ........... 90 HxGN OnCall Dispatch | Advantage Train-the-Trainer (Qty: 2) ................................ 91 HxGN OnCall Dispatch | Mobile Unit Train-the-Trainer (Qty: 2) ............................... 92 HxGN OnCall Dispatch | Mobile Responder Train-the-Trainer (Qty: 2) .................... 93 HxGN OnCall Analytics | Dispatch User Training (Qty: 1) ........................................ 94 HxGN OnCall Analytics | Dispatch System Administrator Training (Qty: 1) .............. 95 Xalt Developer Training (Qty: 1) .............................................................................. 96 Attachment E – OnCall Dispatch Specifications ............................................................ 97 Attachment F – System Configuration Diagram ............................................................. 98 Attachment G – CAD/Mobile Functional Specifications Matrix ..................................... 99 Attachment H – Interface Descriptions ......................................................................... 100 COTS Interfaces .................................................................................................... 100 ANI/ALI Interface .................................................................................. 100 HxGN OnCall Dispatch | Informer ........................................................ 101 HxGN OnCall Dispatch | Fire Station Printing ...................................... 102 HxGN OnCall Dispatch | ProQA ........................................................... 102 HxGN OnCall Dispatch | CAD Link ....................................................... 103 HxGN OnCall Dispatch | Fire Link ........................................................ 104 HxGN OnCall Dispatch | Tracker .......................................................... 105 HxGN OnCall Dispatch | Notifications .................................................. 108 Avigilon VMS Interface ......................................................................... 110 Standard Interfaces ............................................................................................... 110 RapidSOS OnCall Call-Taker Interface ................................................ 110 Fire Station Alerting OnCall Dispatch Interface .................................... 111 PLT OnCall Dispatch Interface ............................................................. 111 External Alarms OnCall Dispatch Interface .......................................... 112 Custom Interfaces .................................................................................................. 112 Text to 911 ........................................................................................... 112 Query to OneSolution CAD .................................................................. 113 Query to OneSolution RMS .................................................................. 113 Consulting Services ............................................................................................... 114 Eventide Recording .............................................................................. 114 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Attachment I – Glossary of Terms ................................................................................. 115 Attachment J – GIS Requirements for the HxGN OnCall Dispatch System ............... 118 Attachment K – Warranty ............................................................................................... 120 Attachment L – Regional Provisions ............................................................................. 123 Attachment L-1 – CJIS Security Addendum ................................................................. 124 Attachment M – Special Terms and Conditions ........................................................... 126 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Statement of Work 1 Introduction This Statement of Work, including the attachments hereto, provided by Intergraph Corporation by and through its Hexagon Safety, Infrastructure & Geospatial division (“Hexagon”) to Orange County Emergency Services (“Customer”) describes the Products and Services that will be provided to implement an integrated computer aided dispatch (“CAD”) system and mobile system for the Customer (the “Project”) in exchange for payment of the amount set forth in the Quote (which is included as Attachment A). This SOW sets forth the Products and Services Hexagon will provide as well as each Party’s responsibilities and obligations to implement the Products. Except as otherwise provided herein, capitalized terms shall have the meaning set forth in Attachment I (Glossary of Terms) hereto. The Software provided by Hexagon will be the HxGN OnCall Dispatch Advantage Subsystem (“HxGN OnCall Dispatch System” or “OnCall Dispatch”). This Statement of Work is made pursuant to and governed by GSA Contract #47QTCA18D003G (the GSA Contract”). Purpose The SOW guides the Tasks and Activities for the Project. It documents Project implementation requirements, identifies each Task within the implementation process, sets expectations for each Party, and identifies the Task Acceptance Criteria. The SOW includes and incorporates the following Attachments: Attachment A – Pricing Summary Attachment B – Payment Schedule Attachment C – Initial Project Schedule Attachment D – Training Curriculum Attachment E – OnCall Dispatch Specifications Attachment F – System Configuration Diagram Attachment G – CAD/Mobile Functional Specifications Matrix Attachment H – Interface Descriptions Attachment I – Glossary of Terms Attachment J – GIS Requirements Attachment K – Warranty Attachment L – Regional Provisions Attachment L-1 – CJIS Security Addendum Attachment M – Special Terms and Conditions The remainder of this section details Project assumptions that impact the Project cost, schedule and scope, Project team composition, and Project management responsibilities. Each Task identified in this SOW includes the following, as necessary: Task Description, Task Deliverables, Task Prerequisites, Task Assumptions, Hexagon/Customer Team Participation and Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 2 Responsibilities, and Task Acceptance Criteria. The Tasks defined in the SOW may not be listed chronologically, and the actual Project implementation Tasks and timelines will follow the Project Schedule, unless otherwise noted. Software Functionality and Support As part of this Project, Hexagon shall provide licenses to Software identified in Attachment A (“Project Software”). The Project Software is licensed in accordance with the End User License Agreement subject to the GSA Contract. The Project Software shall have the capabilities and functionality set forth in the Specifications corresponding to the Project Software, which reflects all of the functionality Hexagon is obligated to provide. The Project Software shall only be tested to evaluate conformity to the Specifications. The COTS versions of the Project Software will be provided, and, unless otherwise provided in the Specifications, this Order does not include any Product Change Requests or Customizations. OnCall presents an iterative upgrading process that will also be reflected in the Project. Several times per year, Hexagon may publish a new release to OnCall Software Products. Until the end of the Testing Phase, Hexagon may periodically implement newer releases of OnCall within the Customer’s environment, so the Customer may have a more current release of OnCall leading into the Training Phase and Deployment Phase. Upon Cutover, the Warranty Period for the Project Software shall commence as described in Attachment K (Warranty). Project Governance Hexagon will assign a Project Manager at the beginning of the Project to act as the primary point of contact at Hexagon for the Customer and provide general oversight and guidance for the Hexagon Project team throughout Project. To ensure successful delivery of the Project in accordance with the schedule, regular communications and an escalation path are necessary. Typically, all formal communications will occur between the Hexagon Project Manager and the Customer Project Manager. Generally, each Party’s Project Manager will have, at minimum, a bi-weekly status conference with one another. On a monthly basis, Hexagon will provide a status report reflecting completed Activities, upcoming Activities, at-risk Activities, other pertinent matters affecting the Project, and, as necessary, an updated Project Schedule. The Customer may propose revisions to the status report and its attachments, but it must do so within five (5) Business Days, otherwise it is final and accepted by the parties. Finally, on a quarterly basis, or more frequently if deemed necessary by the Parties, the Department Sponsor for Customer, a Hexagon Director or Vice President responsible for operations, and the Customer’s Project Managers shall hold a remote executive review meeting to discuss the status of the Project and particular challenges impacting the Project. The two senior officials for both parties shall also serve as the escalation point for disputes arising between the Project Managers. Projects of this nature involve both Parties performing a variety of Tasks that are dependent upon one another. With that type of relationship and the number of Tasks involved, from time to time delays may occur. The Hexagon Project Manager and Customer Project Manager will address and take actions to mitigate such delays, to the extent reasonably possible. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 3 The Hexagon Project Manager will manage the Project Schedule and provide copies of it to the Customer as updated. From time to time and outside of the status report process described above, the Project Managers may find an adjustment to the Project Schedule is necessary. If the adjustment is mutually agreeable, the Hexagon Project Manager shall update the Project Schedule and it will become the then current Project Schedule, superseding all prior Project Schedules. The Parties acknowledge that potentially material adjustments to the Project Schedule may need to be addressed through a Change Order due to its impact on other aspects of the Order. Unless otherwise noted between the Project Managers, all Tasks reflected in this SOW are regarded as having completed the Task Acceptance Process upon Cutover or commencement of a Task for which the earlier Task was a prerequisite as noted within the SOW and/or Project Schedule. Any provisions particular to Customer’s country are specified in Attachment L – Regional Provisions, which shall supersede any conflicting provisions provided in this SOW. Customer Core Team(s) The Customer shall provide qualified resources to staff the Core Team (described below) to facilitate a successful implementation of OnCall. The Core Team consists of an overall Customer project manager who is responsible for the day-to-day coordination of Customer’s Project Activities and personnel divided amongst smaller discipline-oriented groups with particular roles and responsibilities appropriate to the discipline. Those subdivided groups are denoted with suggested team member resources below. Core Team Roles and Responsibilities Dispatch Core Team Below is the defined group of Customer members responsible for decision making for the remainder of the Public Safety Access Point (“PSAP”) user group(s) regarding configuration and use of the OnCall Dispatch solution. The “Dispatch Core Team” should consist of, at a minimum, the following resources with the corresponding qualifications: 9-1-1 Call-Taker – This person intimately understands the process by which emergency calls for service are answered, triaged, created in the current CAD, and sent for dispatch. Radio Dispatcher – This person intimately understands the structure of the PSAP, the agencies for which it dispatches, and the methods in which dispatching occurs. System Administrator (Operational) – This person is responsible for the operational administration of the OnCall Dispatch system. Managing things like user accounts, permissions, parameter settings, user interface layouts, units, event types, etc. Decision Maker (Operational) – This person has authority, either by role or designation, to make decisions on behalf of the agency or agencies OnCall Dispatch is serving pertaining to the configuration of OnCall. The ideal size of the Dispatch Core Team is six (6) members. Under no circumstances shall the Dispatch Core Team be larger than twelve (12) members. Mobile Core Team Below is the defined group of Customer members responsible for decision making for the remainder of the field operations user group(s) regarding configuration and use of the OnCall Dispatch mobile solutions (OnCall Mobile) including OnCall Dispatch Mobile Unit, and OnCall Dispatch Mobile Responder. The Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 4 “Mobile Core Team” should consist of, at a minimum, the following resources with the corresponding qualifications: Patrol / Firefighter – This person is an active member of the patrol / operational division of the agency. They are tasked with responding to calls for service, field-initiated activities like traffic stops or inspections, and other duties in patrol / operations. This person should not be technology averse. They should embrace the use of technology and seek to find ways to leverage it to their benefit in their daily duties. Patrol Supervisor / Fire Supervisor – This person is an active member of the patrol / operational division of the agency and responsible for the day-to-day supervision of a group of patrol members or of a specific station/apparatus crew. This person is typically a rank of Sergeant or above in law enforcement and lieutenant or above in Fire/EMS, although actual rank structure in agencies may vary. Investigations / Detective / Fire Marshal – This person is an active member of the investigations division or fire marshal’s office and has primary responsibility for long-term case work or other fire-related investigations. Command Staff – This person is an active member of the command staff at the agency. This person is typically a rank of Captain or higher in law enforcement or battalion chief or higher in fire departments, although actual rank structure in agencies may vary. Decision Maker – This person has authority, either by role or designation, to make decisions on behalf of the agency or agencies OnCall Dispatch Mobile Unit or Mobile is serving pertaining to the configuration of OnCall Dispatch mobile products. The ideal size of the Mobile Core Team is six (6) members. Under no circumstances shall the Mobile Core Team be larger than twelve (12) members. It is possible to have a Mobile Core Team duplicated for different responder roles, such as a law enforcement Mobile Core Team and a Fire Mobile Core Team. Project Assumptions The following list of assumptions and Customer responsibilities reflect Hexagon’s understanding of the Project. Changes in any of the assumptions and Customer responsibilities will affect the scope, Project Schedule, and/or cost of the Project. Agreement and Schedule Assumptions The Agreement has been executed by both parties and the Customer has provided either a notice to proceed or PO. Hexagon and the Customer will review the SOW and determine a mutually agreeable date for the Services to be performed. The Customer shall perform its assigned responsibilities as identified within the Initial Project Schedule (Attachment C) and Project Schedule developed as part of Task 1 in the time allotted. If the Customer does not reasonably comply with the Project Schedule, Hexagon is permitted with written notice to suspend its performance on this Project and redeploy its resources on other active projects until the Parties determine a mutually agreed upon date to re-start the Project. At that time, a new Project Schedule will be provided. Hexagon will have timely access to the applicable members of the Core Teams and other Customer Project staff in accordance with the Project Schedule. Customer shall make additional Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 5 personnel available on a priority basis, as needed, to provide subject matter expertise to complete this Project. Customer shall assign appropriately qualified personnel to the Core Teams and ensure they are actively engaged in the Project. Any work and effort ascribed to Hexagon in a given Task is confined to that specific Task and may not be used for or applied to any other Task. Customer shall provide Hexagon Project Manager with contact information for a Customer resource to resolve any issues that should arise from Hexagon’s access of Customer’s System during working and non-working hours. Any Service Request that is set to “NEED MORE INFO” or “RE-TEST” will be automatically closed after ten (10) Business Days if the Customer does not update the SR. Any workshop having a duration of three (3) Business Days or less shall begin no earlier than Tuesday of the week of that workshop and will conclude that same week. The Customer shall provide Hexagon with access to all data, documents, plans, reports, diagrams, and analyses reasonably related to the Project or otherwise necessary to facilitate Hexagon’s performance of its Activities. Unless expressly stated in this SOW, all Documentation, if any, provided by Hexagon under this SOW will be COTS Documentation, and the Documentation will not be customized by Hexagon. All Documentation delivered will be in Hexagon-approved format. Changes to Hexagon-format to accommodate specific Customer requests may be done at Hexagon’s discretion and at an additional cost. Unless Hexagon and Customer mutually agree otherwise, all Documentation provided by Hexagon will only be provided in electronic format. Unless otherwise stated in the Task, all Tasks will be conducted remotely. All Hexagon personnel performing remote Activities will be identified and properly vetted prior to commencement of those remote Activities. To the extent the Customer requires Hexagon personnel undergo COVID testing prior to performing work at Customer’s facilities, the Customer would be responsible for any such costs, which are not included in the scope and price of this Order. If the title of a Task includes the name of a Subsystem (e.g., Dispatch), that Task shall be construed as pertaining only to that Subsystem unless expressly stated otherwise. Hardware and Software Assumptions All Software will be electronically delivered. All specifications provided with this SOW (Attachments E and F) will assume a traditional on- premises solution (i.e., not a hosted solution), and any change with respect to alternative hosting requires execution of a mutually agreed upon Change Order. The Customer shall purchase, install, and test all physical hardware, including the client/mobile hardware. The Customer will ensure its hardware, operating system software, database software, and other third-party products/environments conform with Attachments F. Deviations from Attachments F will not be considered due to the critical nature of the software supported by these systems. Hexagon and the Customer will verify the final system hardware configuration to ensure conformance with Attachment F. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 6 Customer shall purchase all applicable operating systems, database licenses, and Third-Party Software and ensure such operating systems, database licenses, and Third-Party Software meet the minimum requirements as defined in Attachments F. HxGN OnCall Dispatch requires SQL Server 2022 Enterprise Edition (EE) with SA, which will be configured in an “Always On” configuration for the Production Environment CAD database servers. The test environment CAD database server requires SQL Server 2022 Developer Edition (DE), and the training environment CAD database server requires SQL Server 2022 Standard Edition (SE). Hexagon technology for this Project will be implemented in the Microsoft environment as specified in Attachments F. Customer shall purchase, install, configure, and administer its Network Infrastructure, including, but not limited to, its WAN/LAN and wireless infrastructure. Customer’s wireless infrastructure shall meet minimum bandwidth requirements as stated in Attachments F. Customer shall be responsible for the wired and wireless connectivity between servers/clients and clients/clients. For automatic failover to a secondary location: (i) the network latency between the site servers shall be less than 10 milliseconds (ms) and (ii) load balancers must support and be configured to provide automatic failover between locations (Global Server Load Balancing). Customer shall be responsible for, and purchase and maintain if necessary, any hardware and/or third-party software necessary for implementing interfaces. Except as specified in this SOW, including Attachment A: Pricing Summary, Hexagon is not required to provide any additional Software customizations, custom forms, forms modifications, third-party software, custom interfaces, or custom reports. To the extent the Customer desires to use the Software or other deliverables provided herein in a manner or in combination with software or hardware that is not certified or recommended by Hexagon, then the Customer shall be solely responsible for such use. Hexagon shall not be responsible for the correction of any errors, Defects, reduced performance, compromised functionality, or other unintended consequences arising from such use. The Customer also shall not withhold acceptance of any deliverable or the System due to such use. Customer has reviewed the SOW and acknowledges and agrees Software Requirements: (i) represents all the functionality required of the System; and (ii) is the only functionality that is required to be delivered under this SOW. Customer shall have its GIS system conform to the requirements set forth in Attachment J (GIS Requirements) and other GIS specifications provided by Hexagon. Customer may use any supported third-party mapping provider for GIS information within OnCall Dispatch during this Project (see Attachment J). It is the Customer’s responsibility to provide this. The mapping subsystem shall be dedicated only to supporting HxGN OnCall Dispatch. System Access Assumptions Depending upon the Customer’s jurisdiction, additional security guidelines and assumptions are provided in Attachment L. Customer consents to Hexagon’s inspection and use of Customer’s data and systems, including, but not limited to, log files and databases, for the limited purpose of providing the Services specified herein and any future maintenance or warranty services described within the Agreement. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 7 Customer shall grant Hexagon personnel system administrator level access with unique log-in credentials to all servers, networks, databases, and workstations that will be involved in the Project. SecureLink is the remote access solution used by Hexagon. If Customer desires for Hexagon to utilize an alternate method and/or process for remotely working on their System, such alternate method and/or process shall be mutually agreed upon prior to this SOW being executed. Such alternate method and/or process may impact the original level of effort and Project Schedule quoted for this upgrade, which in turn may require a Change Order to modify. Customer shall provide unrestricted system and VPN access via SecureLink to Hexagon developers and implementers who will need to have access to multiple infrastructure platforms at the same time. The Customer shall provide Hexagon personnel individualized system access credentials and allow Hexagon authorized resources VPN access twenty-four (24) hours a day, seven (7) days a week for the duration of the Project. Customer shall provide external VPN access while on site to access various Hexagon resource libraries. After completion of this Project, Hexagon will VPN using SecureLink into the live System only at Customer’s request and will follow Customer’s required VPN access procedures. Third-Party Assumptions Customer shall schedule and coordinate third-party technical resources with the skills necessary to perform and/or support all Customer Responsibilities, provide necessary information, respond to Hexagon requests, and support the testing of interfaces, as required. Customer shall schedule and coordinate third-party technical resources in such a way as to ensure that a negative impact to the overall Project Schedule does not occur. Customer shall maintain, in good working order, all third-party systems which will integrate with Hexagon software or on which the Hexagon software depends as part of this Project. Customer shall be responsible for the operation and timely availability of external systems or third-party software necessary for the execution of the Project. If a delay in the Project is caused by a third-party vendor, Hexagon services not covered in this SOW may be required at additional costs. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 8 Project Tasks Project Initiation Prior to the Kickoff Meeting and after execution of this SOW or Order, the Hexagon Project Manager will contact the Customer Project Manager to identify the Project Start date and coordinate scheduling the Kickoff Meeting. For the Project to be successful, the following initial Activities must be performed before any Tasks occur: Customer shall order hardware, database software, operating system software, or other third- party software (excluding Kemp Load Balancers which will be ordered by Hexagon) consistent with the requirements set forth in Attachments E and F. The Hexagon Project Manager will contact the Customer Project Manager. During this initial contact, the Hexagon Project Manager will: Schedule the kickoff meeting; Identify the Project Start date; Create a detailed agenda describing the goals of the kickoff meeting; Discuss any mitigating factors that could affect the Project (e.g., scheduling conflicts, communication factors, and other risk factors); Schedule a conference call before the kickoff to go over the kickoff agenda; Ensure both Hexagon and Customer have appropriate Subject Matter Experts available for kickoff; and Provide document titled “Infrastructure Build Document”, if not previously provided to the Customer. Hexagon’s Project Manager will prepare kickoff materials. Hexagon’s Project Manager shall have updated the Initial Project Schedule and provide the draft Updated Initial Project Schedule and sent a copy to the Customer Project Manager for review prior to the Kickoff meeting. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 9 Planning Phase 1. Project Kickoff Meeting Task Description The objective of this Task is to discuss and address questions regarding Project Assumptions, discuss the updated Initial Project Schedule and agree to it at the meeting or shortly thereafter, and all requirements are understood prior to beginning any significant work. A meeting for Project Kickoff will be held after the SOW has been fully executed. The Project Kickoff meeting will be scheduled by each party’s Project Manager as part of Project Initiation Activities. Prior to the Kickoff Meeting and after written acceptance of the Agreement, the Hexagon Project Manager will contact the Customer Project Manager to identify the Project Start date and coordinate scheduling the Kickoff Meeting. The Project Kickoff Meeting shall last no more than one (1) Business Day. During this Task, the Parties shall confirm the updated Initial Project Schedule as updated by the Hexagon Project Manager. The resulting updated Initial Project Schedule shall be substantially similar in durations as that provided within Attachment C. Prior to the Project Kickoff Meeting Task, the Customer Project Manager shall have reviewed the updated Initial Project Schedule and be in a position to succinctly identify any needed changes understanding material extensions of the Initial Project Schedule may require additional Hexagon Services to be added via a Change Order. Once the list of changes has been made to the updated Initial Project Schedule by the Hexagon Project Manager, the Hexagon Project Manager will thereafter provide the Project Schedule to the Customer Project Manager. From time to time, the Parties’ Project Managers may modify the Project Schedule upon mutual written consent or upon transmission of an updated Project Schedule to the Customer Project Manager as part of a status report and the Customer Project Manager offers no objection to the updated Project Schedule within five (5) Business Days thereafter. At the Project Kickoff Meeting, the Customer shall provide: (i) contact information for all members of its Core Team and Executive/Departmental Sponsor, (ii) proposed alterations to the updated Initial Project Schedule, (iii) contact information for any third-party vendors which OnCall will integrate as contemplated in Attachment H, and (iv) identify to Hexagon any perceived concerns or risks with the Project. During the Project Kickoff Meeting, Hexagon shall provide template COTS Interface Questionnaires for Customer completion prior to required Tasks. Task Deliverables Kickoff meeting agenda Project Schedule Kickoff meeting minutes, to include identified risks and action items COTS Interface Questionnaire Dynamo e-learning licenses Detailed schema definition Task Prerequisites Agreement executed by both Customer and Hexagon and PO issued (if applicable). Hexagon Project Manager has verbally communicated with the Customer to (i) identify the Project Start date and (ii) coordinate a date for the Project Kickoff Meeting. Customer has assigned a Customer Project Manager. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 10 The Core Team has reviewed this SOW. Task Assumptions The Hexagon Project Manager will conduct the kickoff. This task will be conducted on site. Some members of the Hexagon Project Team may participate remotely. The Dynamo e-learning subscription commences during this Task and lasts for a duration of twelve (12) months from the date issued. Hexagon Team Participation and Responsibilities Hexagon shall: Review the Project organization, roles, and responsibilities with the Customer; Conduct an overview of the Project including a review of the SOW to verify all aspects of the Project approach; Review the draft Updated Initial Project Schedule and adjust the Updated Initial Project Schedule as needed and mutually agree upon it with Customer; Work with Customer to identify and document any potential Project risks; Provide meeting minutes that document risks and action items that affect the Project Schedule, resources, and/or the SOW; Inform the Customer of VPN requirements for Project implementation and continued System maintenance; Review of delivery methodology; Provide the Dynamo e-learning licenses for use by the Customer Core Team; Establish status reporting requirements; and Provide overview of Standard Interfaces being delivered as part of the Project as identified in Attachment H. Provide detailed schema definition Customer Team Participation and Responsibilities Customer shall: Review the SOW; Ensure its Core Teams attend the applicable portions of the Kickoff Meeting; Provide SMEs and any other resources as recommended by the Customer and Hexagon Project Managers; Provide Hexagon with VPN access and individualized user accounts to Customer’s System as appropriate for this Project and continued software maintenance; Have previously reviewed the Updated Initial Project Schedule and work with Hexagon to finalize the Updated Initial Project Schedule; Provide location and logistical support for Kickoff Meeting; and Designate and prepare workspace for Hexagon personnel. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 11 Task Acceptance Criteria This Task is complete at the conclusion of the Project Kickoff Meeting and delivery of the Project Kickoff meeting minutes to Customer. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 12 2. COTS Interface Questionnaire Completion Task Description Hexagon will provide an interface questionnaire (“COTS Interface Questionnaire”) to the Customer to complete. The Customer shall complete the COTS Interface Questionnaire within five (5) Business Days of receipt (“COTS Interface Review Period”) whereupon Hexagon will be able to install the COTS Interface and configure it based upon the information provided in the COTS Interface Questionnaire subject to the functionality and features within the COTS version of the Interface. The following Interfaces are regarded as the COTS Interfaces (collectively, "COTS Interfaces”): ANI/ALI Interface (included with HxGN OnCall Dispatch | Advantage) HxGN ONCall Dispatch | ProQA HxGN OnCall Dispatch | Informer HxGN OnCall Dispatch | Fire Station Printing HxGN OnCall Dispatch | CAD Link HxGN OnCall Dispatch | Fire Link HxGN OnCall Dispatch | Tracker CCU HxGN OnCall Dispatch | Notifications Avigilon VMS Interface For more information on, parameters of, and assumptions underlying the COTS Interfaces, see Attachment H, Interface Descriptions. Task Deliverables Completed COTS Interface Questionnaires Task Prerequisites Project Kickoff Meeting Task is complete. Hexagon has submitted COTS Interface Questionnaires to Customer. Task Assumptions The Customer will direct its third-party vendors to provide any API or specification documentation required to configure the COTS Interfaces. If required, all NDAs between Hexagon and third parties will be executed and current. The Customer will exercise all reasonable efforts to facilitate its third-party vendors reasonable cooperation with this requirement. The Customer will exercise all reasonable efforts to facilitate cooperation and information from its third-party vendors and/or state agency as reasonably necessary for the configuration, testing, and Cutover of the COTS Interfaces. Unless otherwise provided in the Specifications, only COTS versions of the COTS Interfaces will be provided and configured. The Customer shall be responsible for underlying requirements pertaining to its third-party systems as described in Attachment H. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 13 The ANI/ALI interface component of the OnCall Dispatch System will provide the interface to an ANI/ALI controller. It will accept ANI/ALI packets containing ASCII data via an Ethernet Network (TCP/IP) or a Serial COM Port connection. If the Customer’s ANI/ALI feed is via Serial COM Port the Customer will need to obtain an IP to Serial device. Hexagon Team Participation and Responsibilities Hexagon shall: Review completed COTS Interface Questionnaires. Customer Team Participation and Responsibilities Customer shall: Promptly review, complete, and submit COTS Interface Questionnaires and provide comments, questions, or approval within the COTS Interface Review Period. Task Acceptance Criteria This Task is complete upon Hexagon providing the COTS Interface Questionnaires and reviewing Customer’s responses it provided within the COTS Interface Review Period. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 14 3. OnCall Dispatch & Mobile Unit Launch Task Description OnCall Dispatch & Mobile Unit Launch (“Launch Workshop”) is a workshop style session lasting up to three (3) Business Days that is intended to educate Dispatch and Mobile Core Team members on the features and functionality of OnCall Dispatch and OnCall Dispatch Mobile Unit to support the collection and importation of data and information that CAD requires to execute its primary functions (“CAD Static Data”). During the Launch Workshop, Hexagon will provide limited instruction on the use of OnCall Dispatch and OnCall Dispatch Mobile Unit illustrating how the CAD Static Data elements identified below are utilized in the Subsystem. The Launch Workshop is limited in scope to facilitate upcoming System Build Tasks; it is not intended or designed to provide a comprehensive overview or instruction of the Subsystem. Such instruction and training will be provided at later stages of the Project. At the conclusion of the Launch Workshop, Hexagon shall provide to Customer OnCall Dispatch Static Data Collection Spreadsheet(s) to facilitate Customer’s collection and eventual importation of CAD Static Data in subsequent Tasks. Task Deliverables OnCall Dispatch Static Data collection spreadsheets Task Prerequisites Project Kickoff Meeting Task is complete. Customer Dispatch Core Team is identified. Customer Mobile Core Team is identified. Task Assumptions Launch Workshop is conducted using a Hexagon-provided default OnCall Dispatch & Mobile Unit environment. Hexagon responsibilities will be executed on site at a Facility. The Launch Workshop shall last no more than three (3) Business Days. Customer has provided a Facility. Hexagon Team Participation and Responsibilities Hexagon shall: Provide limited, focused instruction on the use of OnCall Dispatch, OnCall Mobile Unit, and OnCall Dispatch Administrator, on functional areas that utilize or display the following CAD Static Data elements: Agencies Special Situation Types Unit Types (Patrol, Engine, etc.) Personnel/User Accounts Units Beats/Station Areas Event Types Dispatch Groups Disposition Codes Stations (Police Stations, Sub-Stations, Fire Stations, etc.) Out-of-Service Types Number Formats (event, case, etc.) Facility Service Types Rotational Services (towing, ambulance, lock smith, etc.) Known Caller Types Vehicles Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 15 Provide the Customer with Microsoft Excel based data collection spreadsheets (“OnCall Dispatch Static Data Collection Spreadsheets”) to be used in assembling the CAD Static Data elements. Customer Participation and Responsibilities Customer shall: Provide a facility according to the requirements provided in Task Assumptions; Ensure appropriate members of the Dispatch Core Team and Mobile Core Team attend the workshop for the entire Launch Workshop; and Participate in discussions and engage with the Hexagon team member. Task Acceptance Criteria This Task is complete upon conclusion of the Launch Workshop and the delivery of the OnCall Dispatch Static Data Collection Spreadsheets. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 16 4. OnCall Dispatch GIS Requirements Review – Web Conference Task Description Over the course of up to one (1) Business Day, Hexagon will present on the following topics during the “OnCall Dispatch GIS Requirements Review”. This Task introduces the Customer GIS team to the GIS services the Customer must provide and which OnCall requires in order to function. Those services are, at a minimum an address locator service, a routing service, and a base map display service. Hexagon will also cover the deployment related polygon feature classes required to facilitate the assignment of geographic areas to specific agencies. Introduction to OnCall Dispatch GIS data requirements (see Attachment J) Optional GIS data elements that can be used by OnCall Dispatch This session will use Hexagon-provided GIS data for the purposes of discussion. Hexagon will use its equipment to conduct any demonstrations that may occur. Customer attendance should be limited to GIS professionals with responsibility for the creation and maintenance of Customer GIS data. Up to six (6) Customer personnel may attend. Map content will be provided to the OnCall Dispatch system through map layers and web services to be provided by the Customer. Task Deliverables OnCall Dispatch GIS Requirements Review Task Prerequisites Project Kickoff Meeting Task is complete. Task Assumptions Appropriate facilities have been identified to support the number of attendees (if co-located), including an LCD projector and a projection screen. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct the OnCall Dispatch GIS Requirements Review. Customer Team Participation and Responsibilities Customer shall: Ensure its GIS/Map Administrator is involved throughout this Task; Supply facilities, including an LCD projector and a projection screen; Designate and assign no more than four (4) Customer mapping/GIS personnel to attend the entire workshop. Two (2) additional people may attend as observers/auditors; and Ensure that all appropriate Customer GIS professionals are sufficiently trained and experienced in GIS fundamentals. Task Acceptance Criteria The Task is complete after the OnCall Dispatch GIS Requirements Review is conducted. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 17 5. Custom Interface Requirements Gathering Task Description During this Task, Hexagon and Customer will meet via conference call to validate the assumptions and design of each Custom Interface identified in this SOW and Attachment H (Interface Descriptions). This Custom Interfaces Requirements Gathering workshop is intended to contain a series of discussions to validate the requirements and assumptions underlying the Custom Interfaces. These sessions should include third-party vendors where appropriate. During the sessions, the specific workflow and data requirements for each of the interfaces listed below will be discussed in detail. The information obtained in combination with the information in Attachment H will be used to develop an Interface Control Document for each Custom Interface. If the assumptions reflected in Attachment H materially change, a Change Order may be appropriate. The ICDs will become the foundation for the Custom Interface development by Hexagon. Once an ICD is mutually approved, it should only be modified through a Change Order. The Customer shall not make any changes to and shall take appropriate actions to prevent its third-party vendor from making substantive changes to the third-party software that is the subject of a Custom Interface once that Custom Interface’s respective ICD has been finalized. The following are regarded as “Custom Interfaces” as the term is defined in Attachment I of this SOW: Text to 911 Query to OneSolution CAD Query to OneSolution RMS For descriptions and assumptions regarding each Custom Interface listed above, please see Attachment H: Interface Descriptions. As it pertains to the development of the ICD, the parties shall follow the following process. After the Customer provides the necessary information regarding the Custom Interface, Hexagon will prepare a draft ICD for each Custom Interface. Hexagon will then provide the initial draft ICD to the Customer for its review. The Customer shall review the draft ICD and provide any feedback or comments within ten (10) Business Days. As appropriate, Hexagon will incorporate the feedback into the ICD or advise the Customer why certain requests could not be included (e.g. the request conflicted with Attachment H) and finalize the ICD. Hexagon will provide the finalized ICD to the Customer for its written acknowledgement. The Customer will provide a response within three (3) Business Days from Hexagon providing the finalized ICD. Task Deliverables Workshop meeting minutes, to include notes on the specific workflow and data requirements for each custom interface proposed ICD documents Task Prerequisites Project Kickoff Meeting Task is complete. Task Assumptions The Customer will coordinate interactions with the third-party vendors, including obtaining and providing any API or specification documentation required to develop the proposed interfaces. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 18 If required, all NDAs between Hexagon and third parties will be executed and current. Customer is responsible for facilitating its third-party vendors reasonable cooperation with this requirement. The Customer is responsible for obtaining cooperation and information from its third-party vendors and/or state agency as reasonably necessary for the development, testing, and cutover of the interfaces. Hexagon Team Participation and Responsibilities Hexagon shall: Lead the interface requirements gathering process and track outstanding items requiring resolution; Confer with Customer and third-party points of contact to gather information required to develop ICDs; Validate the third-party points of contact are appropriate sources of information necessary to develop ICD; Mutually agree with the third-party vendors on the operational and technical interface requirements; Gather all available interface data detailed schema, protocols, and specifications, as needed; Prepare draft ICDs and submit to Customer for feedback; Incorporate Customer feedback into draft ICDs; Finalize ICDs for Customer review and approval; and Manage the approved ICDs consistent with the change control process. Customer Team Participation and Responsibilities Customer shall: Identify and set up appropriate facilities; Provide points of contacts who are knowledgeable of the workflow and data requirements for Customer hardware and software components with which the Custom Interfaces will interact; Provide or have available all necessary information during the workshop to facilitate the creation of the ICD; Promptly review all draft ICD submissions and provide comments, questions, or approval within ten (10) Business Days of receipt; and Agree to and sign the ICDs before any development work can begin. Failure to approve in a timely manner may impact Project Schedule and incur additional cost. Task Acceptance Criteria This Task is complete upon completion of all ICDs and execution of the ICDs by both Hexagon and the Customer. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 19 6. Custom Interface Development Task Description During this Task, Hexagon will develop the Custom Interfaces based upon the ICDs that were created from the Custom Interface Requirements Gathering Task. Task Deliverables Custom Interface documentation Task Prerequisites Custom Interface ICDs have been executed by each Party. Task Assumptions Any changes to a third-party interface developed by Hexagon that will alter the agreed-upon ICD will have to be reflected in a mutually executed document, which may include a Change Order. Development of the Custom Interface shall not commence until the signed/approved ICD is returned to Hexagon. Failure to approve in a timely manner may impact project schedule and incur additional cost. Hexagon Team Participation and Responsibilities Hexagon shall: Develop the Custom Interfaces based upon the ICD. Customer Team Participation and Responsibilities Customer shall: Ensure SMEs are available as needed; and Obtain third-party cooperation as reasonably requested by Hexagon. Task Acceptance Criteria This Task is complete when all Custom Interfaces are developed. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 20 7. Load Balancer Equipment Ordering Task Description Hexagon resources will order the load balancer components as required for the virtual environments as specified in Attachment F (System Configuration Diagram, Hardware specifications, BOM items listed as Hexagon furnished) of this SOW. Task Deliverables Estimated delivery date of Kemp load balancers Task Prerequisites Equipment requirements have been finalized. Project Kickoff Meeting Task is complete. Task Assumptions N/A Hexagon Team Participation and Responsibilities Hexagon shall: Order the Kemp load balancers. Customer Team Participation and Responsibilities Customer shall: N/A Task Acceptance Criteria This Task is complete when Hexagon resources have ordered the Equipment specified in this Task. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 21 Staging Phase 8. Physical Infrastructure Installation Task Description This Task involves Customer physically installing the servers and storage into the datacenter and the configuration of the physical servers and storage that will host the virtual environment. Task Deliverables Customer staging of the physical infrastructure Task Prerequisites Project equipment is ordered and received. Customer must have the license keys for their hypervisor, SQL developer and Windows software. If such license keys were purchased by Hexagon for Customer, then Customer will have received an email and shall have downloaded these license keys. The Customer has completed the Infrastructure Build Document provided by Hexagon which includes a list of server names and IPs and service account requirements and other various information. Task Assumptions New servers will be created\provided for staging the Hexagon software and are for the sole purpose of Hexagon Software and will not serve other roles. Hexagon Team Responsibilities Hexagon shall: Provide the VMware based VM templates, if desired, to the customer via electronic download (FTP, File copy, etc.). There will be two (2) files totaling approximately 30GB; and Assist the Customer with importing the Hexagon-provided templates to the templates datastore. All VMs will be created from these templates. Customer Team Responsibilities Customer shall: At each site: Provide Rack Space for the server equipment; Provide Power in the rack; Provide Network connections for the provided equipment on the appropriate VLANs; Provide adequate cooling for the servers; Provide required server names and IPs for all of the equipment; Provide domain level credentials to join servers to the domain; Provide assistance with resolving issues related to network connectivity and\or remote access; Perform the physical installation of the Project equipment in Customer datacenter or location specified in advance by Customer; Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 22 Connect the HP ILO or Dell iDRAC, assigning an IP Address and\or license to those to allow remote access; Make connections between the servers and storage, as required; Assign an IP Address to the storage array to allow connectivity for full configuration; Connect to the servers license the hypervisor host OS if required; Configure storage to be presented to the hosts; Configure the networking on each host to provide two (2) virtual switches each configured with two (2) NICs. The first virtual switch will support hypervisor management connectivity and VM migration (10 gig). The second virtual switch will support the Production VM traffic (1 gig); and Configure the virtual switch that will be utilized by the virtual Kemp load balancers to change the following settings: MAC address changes from reject to accept. Forged Transmits from reject to accept. Answer other configuration questions as they arise. Task Acceptance Criteria This Task is complete when: (i)(a) Customer has all designated Project server hardware staged and (b) the physical servers and storage that will host the virtual environments configured and, (ii) Hexagon has provided the VM templates to the Customer. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 23 9. Virtual Server and OnCall Software Staging Task Description This Task is intended to facilitate the installation and configuration of virtual machines, Microsoft SQL Servers utilizing SQL Developer edition, the client specific OnCall software suite, associated Third Party Software, and load balancers. This Task will occur in multiple steps. This Task will result in a working environment that will be configured in future tasks. Hexagon will perform all related tasks as described via the Hexagon OnCall Management Tool which utilizes PowerShell for automation of the tasks described herein. Hexagon will initially confirm the hardware has been configured and set up according to Hexagon standards and able to receive the Software. If deviations are identified, Hexagon will notify the Customer and the Customer will take prompt action to address the deviation. Hexagon will begin this Task by working with the customer to install the virtual servers into the virtual environment identified by the Customer. Hexagon will work with the customer to create the virtual servers, assigning them the required CPU, memory, and disk space, set server names and IP addresses, and join the virtual servers to the domain. Hexagon shall also work with the customer to create GPO to add Hexagon Administrator groups to the local administrator groups of the servers to allow Hexagon the required access for this Project. Hexagon will also complete the following SQL Implementation Steps: Create SQL Service Accounts, install and configure Windows Failover Clustering, enable and configure SQL AlwaysOn Availability group(s) with an associated Availability Group Listener, and Test SQL AlwaysOn Availability Group(s) for proper failover. Hexagon will install and perform initial configuration of the Hexagon OnCall Product Suite included in this Project. Hexagon shall stage and install Software Products on the virtual servers, which includes creating the directory, setting up folder permissions, installing the Hexagon license servers, and installing and setting up Software Products. Software installed during this Task does not constitute a fully configured system. Additional configuration Tasks are described later in this SOW. Hexagon will install and configure the load balancers. Hexagon and Customer will hold a meeting to discuss and provide consultation regarding which URLs will be used by the load balancers (“Load Balancer Meeting”). The Customer will ultimately determine and be responsible for the selection of the URLs that will be utilized by the OnCall Product Suite. Hexagon will use those URLs to configure the load balancer VIPs. The load balancers will be configured for GSLB (Global Site Load Balancing) and or HA (High Availability). Special DNS entries will need to be made to delegate the name resolution of the URLs if using GSLB. The Customer should test the configuration of the load balancers. As part of this Task, Hexagon will initiate the Site Configuration document. At this stage this document is a draft that will be updated throughout the Project. Task Deliverables Draft Site configuration Document Installation of OnCall Product Suite(s) URLs configured on the Load Balancers Ability to login to most of the applications (Some require additional configuration before functional, like OnCall Analytics) Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 24 Task Prerequisites Customer has completed and returned the Infrastructure Build Document to Hexagon. Customer has installed and configured the hypervisor Virtual Infrastructure in accordance with Attachment F. The hypervisor host have the virtual switch that will be utilized by the virtual Kemp load balancers have had the following settings changed: MAC address changes from reject to accept. Forged Transmits from reject to accept. Customer has downloaded the Hexagon provided software. Customer has uploaded the ESRI Media ISO to a datastore available to Hexagon, if applicable. Customer has imported the Hexagon provided templates. Customer has placed Hexagon and required third party licenses that have been provided to the Customer and placed on a network share accessible by Hexagon. Task Assumptions The Virtual Infrastructure is Nutanix. New virtual servers will be for the sole purpose of the Project defined by this SOW and will not serve other roles. Hexagon will require the following permissions during the Project. Administrative access to the hypervisor management console that the VMs will be created in. Domain Administrator level permission on the domain to allow the following: Join virtual servers to the domain Create Computer Objects Create server clusters Create and manage DFS configurations Create users and groups Add\modify DNS entries in support of the Load balancer configuration Hexagon Team Participation and Responsibilities Hexagon shall: Perform Virtual Server Implementation with customer assistance when not a VMware environment Install SQL and configure the SQL AlwaysOn Availability group and the MS Windows Failover Cluster Perform the Software Installation Configure Hexagon Licensing Servers Host the Load Balancer Meeting Provide the Draft Site Configuration Documentation Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 25 Customer Team Participation and Responsibilities Customer shall: Provide information, credentials, and access to systems, the network, VMs, domains, as requested by Hexagon to facilitate Hexagon completing this task. Answer questions as needed. Promptly address any deviations in hardware, operating system, database software from what is required in Attachment E and F. Task Acceptance Criteria This Task is complete when Hexagon has completed the Software Installation and provided the Draft Site Configuration Documentation to Customer. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 26 10. OnCall Dispatch GIS Consulting Task Description A central feature of OnCall Dispatch is interoperation and use of Customer provided GIS services within OnCall Dispatch. The Customer may use whichever map provider they choose, subject to Attachment J. The objective of this Task is to collaborate with the Customer’s GIS Administrator regarding use of the Customer-provided map services within OnCall Dispatch and management of the source map. Over the course of up to three (3) consecutive weeks (“GIS Consulting Period”) a Hexagon technical resource will host meetings with the Customer GIS Administrator and any other interested Customer SMEs, which in the aggregate shall last no more than twenty-four (24) Business Hours (“GIS Meeting Time”). The OnCall Dispatch GIS Consulting is intended to be a collaborative session and for Hexagon and the Customer GIS Administrator to discuss use of the map services within OnCall Dispatch and management of the map services in the context of OnCall Dispatch. As time permits, the parties can discuss other GIS related topics. To facilitate a productive session, the Customer GIS Administrator, at a minimum, should have participated in the OnCall Dispatch GIS Requirements Review. The Customer shall also have complied with the mapping requirements prior to this Task. As a result of the sessions, the Customer’s GIS Administrator will have been provided additional insight and information on how to manage and use the map services in connection with OnCall Dispatch. For purposes of clarity, these sessions are not intended to result in configuration or modification of Customer’s source map data. The Customer may configure the map services at its discretion up to the commencement of Functional Testing. At the commencement of Functional Testing, the Customer shall refrain from making any modification or configurations to the map services until after System Cutover. Task Prerequisites OnCall Dispatch GIS Requirements Review Task is complete. Task Assumptions The Customer GIS Administrator has sufficient authority to make decisions about the use, configuration, and integration of the source map data. Hexagon will not provide training or services specific to Esri software. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct the GIS Consulting through a Hexagon technical resource. Customer Team Participation and Responsibilities Customer shall: Manage and make any desired configurations to the Customer-provided map data; and Ensure appropriate GIS resources attend GIS consulting session(s). Task Acceptance Criteria This Task is complete upon the earlier of: (i) use of all of the GIS Meeting Time or (ii) end of the GIS Consulting Period. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 27 11. OnCall Dispatch System Build 1 Task Description OnCall Dispatch System Build 1 workshop (“System Build 1”) builds upon the OnCall Dispatch and Mobile Unit Launch to begin the process of populating OnCall with required static data elements. System Build 1 is the first of two (2) static data workshops and primes OnCall Dispatch with base data to support the buildout of remaining static data elements addressed in OnCall Dispatch System Build 2 and the OnCall Dispatch Deployment & Response Planning Workshop. At the commencement of System Build 1, the Customer shall have obtained information and documents (e.g., records, operating procedures, resources, etc.) to support the eventual entry or import of the Build 1 Data Elements. For any Build 1 Data Elements not entered or imported during System Build 1, the Customer will enter those after System Build 1 within ten (10) Business Days and prior to OnCall Dispatch System Build 2. During System Build 1, the focus will be on the entry and import of Build 1 Data Elements (as defined below). System Build 1 will last no longer than three (3) Business Days. As part System Build 1, the Customer will be instructed in the use of OnCall Dispatch Administrator to facilitate the manual entry of static data elements. This instruction is critical to provide an understanding of the process of creating and managing static data and the relationships between static data elements. Some manual entry of all static data elements is required as part of the workshop. Bulk import of remaining data can occur after sufficient understanding of the data elements and relationships is obtained. Following System Build 1, OnCall Dispatch will have foundational data elements to support future build activities. Task Deliverables OnCall Dispatch System Build 1 workshop Task Prerequisites OnCall Dispatch & Mobile Unit Launch Task is complete. Virtual Server and OnCall Software Staging Task is complete. OnCall Dispatch GIS Consulting Task is complete. Initial GIS services published and configured for use by OnCall Dispatch: Map display Routing Geocoding Task Assumptions Hexagon responsibilities will be executed on site at a Facility. System Build 1 is conducted using the Customer’s OnCall Dispatch environment. System Build 1 will last no more than three (3) Business Days. Hexagon Team Participation and Responsibilities Hexagon shall: Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 28 Host System Build 1 during which, limited, focused instruction on the use of OnCall Dispatch, OnCall Mobile Unit, and OnCall Dispatch Administrator, on functional areas that utilize or display the following static data elements (“Build 1 Data Elements”): Agencies Special Situation Types Unit Types (Patrol, Engine, etc.) Personnel/User Accounts Units Beats/Station Areas Event Types Dispatch Groups Disposition Codes Stations (Police Stations, Sub- Stations, Fire Stations, etc.) Out-of-Service Types Number Formats (event, case, etc.) Facility Service Types Rotational Services (towing, ambulance, lock smith, etc.) Known Caller Types Vehicles Provide the Customer with Microsoft Excel based data collection spreadsheets to be used in assembling the Build 1 Data Elements for importation into the Dispatch Subsystem. Customer Participation and Responsibilities Customer shall: Ensure appropriate Dispatch and Mobile Core Team members attend and actively participate during the System Build 1 for the entire duration; Provide a Facility; Provide a Project Workstation to each attendee; Provide all necessary information and documents to facilitate importation of Build 1 Data Elements at the outset of System Build 1; and Participate in discussions and engage with the Hexagon team member. Task Acceptance Criteria This Task is complete upon conclusion of System Build 1. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 29 12. OnCall Dispatch Deployment & Response Planning Workshop Task Description This workshop, “Deployment and Response Planning Workshop,” builds upon System Build 1 to begin the process of creating the deployment and response planning components of OnCall Dispatch. The Deployment and Response Planning Workshop is intended to facilitate importation with deployment data necessary to successfully execute the OnCall Dispatch System Build 2 and the subsequent OnCall Dispatch configuration workshops. As part of the Deployment and Response Planning Workshop, Customer will be taught about the OnCall Dispatch deployment model which details how OnCall Dispatch determines responding agencies for events. Customer will also be taught about the OnCall Dispatch unit recommendation model, how to build response plans, and briefed on the parameters which control how OnCall Dispatch processes response plans. The Deployment and Response Planning Workshop shall last no longer than three (3) Business Days. At the outset of Deployment and Response Planning Workshop, the Customer must have obtained and have necessary information and documents to facilitate eventual creation of the Deployment Plans, and Response Plans (as defined below). The Deployment and Response Planning Workshop is intended to provide the Customer experience on how to build Deployment Plans and Response Plans; it is not expected or intended that all such Deployment Plans and Response Plans will be completed during the Deployment and Response Planning Workshop. The Customer will be expected to complete the build of any necessary Deployment Plans and Response Plans within ten (10) Business Days prior to the commencement of System Build 2. Task Deliverables OnCall Dispatch Deployment & Response Planning Workshop Task Prerequisites OnCall Dispatch System Build 1 Task is complete. Necessary Build 1 Data Elements have been imported into the Dispatch Subsystem to facilitate the build of Deployment Plans and Response Plans. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. Workshop is conducted using the Customer’s OnCall environment. Deployment and Response Planning Workshop shall last no longer than (3) Business Days. Hexagon Team Participation and Responsibilities Hexagon shall: Provide formal instruction on the OnCall Dispatch deployment model (“Deployment Plans”): Deployment plans Emergency Service Zones Beats & Backup Beats Dispatch Groups Provide formal instruction on the OnCall Dispatch response planning model (“Response Plans”): Recommend unit service: Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 30 Number of recommend unit services needed Recommend search area Recommend method (beats, street network, closest) Recommend unit parameters Response plans: Requirements Requirement Groups Conditions Nested plans Support Customer buildout of deployment and response plans. Customer Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Ensure appropriate Dispatch and Mobile Core Team members attend and actively participate during the Deployment and Response Workshop over the entire duration; Bring maps, documents, or other materials that detail the agency deployment model(s) and Deployment Plans; Bring materials that document or detail the agency unit recommendation model(s) and Response Plans; and Build deployment and response plans with Hexagon guidance during the Deployment and Response Planning Workshop and independently following Deployment and Response Planning Workshop. Task Acceptance Criteria This Task is complete at the conclusion of the Deployment and Response Planning Workshop. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 31 13. OnCall Dispatch System Build 2 Task Description This OnCall Dispatch System Build 2 Workshop (“System Build 2”) finalizes Hexagon-led system build activities and completes the enablement of the Dispatch and Mobile Core Teams to continue build related activities for the remainder of the project. The same Dispatch and Mobile Core Team members who participated in System Build 1 and the Deployment and Response Planning Workshop shall attend System Build 2 to ensure continuity of decisions and facilitating continuing to build upon previous workshops. Additionally, System Build 2 focuses on reviewing data entered into the Subsystem for level of completion and analyzing whether data was entered/imported correctly. New topics to be covered as part of System Build 2 are contact directory, message groups, message templates, lineups, ORIs, special addresses, and common place names. System Build 2 shall last no longer than three (3) Business Days. While certain updates or modifications to the static data may occur during the Configuration Phase, the Customer shall upload all of its static data within ten (10) Business Days following System Build 2. Task Deliverables OnCall Dispatch System Build 2 Workshop Task Prerequisites OnCall Dispatch Deployment & Response Planning Workshop Task is complete. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. Workshop is conducted using the Customer’s OnCall environment. System Build 2 will last no more than three (3) Business Days. Hexagon Team Participation and Responsibilities Hexagon shall: Load deployment polygons into the OnCall Dispatch database; Provide support to Customer teams while continuing the system build efforts; Review with the Customer teams the data entered to date for accuracy and level of completion; and Provide feedback on the build progress and areas that need focus or attention. Customer Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Ensure past participants in System Build 1 and Deployment and Response Workshop attend System Build 2 for the entire duration; Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 32 Provide at the outset of System Build 2 all necessary information and documents to: facilitate review of Build 1 Data Elements, Response Planning Parameters, Deployment Parameters, and new elements stated above; Participate in discussions and engage with the Hexagon team member; Complete any outstanding entry or import of static data within ten (10) Business Days following the end of System Build 2. Task Acceptance Criteria This Task is complete upon conclusion of System Build 2. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 33 Configuration Phase 14. OnCall Dispatch Fundamentals for Core Team Task Description The OnCall Dispatch Fundamentals for Core Team course is presented directly to Dispatch and Mobile Core Team personnel to provide complete instruction on the use of the OnCall Dispatch and Mobile Unit applications. The course shall last no longer than four (4) Business Days. This course is intended to instruct the Dispatch and Mobile Core Teams with the features of OnCall Dispatch and Mobile Unit, including event processing and dispatching, map utilization, and inquiries. The following major topics will be reviewed, as applicable: HxGN OnCall Dispatch | Advantage functions: Event Creation and Updates Map View Control Inquiries Messaging Recommending and Dispatching Units Updating Unit Statuses and Properties HxGN OnCall Dispatch | Mobile Unit functions: Accessing the system Event Updates Unit Status Changes Messaging Task Deliverables OnCall Dispatch Fundamentals for Core Team course Task Prerequisites System Build 2 is complete. Completion by Customer attendees of an introductory Microsoft Windows course or equivalent knowledge and familiarity with the Microsoft Windows user interface. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. The course shall last no longer than three (4) Business Days. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct OnCall Dispatch Fundamentals for Core Team course. Customer Team Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Ensure appropriate personnel who have attended an introductory MS Windows course, or have comparable education, training, or experience, participate fully and collaboratively in the session; Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 34 Designate the Dispatch and Mobile Core Team members for attendance and ensure those same participants participate in subsequent Dispatch and Mobile configuration and testing Tasks; Provide sufficient copies of the training materials supplied by Hexagon to support all students in the Core Team Training; Ensure that all training workstations and servers are operational prior to the agreed start of training classes; and Provide internal training to users that are unable to attend the Hexagon-provided training. Task Acceptance Criteria This Task is complete upon delivery of the OnCall Dispatch Fundamentals for Core Team course. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 35 15. COTS Interface Product Installation and Configuration Task Description During this Task, Hexagon will install and unit test the COTS Interfaces in the Customer’s Production Environment. Hexagon will be able to install the COTS Interface and configure it based upon the information provided in the COTS Interface Questionnaire subject to the functionality and features existing within the COTS version of the COTS Interface. To facilitate Hexagon’s implementation and configuration of the COTS Interfaces, the Customer shall make available or provide access to all third party software components which are intended to integrate with the Dispatch Subsystem through the COTS Interface(s). Although the Customer is expected to participate in Hexagon’s internal testing of the COTS Interfaces, the Customer will formally test interface functionality during Functional Testing Task. Task Deliverables Installation and configuration of the COTS Interfaces which are listed in the COTS Interface Questionnaire Completion Task above. For more information on the COTS Interfaces, see Attachment H, Interface Descriptions. Task Prerequisites Operation or availability of all external systems or Third-Party Software. Completed COTS Interface Questionnaires provided to Hexagon during the COTS Interface Review Period. Virtual Server and OnCall Software Staging Task is complete. Hexagon Team Participation and Responsibilities Hexagon shall: Install COTS Interfaces in the Customer’s Production and Disaster Recovery Environments; and Unit test interfaces in accordance with the COTS Interface Questionnaires. Customer Team Participation and Responsibilities Customer shall: Ensure SMEs are available to support Hexagon Activities as needed; Verify that physical connectivity and communication has been achieved from Customer’s Communication/Interface server to remote system servers and all other third-party systems (such as Customer message switch(es), State/NCIC, RMS systems etc.); Provide availability and confirm operation of external systems or third-party software; Provide the following information to Hexagon: IP address for remote databases/systems Socket value for remote databases/systems Enter operator IDs (ORIs), terminal mnemonics, etc., as needed by remote databases/systems Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 36 Ensure the system and network administrators are available to work closely with the Hexagon team for the duration of the Task; and Ensure third-party cooperation with Hexagon’s reasonable requests. Task Acceptance Criteria This Task is complete when each COTS Interface is installed and configured in accordance with the COTS Interface Questionnaire, and subject to the functionality and features within the COTS version of the COTS Interface. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 37 16. CommSys ConnectCIC Installation Task Description During this Task, Hexagon will utilize the CommSys ConnectCIC State Interface middleware product to interface with the state message switch for the following state and national transactions. The CommSys ConnectCIC middleware product will work with the Customer’s Informer interface to support the transactions listed below. Person (In State and NLETS) (QW, DQ, QM) Wanted/Warrants Missing Driver’s license Driver's license history Vehicle (In State and NLETS) (QV, RQ) Wanted/stolen Registration Vehicle Parts Gun by (serial, caliber, make) (QG) Article (serial, type) (QA) Boat (In State and NLETS) (QB, BQ) Hull Number Registration ID Administrative Message (AM) Canadian Queries Person Driver’s License/Want (WQ, UQ) Vehicle Registration/Want (VQ, XQ) Boat by License, Hull, Registration (CBQ) Gun by Serial (CGQ) Article by Serial (CAQ) Secondary Person (Nested Query) Surrounding States Parsing HxGN OnCall Dispatch | Informer Interface will support the queries to NCIC (via CommSys ConnectCIC) from Dispatch and Mobile Unit. Task Deliverables CommSys ConnectCIC setup and installation Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 38 Task Prerequisites COTS Interface Product Installation and Configuration Task is complete. Task Assumptions Primary agency shall be the Customer. The supported transactions include basic queries. This Project does not include the development of any new forms, queries, or transactions for Informer unless specifically identified herein. First year maintenance for CommSys ConnectCIC shall begin upon Cutover. Hexagon Team Participation and Responsibilities Hexagon shall: Ensure CommSys has installed ConnectCIC State Interface middleware; and Work with CommSys to verify the ConnectCIC State Interface middleware product is set up and installed for the Customer agencies listed above. Customer Team Participation and Responsibilities Customer shall: Ensure that documentation detailing the format, development\design, and connection information (IP, protocol, credentials, etc.) is current and provided to Hexagon either by the State or by Customer. If this information is not provided by the State, Customer is responsible for collecting and determining if this information is valid and providing it to Hexagon. If the documentation is not provided to Hexagon, additional services\charges may be incurred by Customer; Have CJIS-related security in place as it relates to Informer data, transactions, and responses; Provide points of contact who are knowledgeable of the workflow and data requirements for Customer hardware and software components with which Hexagon deliverables will interface; Provide test connections to State/NCIC, as well as other external systems required for the Project; Provide live connections to State/NCIC, as well as other external systems required for the Project; Enter associated ORI, user credentials (if applicable), and terminal mnemonics; Provide test records to ensure that the transactions received by the System in a test environment are in the same format and contain the same information as those received in a Production environment; and Test and report any Defects to Hexagon within ten (10) Business Days of installation of ConnectCIC in Customer’s environment. Task Acceptance Criteria This Task is complete upon installation of the CommSys ConnectCIC product. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 39 17. OnCall Dispatch Configuration Consulting 1 Task Description The primary purpose of OnCall Dispatch Configuration Consulting is to teach the Customer how to use the features of OnCall Dispatch Administrator related to configuration. This includes the User Interface Editor, the Layout Manager, and Configuration Parameters. The Customer is solely responsible for completing all desired configurations of OnCall Dispatch and OnCall Mobile Unit necessary to achieve the Customer’s desired outcomes. Hexagon provides direct support in a time-boxed method as described in this task. During this Task, Hexagon will conduct the “Configuration 1 Workshop,” which will last no longer than three (3) Business Days. Hexagon will provide support for the Customer’s configuration activities for up to three (3) Business Days following the Configuration 1 Workshop (“Configuration 1 Period”). During the Configuration 1 Workshop, Hexagon and Customer will work collaboratively with one another to configure the Basic Settings, Viewing Settings, Call Taking Process Settings, Event Creation Settings, and UI Layouts (as defined below) with Hexagon providing instruction and guidance and the Customer executing the desired configuration changes. Up to the end of the Configuration 1 Period, Hexagon will support the Customer’s effort to configure the Configuration 1 Settings (as defined below) and subject to the Benchmark Criteria. After the Configuration 1 Period has expired, the Customer will be responsible for working independently on making any configuration changes to the Configuration 1 Settings that were not otherwise completed during the Configuration 1 Period or that Customer seeks to further configure. Scope of the configuration is limited to the capabilities described in the Benchmark Criteria. Not all requested product configuration may be possible. Task Deliverables OnCall Dispatch Configuration 1 Workshop Task Prerequisites Customer’s OnCall Dispatch Subsystem is available for use. Initial GIS services published and configured for use by OnCall Dispatch: Base Map display Routing Geocoding OnCall Dispatch Fundamentals for Core Team Task is complete. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. The Configuration 1 Workshop will last no longer than three (3) Business Days. The Configuration 1 Workshop will be interactive with up to twelve (12) Customer attendees for up to seven (7) Business Hours per day. Customer Dispatch Core Teams will record the list of requested configurations from each day, placing them in order of priority to be completed. Requested configurations to the Configuration 1 Settings not completed by the end of the Configuration 1 Period can be independently completed by the Customer, if so desired, which must be done prior to Configuration 2 Workshop. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 40 Hexagon Team Participation and Responsibilities Hexagon shall: Provide consulting and configuration services to review (collectively, “Configuration 1 Settings”): Customer’s preferences for basic settings, including but not limited to (collectively, “Basic Settings”): Colors for unit statuses Colors for event priorities Icons for event types on the map and event cards/boards Icons for unit types Customer’s needs for viewing event and unit related data in real-time lists (status monitors) (collectively, “Viewing Settings”): Filters Visible columns Context (right-click) menus Customer’s emergency and non-emergency call-taking processes, including but not limited to (collectively, “Call Taking Process Settings”): Location validation Event-type selection Jurisdiction determination Customer’s event creation processes, including but not limited to (collectively, “Event Creation Settings”): Single Agency Response Multiple Agency Response Nearby or possible duplicate detection User Interface Layouts (“UI Layouts”) Customer Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Ensure the attendance and active participation of the Dispatch Core Team members and other SMEs for the duration of the Configuration 1 Workshop; Participate in discussions and engage with the Hexagon team member; Track and prioritize requests for configuration of the Configuration1 Settings on a daily basis during the Configuration 1 Workshop; and Complete any changes to Configuration 1 Settings prior to the commencement of Configuration 2 Workshop. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 41 Task Acceptance Criteria This Task is complete upon: (i) the conclusion of the Configuration 1 Workshop and (ii) upon the earlier of, expiration of the Configuration 1 Period or configuration of the Configuration 1 Settings. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 42 18. OnCall Dispatch Configuration Consulting 2 Task Description The primary purpose of OnCall Dispatch Configuration Consulting is to teach the Customer how to use the features of OnCall Dispatch Administrator related to configuration. This includes the User Interface Editor, the Layout Manager, and Configuration Parameters. The Customer is solely responsible for completing all desired configurations of OnCall Dispatch and OnCall Mobile Unit necessary to achieve the Customer’s desired outcomes. Hexagon provides direct support in a time-boxed method as described in this Task. During this Task, Hexagon will conduct the “Configuration 2 Workshop”, which will last no longer than three (3) Business Days. Hexagon will provide support for the Customer’s configuration activities for up to three Business Days following the Configuration 2 Workshop (“Configuration 2 Period”). During the Configuration 2 Workshop, Hexagon and Customer will work collaboratively with one another to configure the Configuration 2 Settings (as defined below) with Hexagon providing instruction and guidance and the Customer executing the desired configuration changes. Up to the end of the Configuration 2 Period, Hexagon will support the Customer’s effort to configure the Configuration 2 Settings (as defined below) and subject to the Benchmark Criteria. After the Configuration 2 Period has expired, the Customer will be responsible for working independently on making any configuration changes to the Configuration 2 Settings that were not otherwise completed during the Configuration 2 Period or that Customer seeks to further configure. Scope of the configuration is limited to the capabilities described in the Benchmark Criteria. Not all requested product configuration may be possible. Task Deliverables OnCall Dispatch Configuration 2 Workshop Task Prerequisites Configuration 1 Workshop and Configuration 1 Period are complete, and Customer has completed any and all additional configurations to the Configuration 1 Settings. Connection established to Customer’s state crime system. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. Configuration 2 Workshop will last no more than three (3) Business Days. The Configuration 2 Workshop will be interactive with Customer attendees for up to seven (7) Business Hours per day. Customer Dispatch Core Team will record the list of requested configurations from each day, placing them in order of priority to be completed. Requested configurations to the Configuration 2 Settings not completed by the end of the Configuration 2 Period can be completed by the Customer, if so desired, which must be done prior to Configuration 3 Workshop. Hexagon Team Participation and Responsibilities Hexagon shall: Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 43 Provide consulting and configuration services to review the settings below (collectively, “Configuration 2 Settings”): Customer’s event triage and dispatching processes Customer’s event management processes, including but not limited to: Unit recommendation & assignment Unit on event management Unit location changes Staging areas Case numbers Remote inquiries Queued events Rotational services (e.g., Tow trucks, lock smiths, etc.) Call back process Known callers Unit relocation (a.k.a. Move Ups) Shared Crews (a.k.a. Cross-staffing) Field Events (a.k.a. Officer Initiated Events) Associated Events Copied Events Customer Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Ensure the attendance and active participation of the Dispatch Core Team members and other SMEs for the duration of the Configuration 2 Workshop; Participate in discussions and engage with the Hexagon team member; Track and prioritize requests for configuration of the Configuration 2 Settings on a daily basis during the Configuration 2 Workshop; and Complete any configurations changes to the Configuration 2 Settings prior to the commencement of Configuration 3 Workshop. Task Acceptance Criteria This Task is complete upon: (i) the conclusion of the Consulting 2 Workshop and (ii) upon the earlier of, expiration of the Configuration 2 Period or configuration of the Configuration 2 Settings. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 44 19. OnCall Dispatch Configuration Consulting 3 Task Description The primary purpose of OnCall Dispatch Configuration Consulting is to teach the Customer how to use the features of OnCall Dispatch Administrator related to configuration. This includes the User Interface Editor, the Layout Manager, and Configuration Parameters. The Customer is solely responsible for completing all desired configurations of OnCall Dispatch and OnCall Mobile Unit necessary to achieve the Customer’s desired outcomes. Hexagon provides direct support in a time-boxed method as described in this task. During this Task, Hexagon will conduct the “Configuration 3 Workshop”, which will last no longer than three (3) Business Days. Hexagon will provide support for the Customer’s configuration activities for up to three Business Days following the Configuration 3 Workshop (“Configuration 3 Period”). During the Configuration 3 Workshop, Hexagon and Customer will work collaboratively with one another to configure the Configuration 3 Settings (as defined below) with Hexagon providing instruction and guidance and the Customer executing the desired configuration changes. Up to the end of the Configuration 3 Period, Hexagon will support the Customer’s effort to configure the Configuration 3 Settings (as defined below) and subject to the Benchmark Criteria. After the Configuration 3 Period has expired, the Customer will be responsible for working independently on making any configuration changes to the Configuration 3 Settings that were not otherwise completed during the Configuration 3 Period or that Customer seeks to further configure. Scope of the configuration is limited to the capabilities described in the Benchmark Criteria. Not all requested product configuration may be possible. The Customer shall complete any desired configurations prior to the commencement of Customer Functional Testing Task. Task Deliverables OnCall Dispatch Configuration 3 Workshop Task Prerequisites Configuration 2 Workshop and Configuration 2 Period have been completed, and Customer has completed any additional configurations to the Configuration 2 Settings. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. The Configuration 3 Workshop will last no more than three (3) Business Days. The Configuration 3 Workshop will be interactive with Customer attendees for up to seven (7) hours per day. Dispatch Core Team will record the list of requested configurations from each day, placing them in order of priority to be completed. Requested configurations not completed upon consumption of all allocated labor hours can be completed by the Customer, if so desired, which must be done prior to the commencement of Customer Functional Testing. Hexagon Team Participation and Responsibilities Hexagon shall: Provide consulting and configuration services (“Configuration 3 Settings”) to review: Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 45 Biased based profiling data collection Notifications Standard Operating Procedures (SOPs) Event Tags Special Situations Event Security Unit Management Logging on Logging off Unit properties Logon Group (Lineup) CAD Searches Event search Unit history search Equipment Search Broadcasts (a.k.a. BOLOs) Customer Participation and Responsibilities Provide a Facility; Provide a Project Workstation for each attendee; Ensure the attendance and active participation of the Dispatch Core Team members and other SMEs for the duration of the Configuration 3 Workshop; Participate in discussions and engage with the Hexagon team member; Track and prioritize requests for configuration of the Configuration 3 Settings on a daily basis during the Configuration 3 Workshop; and Complete any configurations changes prior to the commencement of Customer Functional Testing. Task Acceptance Criteria This Task is complete upon: (i) the conclusion of the Consulting 3 Workshop and (ii) upon the earlier of, expiration of the Configuration 3 Period or configuration of the Configuration 3 Settings. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 46 20. OnCall Dispatch | Mobile Unit Configuration Consulting Session – Law Task Description Hexagon will conduct one (1) consulting session with the Customer lasting no more than three (3) Business Days as part of the Project (“Mobile Unit Law Configuration Session”). During the Mobile Unit Law Configuration Session, Hexagon will provide information regarding configuration options for Mobile Unit workflows as they pertain to the mobile environment. The Mobile Unit Law Configuration Session will address: Sign on/Sign off Brief Overview of Application Screen Layout Navigation Buttons Alerts Toolbars Event Search Menus and Submenus Map Messaging Unit Board Event Board The included Dispatch Report Network requirements and ports to ensure the Mobile Unit client can communicate appropriately The Customer will need to make available one dispatcher familiar with OnCall Dispatch to perform dispatching and other related tasks as necessary during the Mobile Unit Law Configuration Session. Following the Mobile Unit Law Configuration Session, the Customer will configure Mobile Unit during the next ten (10) Business Days (“Mobile Unit Law Configuration Period”). Hexagon will provide remote support for the Customer’s Mobile Unit Law configuration efforts (“Mobile Unit Law Configuration Consultation”) up to a maximum of two (2) Business Days. The Customer is responsible for configuring the Mobile Unit subsystem. Upon completion of this Task, the Customer will have one (1) mobile configuration of Mobile Unit for testing. Task Deliverables OnCall Dispatch | Mobile Unit Law Configuration Session OnCall Dispatch | Mobile Unit Law Configuration Consultation Task Prerequisites OnCall Dispatch Configuration Consulting 3 Task is complete. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 47 Attendance by the Customer’s personnel will be limited to no more than twelve (12) people and must consist of field users and stakeholders capable of making final decisions about product behavior and functionality. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) instance of Mobile Unit Law Configuration Session and the Mobile Unit Law Configuration Consultation. Customer Team Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Provide mobile SME to support Hexagon as needed; Provide a Dispatcher SME to give feedback on how Mobile Unit will affect dispatchers and to assist with various dispatching Activities; Participate fully and collaboratively in the Mobile Unit Law Configuration Session with the understanding that Mobile Unit client configuration decisions must be documented and agreed upon at the conclusion of these sessions; Configure Mobile Unit during the Mobile Unit Law Configuration Period; and Begin the Mobile Unit Law Configuration Document. Task Acceptance Criteria The Task is complete when Hexagon has conducted the Mobile Unit Law Configuration Session and the Mobile Unit Law Configuration Consultation. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 48 21. OnCall Dispatch | Mobile Unit Configuration Consulting Session – Fire Task Description Hexagon will conduct one (1) consulting session with the Customer lasting no more than three (3) Business Days as part of the Project (“Mobile Unit Fire Configuration Session”). During the Mobile Unit Fire Configuration Session, Hexagon will provide information regarding configuration options for Mobile Unit workflows as they pertain to the mobile environment. The Mobile Unit Fire Configuration Session will address: Sign on/Sign off Brief Overview of Application Screen Layout Navigation Buttons Alerts Toolbars Event Search Menus and Submenus Map Messaging Unit Board Event Board The included Dispatch Report Network requirements and ports to ensure the Mobile Unit client can communicate appropriately The Customer will need to make available one dispatcher familiar with OnCall Dispatch to perform dispatching and other related tasks as necessary during the Mobile Unit Fire Configuration Session. Following the Mobile Unit Fire Configuration Session, the Customer will configure Mobile Unit during the next ten (10) Business Days (“Mobile Unit Fire Configuration Period”). Hexagon will provide remote support for the Customers Mobile Unit Fire configuration efforts (“Mobile Unit Fire Configuration Consultation”) up to a maximum of two (2) Business Days. The Customer is responsible for configuring the Mobile Unit subsystem. Upon completion of this Task, the Customer will have one (1) mobile configuration of Mobile Unit for testing. Task Deliverables OnCall Dispatch | Mobile Unit Fire Configuration Session OnCall Dispatch | Mobile Unit Fire Configuration Consultation Task Prerequisites OnCall Dispatch Configuration Consulting 3 Task is complete. Task Assumptions Hexagon responsibilities will be executed on site at a Facility. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 49 Attendance by the Customer’s personnel will be limited to no more than twelve (12) people and must consist of field users and stakeholders capable of making final decisions about product behavior and functionality. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) instance of Mobile Unit Fire Configuration Session and Mobile Unit fire Configuration Consultation. Customer Team Participation and Responsibilities Customer shall: Provide a Facility; Provide a Project Workstation for each attendee; Provide mobile SME to support Hexagon as needed; Provide a Dispatcher SME to give feedback on how Mobile Unit will affect dispatchers and to assist with various dispatching Activities; Participate fully and collaboratively in the Mobile Unit Fire Configuration Session with the understanding that Mobile Unit client configuration decisions must be documented and agreed upon at the conclusion of these sessions; Configure Mobile Unit during the Mobile Unit Fire Configuration Period; and Begin the Mobile Unit Fire Configuration Document. Task Acceptance Criteria The Task is complete when Hexagon has conducted the Mobile Unit Fire Configuration Session and the Mobile Unit Fire Configuration Consultation. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 50 22. OnCall Dispatch | Mobile Responder Configuration – Law Task Description Hexagon will conduct one (1) remote session to consult on the configuration options outlined in the OnCall Mobile Configuration Options form lasting no more than one (1) Business Day as part of the Project. Hexagon will work with the Customer to complete this form during this session. After completing the overview of the configuration options, Hexagon will configure OnCall Mobile based on the completed OnCall Mobile Configuration Options form. Hexagon will provide up to one (1) Business Day of configuration time and deliver the completed configuration changes for OnCall Mobile for Law. Task Deliverables One (1) OnCall Dispatch | Mobile Responder Law Configuration Task Prerequisites COTS Interface Product Installation and Configuration Task is complete. Task Assumptions N/A Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) remote session of OnCall Dispatch | Mobile Responder Configuration for Law review lasting no more than one (1) Business Day Configure Mobile Responder based on the corresponding OnCall Mobile Configuration Options. Customer Team Participation and Responsibilities Customer shall: Provide mobile SME to Hexagon as needed; and Provide a Dispatcher SME to give feedback on how OnCall Dispatch | Mobile Responder will affect dispatchers and assist with various dispatching tasks. Task Acceptance Criteria The Task is complete when Hexagon has delivered the configured OnCall Dispatch | Mobile Responder for Law based on the corresponding OnCall Mobile Configuration Options form. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 51 23. OnCall Dispatch | Mobile Responder Configuration – Fire Task Description Hexagon will conduct one (1) remote session to consult on the configuration options outlined in the OnCall Mobile Configuration Options form lasting no more than one (1) Business Day as part of the Project. Hexagon will work with the Customer to complete this form during this session. After completing the overview of the configuration options, Hexagon will configure OnCall Mobile based on the completed OnCall Mobile Configuration Options form. Hexagon will provide up to one (1) Business Day of configuration time and deliver the completed configuration changes for OnCall Mobile for Fire. Task Deliverables One (1) OnCall Dispatch | Mobile Responder Fire Configuration Task Prerequisites COTS Interface Product Installation and Configuration Task Assumptions N/A Hexagon Team Participation and Responsibilities Hexagon shall: Conduct one (1) remote session of OnCall Dispatch | Mobile Responder Configuration for Fire review lasting no more than one (1) Business Day Configure Mobile Responder based on the corresponding OnCall Mobile Configuration Options. Customer Team Participation and Responsibilities Customer shall: Provide mobile SME to Hexagon as needed; and Provide a Dispatcher SME to give feedback on how OnCall Dispatch | Mobile Responder will affect dispatchers and assist with various dispatching tasks. Task Acceptance Criteria The Task is complete when Hexagon has delivered the configured OnCall Dispatch | Mobile Responder for Fire based on the corresponding OnCall Mobile Configuration Options form. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 52 24. OnCall Dispatch Archive Database Staging Task Description Hexagon resources will create an OnCall archive database using the CAD Database Utility and the Customer's staging hardware. Task Deliverables OnCall archive database on the Production staging system Task Prerequisites Virtual Server and OnCall Software Staging Task is Complete. The Customer has provided full database backup to Hexagon or given permission for Hexagon to take the backup on the Customer’s behalf. Code Freeze in place on Production Environment. Task Assumptions N/A Hexagon Team Participation and Responsibilities Hexagon shall: Process update to OnCall archive database schema using Customer’s staging hardware; and Use a copy of the ‘production’ database as an initial start point for the archive database. Customer Team Participation and Responsibilities Customer shall: Ensure Hexagon is provided with full backup of existing Production database to be used as start point for the OnCall archive database. Task Acceptance Criteria This Task is complete when the OnCall archive database has been delivered on the Production staging system. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 53 25. OnCall Analytics | Dispatch Configuration Task Description This Task is Hexagon-led and involves configuring OnCall Analytics | Dispatch with Customer’s site- specific parameters. OnCall Analytics is business intelligence software for reporting, analysis, and evidence-based decision making. It provides reporting and analysis capabilities, which are fully described within a document titled: “HxGN OnCall Analytics | Dispatch: Delivered Models and Reports,” which is available upon request. That document describes the types of reports and models available within OnCall Analytics, which may require additional configuration and work by the Customer. Only those reports corresponding to the type of reporting model and Software product included within the Project are available to the Customer. Required OnCall Analytics | Dispatch Advantage Software: HARDWARE DESCRIPTION/USE ONCALL ANALYTICS DISPATCH SOFTWARE COMPONENTS TO INSTALL Report Server The Report Server is a platform that business users will utilize to create, access, view, schedule and manage their reporting content. Microsoft Power BI Report Server OnCall Analytics | Dispatch (paginated reports and dashboards) Data Warehouse Server The Data Warehouse Server is used for the storage of the DW schemas, ETL related jobs and tables. In addition, this server may be used for the report server schemas. SQL Server Data Tools (SSDT) SQL Server Analysis Services (SSAS) SQL Server Integration Services (SSIS) Client Workstation The Client Workstation is used to access, manage and create content. Power BI Desktop Report Server (RS) Report Builder Task Deliverables Configuration of OnCall Analytics | Dispatch software and components for Customer testing and verification Task Prerequisites OnCall Dispatch Archive Database Staging Task is complete. OnCall Dispatch Configuration Consulting 3 Task is complete. Task Assumptions Hexagon will install the OnCall Analytics | Dispatch solution into the Production Environment. Other environments will be the responsibility of the Customer. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 54 Microsoft Power BI Report Server Note: If on-premise hosting of Power BI content is required, Customer must purchase SQL Server 2022 Enterprise Edition with Software Assurance (which includes the Power BI Report Server necessary for on-premise hosting of Power BI content) or may purchase Microsoft Power BI Report Server separately. Hexagon Team Participation and Responsibilities Hexagon shall: Configure the OnCall Analytics | Dispatch software components as outlined in the above table; Install the Microsoft Power BI desktop software (free download) and components as outlined in table above; and Confirm that the software installation and delivery has been completed, the data connections have been tested, and data is accessible in reports. Customer Team Participation and Responsibilities Customer shall: Provide remote access to Customer environment. If remote access is not possible, additional travel and administration time is required to complete the installation and a change order will be required; Provide system administrator to work with the Hexagon team during installation activities; Provide network administrator to work with the Hexagon team during installation activities; Provide database administrator to work with the Hexagon team during the installation activities, if needed; Install additional products not purchased under this Agreement, such as hardware and third-party backup software; and Provide SQL Server software and license keys to Hexagon for the database installation. Task Acceptance Criteria This Task is complete when Hexagon has configured and tested the OnCall Analytics | Dispatch software and data is accessible for reports and analytics in the Production Environment. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 55 26. Custom Interface Product Installation and Configuration Task Description During this Task, Hexagon will install, configure, and test the Custom Interfaces. Although the Customer is expected to participate in Hexagon’s internal testing of the Custom Interfaces, the Customer will formally test the Custom Interfaces’ functionality during Functional Testing. Task Deliverables Documentation of Custom Interfaces installation/testing Task Prerequisites Operation or availability of the external system or Third-Party Software. Custom Interface Development Task is complete. OnCall Dispatch Configuration Consulting 1 Task is complete. Hexagon Team Participation and Responsibilities Hexagon shall: Install Custom Interfaces; and Test Custom Interfaces in accordance with the approved ICDs. Customer Team Participation and Responsibilities Customer shall: Ensure SMEs are available to support Hexagon Activities as needed; Verify that physical connectivity has been achieved from Customer’s communication server to OnCall; Provide availability and confirm operation of external systems or third-party software; Provide the following information to Hexagon: IP address for remote databases Socket value for remote systems Operator IDs (ORIs), terminal mnemonics, etc., as needed by remote systems Ensure the system and network administrators are available to work closely with the Hexagon team for the duration of the Task; and Ensure third-party cooperation with Hexagon’s reasonable requests. Task Acceptance Criteria This Task is complete when each Custom Interface is installed and configured in accordance with the applicable ICD. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 56 27. Standard Interface Product Installation and Configuration Task Description During this Task, Hexagon will install and configure the Standard Interfaces. The Customer will formally test the interface functionality and reliability during Functional Testing. The following are regarded as “Standard Interfaces” as the term is defined in Attachment H of this SOW: RapidSOS OnCall Call-Taker Interface Fire Station Alerting OnCall Dispatch Interface PLT OnCall Dispatch Interface External Alarms OnCall Dispatch Interface CAD to CAD OnCall Dispatch Interface As part of this Task, Hexagon will provide consulting services to advise Eventide on how to use RestAPI to pull the data they require. Task Deliverables Documentation of Standard Interfaces installation Task Prerequisites Operation or availability of the external system or Third-Party Software OnCall Dispatch Configuration Consulting 3 Task is complete. Hexagon Team Participation and Responsibilities Hexagon shall: Install Standard Interfaces. Customer Team Participation and Responsibilities Ensure SMEs are available to support Hexagon Activities as needed; Verify that physical connectivity has been achieved from Customer’s communication server to OnCall; Provide availability and confirm operation of external systems or third-party software; Provide the following information to Hexagon: IP address for remote databases Socket value for remote systems Operator IDs (ORIs), terminal mnemonics, etc., as needed by remote systems Ensure the system and network administrators are available to work closely with the Hexagon team for the duration of the Task; and Ensure third-party cooperation with Hexagon’s reasonable requests. Task Acceptance Criteria This Task is complete when each Standard Interface is installed and configured. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 57 28. Sustaining Coordination Services for the CommSys ConnectCIC ASAP Interface Task Description During this Task, CommSys will provide consulting and sustaining coordination services for the ConnectCIC ASAP implementation. CommSys will provide the Customer with professional services for only the following aspects of the project (the “Sustaining Coordination Services”): Coordinate efforts with the agency’s executive stakeholders, Hexagon, state message switch/control point officials, The Monitoring Association (TMA), and the alarm monitoring companies; Coordinate with Hexagon for the installation of updates to Hexagon’s External Alarms OnCall Dispatch Interface in both a test environment and a production environment as applicable; These may be done at separate times A test plan as appropriate will be used Work with agency officials to identify connectivity issues to The State and The National Law Enforcement Teletype Service (NLETS) network via the state CJIS Message Switch or other transport method if available; Coordinate with new alarm companies that begin operating in production with the ASAP project and with agency officials through introductions, testing, and cutover to production activities; Execute testing to ensure that the end product continues to conform to the APCO/CSAA ANS 2.101.2-2014 standard; and Coordinate troubleshooting efforts with all appropriate agencies and staff as necessary when problems arise. Task Deliverables Sustaining Coordination Services Task Assumptions The testing and verification of the ASAP Interface will take place on site. Task Prerequisites Installation of External Alarms OnCall Dispatch Interface (reference Standard Interface Product Installation and Configuration task above) Installation of CommSys ConnectCIC CommSys ConnectCIC ASAP Option purchased Connectivity between CommSys ConnectCIC and the State CJIS Message Switch to receive NLETS transactions Hexagon Team Participation and Responsibilities Hexagon shall: Coordinate with CommSys for the installation of the External Alarms OnCall Dispatch Interface; Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 58 Coordinate with CommSys and “The Monitoring Association (TMA) for the installation of the ConnectCIC Product for APCO ASAP Alarm Product; and Coordinate with CommSys and TMA to arrange testing and validation of the interface. Customer Team Participation and Responsibilities Customer shall: Provide the appropriate team to complete the Sustaining Coordination Services. Task Acceptance Criteria This Task is considered complete when the ConnectCIC ASAP Interface has been installed and Sustaining Coordination Services have been performed. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 59 Testing Phase 29. Test Plan and Test Cases Development Task Description During this Task, the Customer will create a test plan (“CAD Test Plan”) with Test Cases for OnCall Dispatch. The CAD Test Plan and Test Cases are essential for the Customer to be able to validate and prove the functionality of the Dispatch Subsystem. Every Benchmark Criteria corresponding to OnCall Dispatch should have at least one Test Case; some Benchmark Criteria may have multiple associated Test Cases. The Customer will identify the Benchmark Criteria that correspond to the applicable Test Cases. A clear pass/fail criterion must be defined for each Test Case. The Test Plan and Test Cases will be agency-specific, and work-process driven with clearly documented Pass/Fail criteria. Only the elements of the Test Plan and Test Cases conforming with the Benchmark Criteria shall be used in evaluating and testing the Subsystem. The Test Plan is the set of Test Cases that will serve as the basis of testing the fully configured Subsystem, including interfaces. The Customer will not need a fully configured Subsystem to create the Test Plan and Test Cases. The Test Case creation should be accomplished using a workflow-based Test Case. Task Deliverables Customer’s CAD Test Plan and Test Cases Task Prerequisites OnCall Dispatch Fundamentals for Core Team Task is complete. Task Assumptions N/A Hexagon Team Participation and Responsibilities Hexagon shall: Consult with the Customer during the Test Plan and Test Cases creation Task to validate the Test Cases correspond to the Benchmark Criteria (applicable to Dispatch). Customer Team Participation and Responsibilities Customer shall: Create the CAD Test Plan and Test Cases consistent with the Benchmark Criteria; and Provide CAD Test Plan and Test Cases to Hexagon. Task Acceptance Criteria This Task is complete when the Customer has created the CAD Test Plan and Test Cases and Hexagon has validated the same in accordance with the Benchmark Criteria. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 60 30. Customer Functional Testing Task Description The Customer, with support from Hexagon, will test OnCall Dispatch’s conformance with the Benchmark Criteria. The Customer will conduct Functional Testing over the course of ten (10) Business Days (“Dispatch Testing Period”). During the Dispatch Testing Period, the Customer shall execute the CAD Test Plan and corresponding Test Cases. Except as expressly provided, no other testing or evaluation pertaining to OnCall Dispatch is contemplated in this Project. Customer will document and track the results of each Test Case as either pass or fail and may request Hexagon consultation as necessary during its testing Activity up to twenty-four (24) Business Hours. Within five (5) Business Days of the end of the CAD Testing Period (“CAD Reporting Period”), the Customer shall file any Blocker Defects and Permissive Defects encountered during Functional Testing – Dispatch through Hexagon’s Customer Resource Management (CRM) system. For any Blocker Defect identified, the Customer shall provide, at minimum, the following information: a description of the Defect and the steps used to reproduce it, the functionality tested when the Blocker Defect was encountered, the manner in which the functionality was tested, and the outcome when the functionality was tested. If the Blocker Defects are not filed within the CAD Reporting Period, it is presumed Functional Testing was completed without any Blocker Defect, and this Task is complete. Only Blocker Defects reported by the conclusion of the Reporting Period will be resolved as part of this Task. The existence of Permissive Defect(s) shall not preclude or be a condition of completion of any subsequent Tasks or implementation of a new Release. To the extent requested, Customer agrees to promptly respond to requests for additional information regarding the Blocker Defect requested by Hexagon. Upon diagnosing the Blocker Defect and validating the Defect encountered meets the attributes of a Blocker Defect, Hexagon resources shall proceed to resolve the Blocker Defect accordingly. If the investigation determines the reported Blocker Defect did not meet the attributes of a Blocker Defect then the reported Defect will be reclassified in accordance with the levels provided in the Master Terms Glossary. Alternatively, if the investigation shows the reported Blocker Defect was caused by Customer hardware, Network Infrastructure, or Third-Party Software not provided by Hexagon, or non-conformance with Attachments E and F, then Hexagon will provide such information to the Customer for the Customer to resolve and the Blocker Defect will be closed and regarded as complete. As part of its resolution efforts, Hexagon may at its discretion provide a procedural or programmatic work around, a configuration change, or provide an Update. Once the Blocker Defect(s) is addressed, Hexagon will report to Customer the Blocker Defect has been addressed and the Customer will have five (5) Business Days to execute its Test Plan (“CAD Resolution Testing Period”). After the Functional Testing, the System is intended to be in a near complete state such that all configurations and workflows have been built and tested in accordance with this Task. After this Testing Task is complete the Parties may mutually agree the System should be altered, modified, or otherwise changed. Hexagon shall condition its acceptance of additional modifications outside of addressing Blocker Defects on the execution of a change order to address additional Services, Project Schedule impacts, and fees. To the extent the parties mutually agree to such request and such request is made and agreed upon before the 8th day of the End User Training Period (as defined below), then such change can be addressed. The Customer acknowledges changes requested after this Task may affect the Project Schedule. Task Deliverables OnCall Dispatch Functional Testing Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 61 System Code Freeze Task Prerequisites Customer and Hexagon mutually confirm that OnCall Dispatch and Mobile Unit are ready for testing. Test Plan and Test Cases Development – OnCall Dispatch Task is complete. Hexagon Team Participation and Responsibilities Hexagon shall: Verify all applicable software, systems and ancillary systems, including the redundancy of Production system (if applicable), are ready for Functional Testing; Provide support during Functional Testing; Review Defects filed by the Customer; and Resolve Blocker Defects filed by the Customer. Customer Team Participation and Responsibilities Customer shall: Verify all applicable software, systems and ancillary systems, including the redundancy of Production system (if applicable), are ready for Functional Testing; Execute the CAD Test Plan; and Track and document results from executed Test Cases and file any Blocker Defects in the CRM system by the end of the CAD Reporting Period. Task Acceptance Criteria This Task is complete upon expiration of the CAD Testing Period and resolution of all Blocker Defects reported by the end of the CAD Reporting Period. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 62 Training Phase 31. Hexagon-Led Training Task Description During the Training phase, Hexagon resources will conduct Administrative and Train-the-Trainer sessions for Customer-designated personnel. The following formal training classes are included in the Project (“Hexagon Training Classes”): HxGN OnCall Dispatch System Administrator Training – Qty: 1 HxGN OnCall Dispatch Train-the-Trainer – Qty: 2 Note: Video Responder training is included with this training HxGN OnCall Dispatch | Mobile Unit Train-the-Trainer – Qty: 2 HxGN OnCall Dispatch | Mobile Responder Train-the-Trainer – Qty: 2 HxGN OnCall Analytics | Dispatch System Administrator Training – Qty: 1 HxGN OnCall Analytics | Dispatch User Training – Qty: 1 Xalt Integration Developer Training – Qty: 1 It is recommended that Customer develop its own training program, including, but not limited to: creating a training plan suitable for its needs, identifying a training cadre for each Subsystem, and leveraging the Hexagon training materials and Documentation to ensure its Users have acquired the necessary knowledge and are in a position to use OnCall Dispatch upon Cutover. The Customer is solely responsible for training its Users. The Customer shall complete its User Training no later than thirty (30) calendar days after Hexagon has completed the Hexagon Training Classes (“End User Training Period”). Task Deliverables Training course agendas Applicable COTS Documentation, in electronic format; for the Hexagon Training Classes Task Prerequisites Customer has identified and secured an appropriate training room and set up with the workstations, at least one (1) LCD projector, display screen or other appropriate surface to display a projected image, and white-board space or other ability to take notes and record questions. The Customer has installed and configured at least one (1) workstation per student attending the session. Customer Functional Testing Tasks for each Subsystem are complete. Task Assumptions The Customer will complete end user training within the End User Training Period. Both end-user training and train-the trainer training will be provided as specifically identified herein. Training will take place during normal Business Hours, which is typically from 8:00 am - 5:00 pm. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 63 Training documentation provided by Hexagon with this SOW will be standard COTS Documentation and help files and will not be customized to the Customer’s site-specific configuration. All Documentation will be provided in electronic format. Should printed copies be required, the Customer is responsible for providing them. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct Hexagon Training Classes. Customer Team Participation and Responsibilities Customer shall: Provide appropriate facilities and install/configure workstations as indicated in the Task Assumptions; Provide a Project Workstation for each attendee of the Hexagon Training Classes; Ensure appropriate personnel participate in the Hexagon Training Courses; and Complete end user training within the End User Training Period. Task Acceptance Criteria This Task is complete once Hexagon has delivered the Hexagon Training Classes to the Customer. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 64 32. Test and Training Environment Creation Task Description Following completion of all testing Tasks, Hexagon will create the Test and Training Environments using a snapshot of the Production Ready System. As part of this Task, Hexagon will test the Test and Training Environments to verify the Production Ready System has been properly loaded. For clarification, this testing is not intended to repeat or overlap with Customer Functional Testing Tasks. Task Deliverables Test and Training Environment installed Task Prerequisites Test and Training virtualized environment is available. The System is a Production Ready System. Hexagon Team Participation and Responsibilities Hexagon shall: Install and test the Hexagon System in the Test and Training Environments. Customer Team Participation and Responsibilities Customer shall: Provide IT support, as required; and Provide hardware, database software, operating system software, network, and physical site necessary for creation of Test Environment. Task Acceptance Criteria This Task is complete when the System has been installed and tested in the Test and Training Environments. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 65 Cutover Phase 33. Cutover Plan Task Description Hexagon and the Customer will jointly develop a Cutover Plan. The Cutover Plan will detail the steps necessary to cutover OnCall Dispatch. The Cutover Plan will assign tasks and responsibilities to both Hexagon and Customer personnel in the month prior to Cutover. The Cutover Plan covers topics including Customer staffing, movement of equipment into final locations, final database cleanout of test events, procedures to report issues, and planned sequence of events for the Cutover day. Hexagon will provide the initial draft of the Cutover Plan to the Customer for review. The Customer will review the draft and provide feedback to Hexagon within ten (10) Business Days, which will incorporate appropriate feedback into a final Cutover Plan. Task Deliverables Cutover Plan Hexagon Team Participation and Responsibilities Hexagon shall: Create a draft Cutover Plan (i.e., prepare a checklist of responsibilities and tasks to be completed during the Cutover Task prior to Cutover); Work with Customer personnel to refine the Cutover Plan; and Review and approve the final Cutover Plan. Customer Team Participation and Responsibilities Customer shall: Review and comment on the draft Cutover Plan within ten (10) Business Days of receipt; Work with Hexagon personnel to refine the Cutover Plan; and Review and approve the final Cutover Plan. Task Acceptance Criteria This Task is complete when the Customer has reviewed and approved the final Cutover Plan. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 66 34. System Readiness Review Task Description During this Task Hexagon technical resources, the Hexagon Project Manager, and the Customer team will meet and determine if the OnCall Subsystems are ready for Cutover. In addition, the System Readiness Review verifies that the following has occurred: A document titled, “Cutover Plan” has been developed and approved by both Hexagon and the Customer; Establishment and approval of a schedule for Cutover Activities; and Identification and scheduling of Hexagon and Customer resources required for Cutover Activities. Task Deliverables Readiness Review meeting minutes Discussion notes on the results from Hexagon’s final review of the system Task Prerequisites Cutover Plan Task is complete. Task Assumptions The Customer certifies it has trained all personnel who will be utilizing the system. Hexagon Team Participation and Responsibilities Hexagon shall: Conduct a conference call to discuss if the system is ready to perform Cutover; Provide system Cutover notification to appropriate internal and external interface stakeholders supplying systems integral to Cutover operations; Review and provide timely feedback/approval of Cutover Plan; and Work with Customer to determine suitable Cutover schedule. Customer Team Participation and Responsibilities Customer shall: Participate in the conference call; Notify internal and external interface stakeholders about pending Cutover; Review and provide timely feedback/approval of Cutover Plan; and Work with Hexagon to determine suitable Cutover schedule. Task Acceptance Criteria This Task is complete when the Readiness Review has been conducted. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 67 35. Cutover to Production Use Task Description Cutover reflects the culmination of all the Tasks in this SOW. It reflects the point at which the Customer first uses the System in a live environment for its intended purpose. The Parties shall execute the Cutover Plan, as practical, as part of Cutover. Beginning on Monday of the week of Cutover, Hexagon resources and the Project Manager will support the Customer’s Activities leading to Cutover, during Cutover, and post-Cutover. Except for the day of Cutover where the resource may be on site at alternate hours, the Hexagon resources (PM, CAD Implementer, and CAD Tech Lead) will be available Monday to Friday of the week of Cutover. Upon Cutover, the Customer’s System Administrator will assume primary responsibility of the management and administration of the System, and the Hexagon resources will provide support as needed by the Customer System Administrator. At times where the Hexagon resources are not otherwise available after the Project is complete, the Customer shall contact Hexagon’s HelpDesk in accordance with the Maintenance Terms within the Agreement who will coordinate with the Hexagon Project team on addressing the reported Defects. For Blocker Defects during the week of Cutover, Hexagon’s Project Team will respond to the reported Defect (including during non-Business Hours). Cutover also marks the commencement of the Warranty Period for the Project Software as described in Attachment K. Task Deliverables Cutover of Dispatch Task Prerequisites All prior Tasks are complete. The End User Training Period is complete. Task Assumptions The Parties have agreed Cutover can proceed. Cutover will take place on the day and time specified in the Cutover Plan. Hexagon Team Participation and Responsibilities Hexagon shall: Hexagon shall provide technical resource(s) to support Cutover during the week of Cutover. Customer Team Participation and Responsibilities Customer shall: Ensure availability of trained Users; Ensure availability of Core Team during Cutover Activities; Assume System Administration and management for the System upon Cutover; Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 68 Ensure availability of all third-party vendors impacted by the Cutover; Ensure availability of all IT disciplines necessary to immediately address issues as necessary; and Ensure availability of member(s) of the training cadre during all shifts. Task Acceptance Criteria This Task is complete upon Cutover of the Subsystems. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 69 36. Post-Cutover Support Task Description During this Task, Hexagon resources will provide Post-Cutover support to Customer. The “Post-Cutover Support Period” is the ten (10) Business Days beginning the Monday following Cutover. It is designed to provide the Customer with dedicated, quickly accessible support for questions and Defects encountered in the ten (10) Business Days following the Cutover to Production use of the new System. During this Task, Hexagon resources will be assigned Defects that are filed by the Customer against the new System. Hexagon resources will work to identify and address the Defects reported, understanding the Defects will be triaged based upon their severity during the Post Cutover Support Period. Defects remaining after the Post Cutover Support Period will be addressed by the Help Desk. Defects reported outside of Business Hours will be addressed in accordance with the maintenance provisions of the Agreement. The Post-Cutover Support Period is not a configuration period. Requests for new configurations that are not related to addressing a Defect will not be supported during this time frame. This is done to ensure the stability of the System delivered and that focus remains on Defects and to minimize the introduction of new opportunities for errors or problems. Task Deliverables Task Completion Form confirming that Post-Cutover Support has been provided in accordance with SOW Post-Cutover Support task description Task Prerequisites System Cutover to Production Use Task is complete. Task Assumptions Post-Cutover Support is provided Monday-Friday during normal Business Hours. Standard after- hours emergency support procedures, defined in the Cutover Plan, remain the same for the duration of this Task. Defects will be reported via Hexagon’s designated CRM tool. The Customer System Administrator remains the primary point of contact and initial troubleshooting point of contact for all issues during this Task. The Customer System Administrator maintains responsibility for core system administration tasks. Hexagon Team Participation and Responsibilities Hexagon shall: Provide ten (10) Business Days of Post-Cutover support in accordance with this SOW; and Address Defects within the Post Cutover Support Period. Customer Team Participation and Responsibilities Customer shall: Ensure Defects are recorded in Hexagon’s CRM tool in a timely manner and in accordance to the mutually agreed upon Project Schedule. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 70 Task Acceptance Criteria This Task is complete when the Post-Cutover Support Period has expired. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 71 Final Acceptance The System shall be accepted upon the earlier of: (i) the System has been in production use for thirty (30) calendar days and Hexagon has timely responded to Customer Defect Service Requests (requests other than for addressing a Defect are not included) in accordance with Attachment K (Warranty) or (ii) Customer’s use of the System in production for seventy-five (75) calendar days. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 72 Approval Signatures Signature by all parties listed below constitutes acceptance of and notice to proceed with this SOW, in accordance with this SOW and the GSA Contract. This SOW may be executed in one or more counterparts, each of which shall be deemed to be original, and all of which together shall constitute one and the same agreement. A signature delivered by facsimile shall be deemed to be an original signature and shall be effective upon receipt thereof by the other party. This SOW together with the GSA Contract constitutes the entire agreement between the Parties. This SOW may not be amended or modified unless done so in a writing signed by authorized representatives of both Parties. The pre-printed terms and conditions a purchase order or any other terms and conditions of a Customer purchase order shall be void and shall not constitute a change to this SOW or the GSA Contract. This document is approved by: AUTHORIZED HEXAGON SIGNATURE Name: Tiffany Taylor, North America Finance Director Signature: Date: AUTHORIZED CUSTOMER SIGNATURE Name: Title: Signature: Date: Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E 9/16/2024 Jamezetta Bedford Chair, BOCC 9/26/2024 Statement of Work 73 Attachment A – Pricing Summary Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Statement of Work 74 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description GSA Services OnCall Dispatch Project Services 1 N/A $1,204,917.29 $1,204,917.29 N/A N/A N/A Project services for CAD including Program Management, Implementation and Training. OnCall Software (GSA) HxGN OnCall Dispatch - Backup NL 1 IPS.P.IPS1136 $32,540.55 $32,540.55 IPS.M.IPS1136 $7,086.96 $7,086.96 Server product that provides support for maintaining one or more near real-time backups of an OnCall database server HxGN OnCall Dispatch - Advantage CC 11 IPS.P.IPS1122 $14,448.97 $158,938.67 IPS.M.IPS1122 $3,365.40 $37,019.40 Concurrent user licenses for OnCall Dispatch software HxGN OnCall Dispatch - Advantage CC - Training License 7 IPS.P.IPS1122TRN $7,225.39 $50,577.73 IPS.M.IPS1122TRN $3,365.40 $23,557.80 Concurrent training user licenses for OnCall Dispatch software HxGN OnCall Dispatch - Viewer CC 25 IPS.P.IPS1166 $2,676.88 $66,922.00 IPS.M.IPS1166 $620.28 $15,507.00 Concurrent user licenses for the Viewer software; provides access to live dispatch information and basic capabilities to users outside the control room Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 75 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description HxGN OnCall Dispatch - Resource Management 11 IPS.P.IPS1132 $3,747.81 $41,225.91 IPS.M.IPS1132 $884.40 $9,728.40 User licenses for Resource Management add-on pack; provides support for advanced unit recommendation such as balance of alarm and staging functionality. HxGN OnCall Dispatch - Resource Management - TRN License 7 IPS.P.IPS1132TRN $1,875.26 $13,126.82 IPS.M.IPS1132TRN $884.40 $6,190.80 Training user licenses for the Resource Management add-on pack HxGN OnCall Dispatch - Advanced Mapping 11 IPS.P.IPS1133 $2,676.88 $29,445.68 IPS.M.IPS1133 $643.20 $7,075.20 User licenses for Advanced Mapping add-on pack; provides support for advanced mapping capabilities such as tracking an officer while out of the vehicle with GPS- enabled devices, such as radios HxGN OnCall Dispatch - ProQA Interface 11 IPS.P.IPS1189 $552.24 $6,074.64 IPS.M.IPS1189 $149.28 $1,642.08 User licenses for the ProQA Interface add- on. Refer to Attachment H - Interface Descriptions. HxGN OnCall Dispatch - Mobile Unit 100 IPS.P.IPS1202 $1,339.35 $133,935.00 IPS.M.IPS1202 $333.12 $33,312.00 Concurrent user licenses for Mobile Unit software; MDT dispatch software for Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 76 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description field users (police officer, firefighter, etc.) HxGN OnCall Dispatch - Mobile Responder Client CC 190 IPS.P.IPS3209 $1,019.24 $193,655.60 IPS.M.IPS3209 $264.00 $50,160.00 User licenses for Mobile Responder software; smartphone/tablet app that provides field personnel access to streamlined response and law enforcement workflows HxGN OnCall Dispatch - RestAPI NL 2 IPS.P.IPS1195 $32,105.29 $64,210.58 IPS1195 $7,488.96 $14,977.92 Provides third parties direct interaction with OnCall via an industry- standard RestAPI HxGN OnCall Dispatch - RestAPI NL - Training 1 IPS.P.IPS1195TRN $16,054.01 $16,054.01 IPS.M.IPS1195TRN $7,488.96 $7,488.96 Training license for RestAPI Xalt - Integration Runtime Engine NL 1 IPS.P.IPS3042 $24,559.80 $24,559.80 IPS.M.IPS3042 $6,248.52 $6,248.52 OnCall Dispatch license for Xalt, a lightweight, general purpose integration platform Xalt - Integration Developer Engine NL 1 IPS.P.IPS3042DEV $18,418.94 $18,418.94 IPS.M.IPS3042DEV $4,686.36 $4,686.36 License for Xalt Developer; allows the customer to build their own interfaces Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 77 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description HxGN OnCall Dispatch - Informer 1 IPS.P.IPS1196 $14,769.97 $14,769.97 IPS.M.IPS1196 $3,457.32 $3,457.32 Interface license for Informer; provides a set of forms designed to run queries on local, provincial, regional, and/or national crime information databases. Refer to Attachment H - Interface Descriptions. HxGN OnCall Dispatch - CAD Link Interface 1 IPS.P.IPS1206 $6,636.88 $6,636.88 IPS.M.IPS1206 $1,550.64 $1,550.64 Interface license for CAD Link; facilitates the automatic periodic transfer of event and unit information from OnCall Dispatch to external systems such as Emergency Reporting and ESO. Refer to Attachment H - Interface Descriptions. HxGN OnCall Dispatch - Fire Station Printing 1 IPS.P.IPS1198 $6,636.88 $6,636.88 IPS.M.IPS1198 $1,550.64 $1,550.64 Provides support for remote fire station turnout by printing run cards when units from a station are dispatched. The product can also be configured to print incident summary reports when units from a station are cleared from an incident. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 78 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description HxGN OnCall Dispatch - Fire Link Interface 2 IPS.P.IPS1205 $6,636.88 $13,273.76 IPS.M.IPS1205 $1,550.64 $3,101.28 Interface license for Fire Link; facilitates the automatic periodic transfer of event and unit information from OnCall Dispatch generated during a Call for Service to external Fire Records Management Systems (FRMS). Refer to Attachment H - Interface Descriptions. HxGN OnCall Dispatch - Tracker CC 250 IPS.P.IPS1186 $55.31 $13,827.50 IPS.M.IPS1186 $34.44 $8,610.00 User licenses for Tracker; accepts incoming Global Positioning Satellite (GPS) data directly from a GPS device (in this case, radios), periodically updating locations in OnCall maps HxGN OnCall Dispatch - Notifications 1 IPS.P.IPS1199 $13,378.04 $13,378.04 IPS.M.IPS1199 $3,135.72 $3,135.72 Interface license for Notifications; provides connectivity between the dispatching environment and multiple internal and external communication endpoints such as Alpha paging. Refer to Attachment H - Interface Descriptions. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 79 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description RapidSOS OnCall Call- Taker Interface 1 IPS.P.PSA1106 $5,195.97 $5,195.97 IPS.M.PSA1106 $1,217.52 $1,217.52 Interface license for RapidSOS; receives location accuracy information from the caller’s device and offers updates on demand. Refer to Attachment H - Interface Descriptions. PLT Radio OnCall Dispatch Interface 1 IPS.P.PSA1105 $5,195.97 $5,195.97 IPS.M.PSA1105 $1,217.52 $1,217.52 Interface license for PLT Radio OnCall Dispatch Interface; supports receiving GPS data from P25 radio systems. Refer to Attachment H - Interface Descriptions. External Alarms OnCall Dispatch Interface 1 IPS.P.PSA1101 $5,195.97 $5,195.97 IPS.M.PSA1101 $1,217.52 $1,217.52 Interface license for External Alarms OnCall Dispatch Interface; allows OnCall to interface with the APCO ASAP Standard. Refer to Attachment H - Interface Descriptions. HxGN OnCall Analytics - Dispatch Advantage NL 4 Core 1 IPS.P.IPS2305 $53,508.51 $53,508.51 IPS.M.IPS2305 $12,462.48 $12,462.48 License for OnCall Analytics – Dispatch Advantage; provides complete reporting and analysis capabilities for HxGN OnCall Dispatch data Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 80 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description Dynamo Curriculum HxGN OnCall Dispatch Admin - on prem 12 IPS.P.HXT0001 $31.74 $4,570.56 NA NA NA E-learning curriculum introduces the HxGN OnCall Dispatch administrator to necessary tasks to administer the system, plus delivers lab exercises for hands-on training Dynamo Curriculum HxGN OnCall Analytics Admin - on prem 6 IPS.P.HXT0005 $31.74 $2,285.28 NA NA NA E-learning curriculum provides a series of self-paced e-learning courses that covers the administration of the HxGN OnCall Analytics application OnCall Software (Open Market) HxGN OnCall Dispatch - ProQA Interface - Training 7 IPS1189TRN $338.10 $2,366.70 IPS1189TRN $176.40 $1,234.80 Training user licenses for the ProQA Interface add-on HxGN OnCall Dispatch - Video Responder Advantage 11 IPS1234 1,896.30 $20,859.30 IPS1234 $441.00 $4,851.00 Advantage product allows users to integrate video into the public safety workflow by viewing live video, making it easier to spot potential problems and decide how to respond efficiently and effectively. plus more advanced video management controls Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 81 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description allowing for OnCall Dispatch users to access archive video from VMS’s and control camera movement from within OnCall Dispatch. HxGN OnCall Dispatch - Mobile Unit - Training 7 IPS1202TRN $814.80 $5,703.60 IPS1202TRN $390.60 $2,734.20 Concurrent training user licenses for Mobile Unit software HxGN OnCall Mobile Server 3 IPS3212 - - IPS3212 - - Server component required for Mobile Responder software Video Streamer VMS 2 IPS1224 $13,201.65 $26,403.30 IPS1224 $2,935.80 $5,871.60 Video Streamer VMS (HVS) and associated client component allows Web applications to display video originating from Video Management Systems (VMSs) in an RTSP format encoded as H.264. A License for Video Streamer VMS allows a customer to connect to one VMS. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 82 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description Avigilon VMS Interface 1 IPS1239 $6,317.85 $6,317.85 IPS1239 $1,411.20 $1,411.20 Avigilon VMS Interface provides a method to connect Avigilon Video Management System to Video Streamer HxGN OnCall Dispatch - Call-Taker Interface 2 IPS1227 $3,790.50 7,581.00 IPS1227 $856.80 $1,713.60 Interface license for Call-Taker Interface; enables Call-Taker to connect to various external systems such as RapidSOS, TDD, and text-to-911. Fire Station Alerting OnCall Dispatch Interface 1 PSA1102 $6,317.85 $6,317.85 PSA1102 $1,411.20 $1,411.20 Interface license for Fire Station Alerting; provides support for third-party Fire Station Alerting Solutions. The Interface sends unit and event information to the Fire Station Alerting solution to trigger station alarms, unit dispatch, and other services provided by the vendor as defined by their API. Refer to Attachment H - Interface Descriptions. Custom Interfaces (Open Market) Query Interface to Legacy OneSolution CAD 1 N/A $24,698.38 $24,698.38 N/A $3,139.92 $3,139.92 Hexagon will develop a query interface to the Customer’s legacy OneSolution CAD via the Informer interface. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 83 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description Refer to Attachment H - Interface Descriptions. CAD Query Interface to OneSolution RMS 1 N/A $23,638.78 $23,638.78 N/A $3,527.88 $3,527.88 Hexagon will develop a query interface to the Customer’s OneSolution RMS via the informer interface. Refer to Attachment H - Interface Descriptions. CAD Interface to Text to 911 1 N/A $23,638.78 $23,638.78 N/A $3,527.88 $3,527.88 Hexagon will develop a custom interface to meet this requirement. Refer to Attachment H - Interface Descriptions. CAD Interface to Eventide Recording 1 N/A $2,999.64 $2,999.64 N/A - - Hexagon will provide consulting services to advise Eventide on how to use RestAPI to pull the data they require. Other (Open Market) Kemp Load Balancers 3 N/A $11,231.50 $33,694.50 N/A - - Load balancers required for OnCall web servers in order to provide High Availability. CommSys ConnectCIC 2 N/A $17,125.00 $17,125.00 N/A $3,281.28 $3,281.28 Third-party middleware product for the interface to NCIC for state and local transactions. Refer to Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 84 Product Qty Product Part# Product Unit Price Product Extended Price Maintenance Part# Maintenance Unit Price Maintenance Extended Price Product Description Task 16 above for more detail. CommSys ASAP interface 2 N/A $10,125.00 $10,125.00 N/A $2,031.24 $2,031.24 Third-party software for Automated Secure Alarm Protocol (ASAP) integration. CommSys ASAP Consulting Services 1 N/A $21,875.00 $21,875.00 N/A - - Consulting services for the Customer to coordinate deployment with the Monitoring Association directly. Refer to Task 28 above for more detail. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Statement of Work 85 Pricing Summary Table HxGN OnCall Dispatch Total Software: HxGN OnCall Dispatch Software (GSA): $994,161.22 HxGN OnCall Dispatch Software (Open Market): $158,369.10 Custom Interfaces: HxGN OnCall Dispatch Interface Customizations (Open Market): $74,975.58 Services: HxGN OnCall Dispatch Project Services (GSA): $1,204,917.29 Estimated Total One-Time Software and Services $2,432,423.19 Year 1 Maintenance (Extended Warranty) (GSA) $262,240.35 Year 1 Maintenance (Extended Warranty) (Open Market) $34,735.80 Estimated Total One-Time Software and Services Including Maintenance $2,729,399.34 Pricing Assumptions This offer is valid until December 1, 2024. Wherever applicable, software and services have been priced using the GSA Contract. GSA and Open Market items have been identified on the included detailed pricing summary. Project Services included in this response are inclusive of project management, implementation, Interfaces, training services, and related travel. Static CAD data conversion is included in the base price of the system as part of the project implementation and includes such data as Agency ID, Station Definitions, Personnel Definitions, Unit Types, Unit Definitions, Vehicle Definitions, Event Type Codes, Out of Service Codes, Disposition Codes, Special Address, etc. Historical Data Conversion is not included. OnCall Dispatch does not use a proprietary map. Hexagon assumes the County will provide an OnCall-supported mapping source as described in the OnCall system requirements. "OnCall client licenses are browser based and include the map and system administration functions. Hexagon has provided pricing for CAD software licensing to meet the client count requirements provided by the customer. Please see the included Bill of Materials for software products and quantities included in this proposal. After further discussions with the customer, software license counts may be adjusted. The pricing provided assumes production, test, training, and backup environments. Backup (BCK) and Test (TST) software licenses are provided as needed for the proposed solution based on the purchase of the related production license. These licenses are provided at no additional cost. Year 1 Maintenance (Warranty) commences at Subsystem Cutover. Third party software included in the base system includes accompanying third party maintenance. Some third parties begin software maintenance at cutover and others upon shipment. All have been included in the pricing appropriately based on an expected project timeline. If the project Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 86 timeline is exceeded, additional third-party maintenance cost may be incurred which the Customer would be responsible for payment. To the extent Hexagon’s ability to resell support for third party products ends during the term of the Agreement, then Hexagon shall be relieved of the obligation to provide such support and the annual maintenance fee will be adjusted to account the removal of that software item. The Dynamo Curriculum/E-Learning Licenses (quantity of 18) included in this pricing are for a 12- month duration to begin once the licenses are provided as part of Task 1. The third-party Kemp Load Balancer products procured by Hexagon are provided with a pre-paid 5-year pass-thru-warranty from the original manufacturer. The warranty commences on the date the product is shipped to the customer. Base price includes Bi-Annual HxGN Live attendance fee for one (1) attendee for 2025 HxGN Live. Attendance fees do not include travel and lodging costs. Sales tax is not included in this quote. Final sales tax billed will reflect the applicable tax rates at time of sale as required by law. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 87 Attachment B – Payment Schedule Milestone Payment Schedule MS (#) Milestone Deliverable MS (%) MS ($) 1 Upon Completion of Task #1: Project Kickoff Meeting 15% $409,409.90 2 Upon Completion of Task #9: Virtual Server and OnCall Software Staging 15% $409,409.90 3 Upon Completion of Task #11: OnCall Dispatch System Build 1 15% $409,409.90 4 Upon Completion of Task #13: OnCall Dispatch System Build 2 12.5% $341,174.92 5 Upon Completion of Task #18: OnCall Dispatch Configuration Consulting 2 12.5% $341,174.92 6 Upon Completion of Task #20: OnCall Dispatch | Mobile Unit Configuration Consulting Session - Law 10% $272,939.93 7 Upon Completion of Task #30: Customer Functional Testing - OnCall Dispatch 10% $272,939.93 8 Upon Completion of Task #35: Cutover to Production use 5% $136,469.97 11 Upon Final Acceptance 5% $136,469.97 Total 100% $2,729,399.34 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 88 Attachment C – Initial Project Schedule TASK NAME DURATION BUSINESS DAYS SINCE START On-Prem OnCall Dispatch Project Schedule 400 days 0 days Planning Phase 45.38 days 0 days Project Kickoff Meeting 3.5 days 20 days COTS Interface Questionnaire Completion 5.5 days 27.25 days OnCall Dispatch & Mobile Unit Launch 6.5 days 28.5 days OnCall Dispatch GIS Requirements Review 1.13 days 28.5 days Custom Interface Development 6.75 days 38.63 days Load Balancer Equipment Ordering 0.25 days 23.5 days Staging Phase 108.88 days 23.75 days Physical Infrastructure Installation 1 day 35.25 days Virtual Server and OnCall Software Staging 11.39 days 41.25 days OnCall Dispatch GIS Consulting 21.13 days 52.64 days OnCall Dispatch System Build 1 18.25 days 73.77 days OnCall Dispatch Deployment and Response Planning Workshop 14.98 days 97.02 days OnCall Dispatch System Build 2 15 days 117 days Configuration Phase 324.25 days 132.63 days OnCall Dispatch Fundamentals for Core Team 6 days 137 days COTS Interface Product Installation and Configuration 137.63 days 132 days CommSys ConnectCIC Installation 5.25 days 137.63 days OnCall Dispatch Configuration Consulting 1 18.25 days 148 days OnCall Dispatch Configuration Consulting 2 15.75 days 171.25 days OnCall Dispatch Configuration Consulting 3 14.25 days 196.75 days OnCall Dispatch | Mobile Unit Configuration Consulting Session - Law 15 days 216 days OnCall Dispatch | Mobile Unit Configuration Consulting Session - Fire 18 days 227 days OnCall Dispatch | Mobile Responder Configuration - Law 2 days 221 days OnCall Dispatch | Mobile Responder Configuration - Fire 2 days 235 days OnCall Dispatch Archive Database Staging 0.25 days 317 days OnCall Analytics - Dispatch Configuration 7 days 317.25 days Custom Interface Product Installation and Configuration 7 days 166.25 days Standard Interface Product Installation and Configuration 1 day 211 days Testing Phase 174 days 143 days Test Plan and Test Cases Development - OnCall Dispatch 0 days 143 days Customer Functional Testing - OnCall Dispatch 45 days 271.75 days Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 89 Training Phase 56.5 days 317 days Hexagon-Led Training 35.5 days 317 days HxGN OnCall Dispatch System Administrator Training 8 days 317 days HxGN OnCall Dispatch | Train the Trainer Course 1 11 days 325 days HxGN OnCall Dispatch | Train the Trainer Course 2 10 days 336 days OnCall Dispatch | Mobile Unit Train-the-Trainer Course 1 10 days 317 days OnCall Dispatch | Mobile Unit Train-the-Trainer Course 2 8 days 327 days OnCall Dispatch | Mobile Responder Train-the-Trainer Course 1 2 days 331 days OnCall Dispatch | Mobile Responder Train-the-Trainer Course 2 2 days 333 days OnCall Analytics | Admin and User Training 8.75 days 317.25 days Xalt Developer Training 6 days 346 days OnCall Citizen Reporting Train-the-Trainer (TTT) 5 days 346 days Customer-Led End User Training (30 calendar days) 21 days 352.5 days Test and Training Environment Creation 9.75 days 317 days Cutover Phase 395.38 days 2 days Cutover Plan 11.63 days 373.5 days System Readiness Review 1 day 385.13 days Cutover to Production Use 383.25 days 2 days Post Cutover Support Week 1 5 days 385.25 days Post Cutover Support Week 2 5 days 390.25 days Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 90 Attachment D – Training Curriculum HxGN OnCall Dispatch | Advantage System Administrator Training (Qty: 1) The HxGN OnCall Dispatch | Advantage System Administrator course is a four-day, hands-on training class on how to configure and manage the OnCall system. During this course, the students will learn how to access the OnCall database and use available tools to administer and configure the system. MAJOR TOPICS Understanding the Environment Map Legend Management UI Editor Localized Strings Layout Manager Notification Configuration Custom Fields Parameter Management Deployment Configuration Response Plans Configuration Role Management Type Codes Management Agency Management Geographic Resources Change Management PREREQUISITES Customer Environment fully staged and available HxGN OnCall Dispatch | Advantage fully licensed, staged, and available Credentials available Hexagon user account provisioned with local administrator rights on all appropriate servers and workstations TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for administering and supporting the system Duration Four (4) Business Days Student Capacity Six (6), with a maximum of one (1) student per workstation Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 91 HxGN OnCall Dispatch | Advantage Train-the-Trainer (Qty: 2) HxGN OnCall Dispatch | Advantage Train-the-Trainer is a four (4)-day comprehensive course to familiarize communications personnel with the use of OnCall. Students will learn all of the essential functions of OnCall including navigating the application, entering and updating events, performing inquiries, handling units including updates and status changes, and communicating with other users. An introduction to the use of interfaces to such things as NCIC, state crime databases, and mobile units is also presented, if the interfaces are available. Students completing the course should have a good working knowledge of using HxGN OnCall Dispatch | Advantage. This course also includes three (3) additional days of consulting to guide the Customer in developing its training plan and materials for end users. MAJOR TOPICS Events – Creation, Updates, and Status Changes Mapping – Commands, Controls, and Views Units – Status Changes and Properties Updates Inquiries – Events, Units, and Employees Messaging – Send, Receive, and Attachments Using training guidelines and techniques for HxGN OnCall Dispatch | Advantage PREREQUISITES Customer Environment fully staged and available HxGN OnCall Dispatch | Advantage fully licensed, staged, and available Credentials available Hexagon user account provisioned with local administrator rights on all appropriate servers and workstations TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for training call-taking and dispatching staff Duration Four (4) Business Days Student Capacity Twelve (12), with a maximum of one (1) student per workstation Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 92 HxGN OnCall Dispatch | Mobile Unit Train-the-Trainer (Qty: 2) COURSE OVERVIEW HxGN OnCall Dispatch | Mobile Unit Train-the-Trainer is a two (2)-day comprehensive course to familiarize trainers with the operation and use of the HxGN OnCall Dispatch | Mobile Unit software. Trainers will learn all of the essential functions of HxGN OnCall Dispatch | Mobile Unit including navigating the application, creating, receiving and updating events, utilizing the map, performing inquiries, handling units including updates and status changes, and communicating with other users. Multiple agency-specific operations are also covered, including Fire, Law Enforcement and EMS related updates. Trainers completing the course should have a good working knowledge of HxGN OnCall Dispatch | Mobile Unit. This course also includes four (4) additional days of consulting to guide the Customer in developing its training plan and materials for end users. MAJOR TOPICS Create, receive and update active events Update active unit status and properties Submitting inquires for events and units Submitting and receiving messages Create and receive HxGN OnCall Dispatch | Informer queries from HxGN OnCall Dispatch | Mobile Unit Using training guidelines and techniques for HxGN OnCall Dispatch | Mobile Unit PREREQUISITES Customer mobile hardware fully staged and available HxGN OnCall Dispatch | Advantage and HxGN OnCall Dispatch | Mobile Unit fully licensed, staged, and available Credentials available Hexagon user account provisioned with local administrator rights on all servers and workstations Customer Data collection spreadsheets completed HxGN OnCall Dispatch | Advantage and HxGN OnCall Dispatch | Mobile Unit fully staged and available on the trainer’s workstation COURSE DETAILS Method Conducted on site by Hexagon Personnel Target Audience Personnel responsible for training the field personnel that respond to CAD events (Law, Fire, EMS) Duration Two (2) Business Days Student Capacity Twelve (12), with a maximum of one (1) student per workstation Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 93 HxGN OnCall Dispatch | Mobile Responder Train-the-Trainer (Qty: 2) Mobile Responder training is a Train-the-Trainer course designed to train Agency trainers in the use of the Mobile Responder product. MAJOR TOPICS Using Mobile Responder on Smartphone or tablet Changing unit status Submitting inquiries Sending and receiving messages Updating unit properties Updating events Informer queries PREREQUISITES Responsibility for mobile computing operations Assignment of at least one person who has been through OnCall Dispatch training to perform necessary dispatching and other CAD functions Availability of customer specific Mobile Responder configuration Availability of test or training Mobile Responder smartphone or tablet for use in class TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Designed for Mobile Responder Trainers Duration One (1) day, but can be changed depending on customer needs Student Capacity 12 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 94 HxGN OnCall Analytics | Dispatch User Training (Qty: 1) COURSE OVERVIEW HxGN OnCall Analytics | Dispatch offers the ability to perform reporting and analysis from a data warehouse containing data from databases, as well as provide capabilities for the user to view and modify reports and conduct ad-hoc queries from the data warehouse. This course is designed to familiarize the end user with HxGN OnCall Analytics | Dispatch Advantage. It will provide instruction on accessing, viewing, and creating reports from the OnCall Analytics Report portal. Additionally, training will be provided for the creation and modification of Power BI Reports using the Power BI Desktop tool. TARGET AUDIENCE Personnel responsible for reporting and analysis (Report Builders, Report Consumers, and System Admins) MAJOR TOPICS Power BI Report Server Portal Introduction Overview and Navigation Managing Report Server Content Subscriptions Delivered Analytical/Operational Report Overview Power BI Desktop Introduction Power BI Desktop Navigation Get Data Create Visualizations Filtering Visualizations Formatting Visualizations Pages – Size and Alignment Interacting and Sharing PREREQUISITES Familiarity with Windows-based applications Familiarity with agency workflows COURSE DETAILS Course Duration Two (2) days Course Type Conducted on site by Hexagon Personnel Student Capacity Ten (10) Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 95 HxGN OnCall Analytics | Dispatch System Administrator Training (Qty: 1) COURSE OVERVIEW This System Administrator Training course is designed for System Administrators, to provide instructions on the setup, site-specific configurations, and administrative tasks needed to maintain the HxGN OnCall Analytics | Dispatch Advantage. TARGET AUDIENCE System Administrators MAJOR TOPICS Introduction Installation and Deployment Review of the installation document Security Overview of SSIS (ETL) Site Customization Updates and Patch Delivery PREREQUISITES Familiarity with Microsoft Windows-based applications, administrative tasks, and agency workflows Familiarity with CAD configuration COURSE DETAILS Course Duration One (1) Day Course Type Conducted on site by Hexagon Personnel Student Capacity Four (4) Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 96 Xalt Developer Training (Qty: 1) This Xalt training course is designed for customers who have purchased an Xalt Developer license who have an interest in configuring their own Xalt Systems (interfaces). The Training class will be comprised of general Xalt training and API specific training. Students will receive both classroom training and hands-on experience enabling them to build and manage interfaces using Xalt and the CAD API. Upon successful completion, trainees will be able to take the core concepts/fundamentals and be able to configure simple-to-moderate interfaces in Xalt. With the foundational knowledge provided, trainees will be able to continue to use Xalt and build more complex interfaces over time, as that is the primary way to become a truly proficient user. Please note the stated prerequisites and student capacity, as strict adherence is essential to the successful completion of this course. MAJOR TOPICS General Xalt Knowledge Developing and deploying Xalt Systems Understanding the Data Structures Business Rules Implementation Linking Systems together via Publish/Subscribe and Receive/Inject Generating / Consuming XML Advanced Knowledge Topics (topics will be customized to address customer interface needs) API Knowledge Understanding the specific API functionality available Using Xalt to communicate to the API Subscribing to Topics Subscribing to logs PREREQUISITES Trainees will need a laptop or computer with the .NET 4.0 Framework installed. In addition, strong adherence to the following prerequisites is mandatory: Responsibility for the administration, support, and maintenance of Xalt and the systems/interfaces built within the application. Technical understanding of databases, XML, XSLT, XSD, and network communications. Working knowledge of Windows. This includes major networking components, including clients, servers, local area networks, network ports, and protocols. TRAINING DETAILS Method Conducted on site by Hexagon Personnel Target Audience Xalt User/Implementer Duration Four (4) days Student Capacity 4-8, with a maximum of 1 student per workstation Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 97 Attachment E – OnCall Dispatch Specifications [following this page] Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite System Specifications Release date: August 2023 Release version: 10.00.2303.01 Release type: On-premises and cloud Released by: Hexagon Global Technology Center Release method: Hexagon Global Software Delivery Process Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 2 Copyright © 2019-2023 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved. Warning: The product made the subject of this documentation, including the computer program, icons, graphical symbols, file formats, audio-visual displays and documentation (including this documentation) (collectively, the “Subject Product”) may be used only as permitted under the applicable software license agreement, and subject to all limitations and terms applicable to use of the Subject Product therein. The Subject Product contains confidential and proprietary information of Intergraph Corporation, a member of the Hexagon Group of companies (“Hexagon”), its affiliates, and/or third parties. As such, the Subject Product is protected by patent, trademark, copyright and/or trade secret law and may not be transferred, assigned, provided, or otherwise made available to any third party in violation of applicable terms and conditions cited further below. Terms of Use By installing, copying, downloading, accessing, viewing, or otherwise using the Subject Product, you agree to be bound by the terms of the EULA found here (https://www.hexagonsafetyinfrastructure.com/-/media/Legal/Hexagon/SI/Licenses/EULA_SA_SIG-Eng_062021.pdf). Disclaimers Hexagon and its suppliers believe the information in this publication is accurate as of its publication date. Hexagon is not responsible for any error that may appear in this document. The information and the software discussed in this document are subject to change without notice. Language Translation Disclaimer: The official version of the documentation is in English. Any translation of this document into a language other than English is not an official version and has been provided for convenience only. Some portions of a translation may have been created using machine translation. Any translation is provided "as is.” Any discrepancies or differences occurring in a translation versus the official English version are not binding and have no legal effect for compliance or enforcement purpos es. Hexagon disclaims any and all warranties, whether express or implied, as to the accuracy of any translation. Reasonable efforts have been made to provide an accurate translation; however, no translation, whether automated or provided by human translators is perfect. If any questions arise related to the accuracy of the information contained in a translated version of documentation, please refer to its official English version. Additionally, some text, graphics, PDF documents, and/or other accompanying material may not have been translated. Links to Third-Party Websites This document may provide links to third-party websites for your convenience and information. Third-party websites will be governed by their own terms and conditions. Hexagon does not endorse companies or products to which it links. Third-party websites are owned and operated by independent parties over which Hexagon has no control. Hexagon shall not have any liability resulting from your use of the third-party website. Any link you make to or from the third-party website will be at your own risk and any information you share with the third-party website will be subject to the terms of the third-party website, including those relating to confidentiality, data privacy, and security. Hexagon provides access to Hexagon international data and, therefore, may contain references or cross references to Hexagon products, programs and services that are not announced in your country. These references do not imply that Hexagon intends to announce such products, programs or services in your country. Trademarks "Hexagon,” “Hexagon Safety, Infrastructure & Geospatial,” “Intergraph,” the Hexagon logo, and the Intergraph logo are registe red trademarks of Hexagon AB or its subsidiaries. Other brands and product names are trademarks of their respective owners. Revisions Hexagon reserves the right to revise these terms at any time. You are responsible for regularly reviewing these terms. Your continued use of this document after the effective date of such changes constitutes your acceptance of and agreement to su ch changes. Contact Us Contact us https://hexagon.com/company/contact-us with any questions regarding these terms. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 3 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 4 Contents General Notes ........................................................................................................................... 5 Database Storage Requirements............................................................................................. 6 HxGN OnCall Dispatch Specifications .................................................................................... 7 Browser Requirements ......................................................................................................... 7 HxGN OnCall Dispatch Servers ............................................................................................ 7 Database Servers ........................................................................................................... 7 HxGN OnCall Dispatch Archive Server ................................................................................. 8 HxGN OnCall Dispatch Client Workstations .......................................................................... 9 Application Servers ....................................................................................................... 10 HxGN OnCall Dispatch Operational Reports Application Server ......................................... 11 HxGN OnCall Dispatch Specifications for Interface and Communication Servers .................................................................................................................................... 12 HxGN OnCall Dispatch Interface and Integration Communication Servers ......................... 12 RabbitMQ Servers .............................................................................................................. 13 HxGN OnCall Dispatch | Backup, Test, and Training Servers ............................................. 14 Off Site Backup HxGN OnCall Dispatch Servers ........................................................... 14 Test/Training HxGN OnCall Dispatch Database Servers .............................................. 14 Test and/or Training Interface Communications Servers ............................................... 14 HxGN OnCall Dispatch Specifications for Mobile Unit ........................................................ 15 HxGN OnCall Dispatch | Mobile Unit Client ................................................................... 15 GPS Units ..................................................................................................................... 16 HxGN OnCall Dispatch Specifications for Mobile and Web Servers .................................. 16 HxGN OnCall Mobile Server ......................................................................................... 16 HxGN OnCall Dispatch | Mobile Responder Clients ...................................................... 17 HxGN OnCall Dispatch Specifications for Video Responder and Security Guardian Systems .................................................................................................................. 18 Workstation Components for Video Responder and Security Guardian ........................ 18 Technical Support .................................................................................................................. 20 Submit a Case Online ......................................................................................................... 20 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 5 General Notes This document provides the specifications for hardware required to support the HxGN OnCall® Dispatch system. The specifications in this document reflect technology that is currently considered standard and is routinely available from hardware vendors. These specifications should be used when purchasing new equipment. For those customers with existing hardware and planning on a software upgrade, these specifications are intended to serve as a guide for determining whether existing equipment should be upgraded or replaced to support a mission-critical configuration. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 6 Database Storage Requirements Hexagon's Safety, Infrastructure & Geospatial division has developed the following hardware requirements with the best possible performance and safety in mind. These requirements are intended to provide the required performance during a large incident. HxGN OnCall Dispatch applications and their associated interfaces are database write\read intensive (65% write\35% read). Hexagon recommends that these systems (servers) are not shared with other common applications and that the servers be dedicated to these applications. The most likely single point of bottleneck in a database server is the IO sub-system. The focus with Hexagon's IO storage requirements is on the performance more than on the disk space. Hexagon strongly encourages customers to use Solid State Drives (SSDs) on their database servers. SSDs can provide significantly better performance than spinning drives. Consider how much historical data users want to keep on the live system when deciding on disk space requirements. In particular, features such as attachments, GPS tracking data, and external query results can increase the space requirements. Users may want to place attachments, GPS tracking, and external query results onto separate disks since these tables can become large. For Oracle and SQL Server, the tables are specifically designed to be placed into separate tablespaces (Oracle) or filegroups (SQL Server) for performance and storage. The size of your storage is dependent upon a couple of factors: Storing attachments, images, video, adorned event comments, and tracking data in the database or a separate database How often data is archived When using a SAN to support a virtual environment, Hexagon recommends SSDs be used to meet the IOPs requirements. The ideal configuration would be a SAN that tiers data, meaning that it places the most active data on the fastest drives and less used data on slower drives. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 7 HxGN OnCall Dispatch Specifications Browser Requirements For information on the browsers that were verified for this release see the HxGN OnCall Dispatch Supported Environments. Any other browsers or versions of browsers should be verified and tested before deployment to production use. HxGN OnCall Dispatch Servers The specifications are organized by HxGN OnCall Dispatch system size in extra small, small, medium, and large configurations. A site's hardware must meet the required specifications below in order for the HxGN OnCall Dispatch system to meet the published Hexagon performance standards. Database Servers Item Small Configuration (Less than 50 clients) Medium Configuration (50 - 100 clients) Large Configuration (Greater than 100 clients) Processors 6 cores 10 cores 14 cores Memory 32 GB 64 GB 128 GB Disks - OS 300 GB of space 300 GB of space 300 GB of space Disks - Database and Logs Space of 500 GB and 5000 IOPs (per database) Space of 1000 GB and 10000 IOPs (per database) Space of 2000 GB and 20000 IOPs (per database) Network Single 10 Gb required Single 10 Gb required Single 10 Gb required Windows Server 64-bit Enterprise Edition Enterprise Edition Enterprise Edition Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 8 HxGN OnCall Dispatch Archive Server An archive database should be used to store years of data for reporting, while keeping the live system pruned down to a smaller size to improve performance. The HxGN OnCall Dispatch reporting applications typically read data from an archive database and, dependent on the site, may run on the same server. The HxGN OnCall Dispatch archive server CPU count can be reduced to 4-6 cores (for example, use the requirements defined in the "Application/Interface Servers" section) usually without impacting performance. Be aware that reducing the core count saves SQL costs but the server should be monitored for performance impacts and adjusted accordingly. A single archive server does not require SQL Server Enterprise, but users should be aware of limitations of SQL Server Standard during maintenance tasks and the possible impact on reporting. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 9 HxGN OnCall Dispatch Client Workstations Item Specification Processors i5 processor or greater (Minimum 4 cores) Memory 16 GB minimum; 32 GB recommended Internal Disk 80 GB or greater (Solid State is recommended but is not required.)1 OS Windows 10 64-bit Apple® Mac OS X Video 1920x1080 resolution display 1 The OS and HxGN OnCall Dispatch | Mobile Unit application require ~80 GB of space. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 10 Application Servers Item Extra Small Configuration1 (Less than 35 clients) Small Configuration (35 - 100 clients) Medium Configuration (100 - 400 clients) Large Configuration (Greater than 400 clients) Servers 2 2 4 10 Processors 8 cores 8 cores 8 cores 8 cores Memory 32 GB 32 GB 32 GB 32 GB Disks - OS 100 GB of space 100 GB of space 100 GB of space 100 GB of space Network Single 1 Gb required Single 1 Gb required Single 1 Gb required Single 1 Gb required Windows Server 64-bit 2019 or 2022 Standard or DataCenter 2019 or 2022 Standard or DataCenter 2019 or 2022 Standard or DataCenter 2019 or 2022 Standard or DataCenter 1 For extra small configurations, interfaces can be run on the application server computer to reduce the overall computer count. The "base" set of services need to be run on two separate computers, with additional servers to handle the "busy" services. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 11 HxGN OnCall Dispatch Operational Reports Application Server Item Specification Processors 6 cores Memory 64 GB Disk - OS 300 GB of space1 Network Single 1 Gb required Windows Server 64-bit 2019 or 2022 Standard or DataCenter 1 Hard drive size selection and total storage needs are dependent on call/report volume and data retention plans. High volume customers may require larger capacity disks. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 12 HxGN OnCall Dispatch Specifications for Interface and Communication Servers HxGN OnCall Dispatch Interface and Integration Communication Servers If there are a large number of interfaces (more than 30 or several h igh volume), then an additional interface server may be required. For example, the number of interface servers is more dependent on the number of interfaces instead of the number of users at a site. However, more interfaces require more servers. Consult with a system configuration consultant. The specifications for the interface server can vary based on interface load, and these specifications are considered a starting point. Item Specification Processors 8 cores Memory 32 GB Disk - OS 100 GB of space1 Network Single 1 Gb required Windows Server 64-bit 2019 or 2022 Standard or DataCenter 1 Hard drive size selection and total storage needs are dependent on call/report volume and data retention plans. High volume customers may require larger capacity disks. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 13 RabbitMQ Servers The HxGN OnCall Dispatch Website and Core Services rely on RabbitMQ for message brokering. RabbitMQ must be installed on Windows servers. To make RabbitMQ highly available, three servers are required. HxGN OnCall Dispatch does not persist to messages being passed through RabbitMQ for long periods of time, so a smaller disk size is acceptable. See the HxGN OnCall Dispatch documentation for more information on setting up RabbitMQ. Item Extra Small Configuration (Less than 35 clients) Small Configuration (35 - 100 clients) Medium Configuration (100 - 400 clients) Large Configuration (Greater than 400 clients) Processors 4 cores 4 cores 8 cores 8 cores Memory 16 GB 16 GB 24 GB 32 GB Disks - OS 80 GB of space 300 GB of space 300 GB of space 300 GB of space Network Single 10 Gb required Single 10 Gb required Single 10 Gb required Single 10 Gb required Windows Server 64-bit Enterprise Edition Enterprise Edition Enterprise Edition Enterprise Edition RabbitMQ does not scale horizontally. It must scale vertically. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 14 HxGN OnCall Dispatch | Backup, Test, and Training Servers Off Site Backup HxGN OnCall Dispatch Servers If the off-site HxGN OnCall Dispatch system performance is expected to match the system performance of the production HxGN OnCall Dispatch system, then the off -site system must be configured identically to the production system. If the off -site database server is going to be a synchronous replica with the primary database server, it must match the primary server configuration. Hexagon recommends that they be configured the same way. Test/Training HxGN OnCall Dispatch Database Servers If the test/training system performance is expected to match the load and system performance of the production HxGN OnCall Dispatch system (for example, used for load testing), then the test/training system must be configured identically to the production system. The test HxGN OnCall Dispatch system is used to test new functionality or updates before deployment on the live system. A training HxGN OnCall Dispatch system is a copy of the live system that is used to train new employees without impact to the live system. In addition to the hardware, if your site requires a HxGN OnCall Dispatch system for test/training and wants that system performance to be identical to their production system, then all software licenses must also be the same. If the test system is not used for load testing, follow the guidelines for a small site for server specifications. Using the Standard edition for the database software is acceptable. If a separate training environment is used, follow the guidelines for a small site for server specifications. Using the Standard edition for the database software is acceptable. Training licenses are required if training lasts more than 30 days per year, but they can still exist on the test servers. Test and/or Training Interface Communications Servers Configure the test/training servers identically to their production counterparts. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 15 HxGN OnCall Dispatch Specifications for Mobile Unit HxGN OnCall Dispatch | Mobile Unit Client Item Specification Processors i5 processor or greater (Minimum 4 cores) Memory 16 GB minimum; 32 GB recommended1 Internal Disk 500 GB or greater (Solid State is recommended but is not required.) OS Windows 102 Windows 11 Video 1024x768 or higher resolution display Touch screen is recommended. Ports RS-232 Serial\USB NIC 1 Gb physical and Wireless (WiFi and/or Cellular) 3G or 4G is recommended of cellular wireless data connectivity, either built-in or attached using a USB port. 1Mobile Unit memory requirements are dependent on what other applications are being used, such as field-based reporting, third-party citation application, and so forth. 2 Mobile Unit does not support Google® Android™ or Apple™ iOS™. It is a Windows-only product. Windows RT (Windows using ARM Processor) is not supported. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 16 GPS Units Hexagon AVL products only support the protocols listed below. Devices that support one of these protocols should be compatible with the HxGN OnCall Dispatch | Tracker product. Protocols supported: NMEA (National Marine Electronics Association) TAIP (Trimble ASCII Interface Protocol) If GPS is being reported through Mobile Unit, it must use the NMEA protocol. HxGN OnCall Dispatch Specifications for Mobile and Web Servers HxGN OnCall Mobile Server Item Small Configuration (Less than 50 Dispatcher seats) Medium Configuration (50 - 100 Dispatcher seats) Large Configuration (Greater than 100 Dispatcher seats) Optional HA configuration Requires HA configuration Requires HA configuration Processors 2 cores 4 cores 8 cores Memory 8 GB 16 GB 32 GB Disks - OS 100 GB of space 300 GB of space 300 GB of space Network Single 1 Gb required1 Dual 1 Gb required1 Dual 1 Gb required1 Windows Server 64-bit 2019 or 20222 Standard or DataCenter 2019 or 20222 Standard or DataCenter 2019 or 20222 Standard or DataCenter 1 Hard drive size selection and total storage needs are dependent on call/report volume and data retention plans. High volume customers may require larger capacity disks. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 17 2 For physical servers, Hexagon recommends using teamed NICs configured as switch fault tolerant. Additional Information Hexagon recommends Mobile Server reside on its own server(s). RabbitMQ is required if your site is not using Google's Firebase Cloud Messaging (FCM) and can be installed either on the same server(s) as OnCall Mobile or on separate server(s). RabbitMQ is a separate configuration from HxGN OnCall Dispatch and is only required if you are using the local notification service instead of the default push notification system from Google's Firebase Cloud Messaging (FCM). MongoDB is an optional configuration, is used to support Mobile Server, and can be installed either on the same server(s) as OnCall Mobile or on separate server(s). An existing instance of SQL Server can be used in place of MongoDB to save site configuration and other settings to support Mobile Server. To use SQL Server instead of MongoDB, SQL Server must be installed and configured on the network and accessible from Mobile Server. For production environments, it is recommended at least two instances of the following services are configured: InquiryModule UnitCommandModule Dual network adapters are optional for small configurations. Non-production environments, such as for training or testing, can be configured using a small configuration. Disaster recovery environments should use the configuration that best meets your site's requirements. HxGN OnCall Dispatch | Mobile Responder Clients The following are the supported client devices for the Mobile Responder (also known as HxGN OnCall® Mobile) application: Apple Inc. devices (iPhone® and iPad®) with iOS™ 12 or greater (tested using iPhone 6s, iPhoneX, iPad Pro, and iPad Air2) Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 18 Google LLC Android™ devices with OS versions 10.0 or greater (tested using Samsung Galaxy S9 and Pixel3 XL) For the servers, use the standard database server and Mobile Server specifications defined in the "HxGN OnCall Dispatch | Mobile Responder Server" topic. Hexagon highly recommends that back office communications for Mobile Responder reside on a separate server than interfaces, but on the same server as Mobile Unit, if installed. Mobile Responder uses Leaflet for a mobile-friendly interactive map. The base map and map layers are defined in HxGN OnCall Dispatch | Administrator. Mobile Responder uses an internet-based tile provider such as Google, Bing, Mapbox, MapQuest Open, or any custom tile source a customer may have access to. If ESRI provides a tile source, then the customer could choose to use the custom option. Hexagon uses an HTTP-based tile source to so that maps are not placed on each device, which may only have 8 GB of storage. Certification has been performed on a limited number of devices due to the diversity in the Android market. Testing has been performed with the platforms and devices listed at the beginning of this section. While other devices are viable, Hexagon recommends testing with a single device before purchasing large quantities. See the Hexagon Customer Support page for a definition of viable. HxGN OnCall Dispatch Specifications for Video Responder and Security Guardian Systems The workstation specifications for a system are dependent on the video system provider and the security workstations. For example, they may require a specific video card. The workstation specifications below are provided as a guideline and users should always check with their video system provider. For the servers, use the standard database server and communication server specification are defined in th e HxGN OnCall Dispatch Specifications (on page 7) and the HxGN OnCall Dispatch Specifications for Interface and Communication Servers (on page 12) topics. Workstation Components for Video Responder and Security Guardian Item Specification Operating System Genuine Windows 10 Professional, with Media, 64-bit, English Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 19 Item Specification Processor i7, quad-core, 2.4 GHz, 8 MB cache Memory 32 GB Graphics Minimum: Integrated video card with 256 MB of video Recommended: Discrete video card from AMD®, NVIDIA®, or Intel® To accelerate the decoding of H.264 HEVC video, use one of the following video cards: NVIDIA GeForce GTX 950 NVIDIA GeForce GTX 960 Hard Drive 250 GB SATA 3.0 GB/s Network Single 1 Gb required Multi Select Monitors 21-inch monitors Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall® Dispatch Suite 20 Technical Support Hexagon's Safety, Infrastructure & Geospatial division provides several ways to contact Support, including online case submission and phone support. For general Hexagon information, call 800-345-4856 (US). For phone support, see the Contact Support page https://supportsi.hexagon.com/help/s/contactsupport?language=en_US . Submit a Case Online Hexagon provides an online method of requesting support 24/7. 1. Go to the Support page https://supportsi.hexagon.com/help/s/?language=en_US. 2. Click Log in. 3. Type your username and password, and click Log in. 4. From the Resources list, select Contact Support. The Contact Support page displays. 5. Click Online case submission. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Statement of Work 98 Attachment F – System Configuration Diagram [following this page] Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 1 System Overview TABLE OF CONTENTS System Overview Page 1 Hardware Specifications Page 2 Client Hardware Specifications Page 3 OnCall Mapping & Management Environments Page 4 OnCall Dispatch Prod Environment Page 5 OnCall Dispatch DR Environment Page 6 OnCall Dispatch Test & Training Environments Page 7 Notes Page 8 Server Numbering Legend Notation of a, b, and c for servers indicates the following: a = Production Server b = Redundant Server c = Cold Backup Server This notation indicates which interface servers are serving the same functions within their server group, respectively. Notation of 1a, 2a, 3a, …, etc., for servers indicates that each server is an active production server. Notation of 1b, 2b, 3b, …, etc., for servers indicates that each server is an active redundant server. MANAGEMENT PRODUCTION ENVIRONMENT: Domain Controller/DNS Server #1, 2 Kemp Load Balancing Appliance System Management Server #1 vCenter Server #1 Zabbix Monitoring Server Graylog Monitoring Server MAPPING PRODUCTION ENVIRONMENT: Mapping Server #1, 2, 3 (Production) Mapping Staging Server CAD PRODUCTION ENVIRONMENT: Database Server #1, 2 (CAD SQL AlwaysOn Cluster) Archive Database Server #1a OnCall Message Queue Server #1a, 2a, 3a Web Server, #1, 2, 3 Application Server #1a, 2a, 3a, 4a Video Streaming and Configuration Server Video Streaming Server #1 (Load Balanced) Communications/Interface Server #1a Communications/Interface Server #2a OnCall Analytics Data Warehouse/Platform Server OnCall Analytics Reporting Application Server MANAGEMENT DR ENVIRONMENT: Domain Controller/DNS Server #3 Kemp Load Balancing Appliance System Management Server #2 vCenter Server #2 MAPPING DR ENVIRONMENT: Mapping Server #1, 2, 3 CAD DR ENVIRONMENT: Database Server #3 (CAD SQL AlwaysOn Cluster) OnCall Message Queue Server #1c, 2c, 3c Web Server DR #1, 2, 3 Application Server #1b, 2b, 3b, 4b Communications/Interface Server #1c (Cold Backup) Communications/Interface Server #2c Video Streaming Configuration Server #1 Video Streaming Server #1 CAD TEST ENVIRONMENT: Test Database Server #1, 2 (CAD SQL AlwaysOn Cluster) Test OnCall Message Queue Server #1, 2, 3 Test Communications/Interface Server #1 Test Communications/Interface Server #2 Test Web Server #1, 2 Test Application Server #1, 2 CAD TRAINING ENVIRONMENT: Training Database Server Training OnCall Message Queue Server Training Web Application Server E-Learning OnCall Agency 1 Total 11 11 25 25 100 100 190 190 81.5 231 0 CAD Install Calculator Production numbers only # Dispatch Advantage CCU # of Dispatch Viewer CCU # of Mobile Unit CCU # of Mobile Responder CCU Total # of Effective Seats CAD Total # of Cad and OMU clients Total # of Effective Seats RMS Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 2 Hardware Specifications Provisioned Required Provisioned Required Provisioned Required 252 101 1,248 1,498 23 34 54,100 Provisioned Required Provisioned Required Provisioned Required 150 60 642 770 4 6 14,500 *Mobile device VPN Bandwidth minimum requirement 490 Mbps Quantity Make 3 * Kemp 13 Microsoft 4 Microsoft 2 Microsoft * Kemp Load Balancers are required as part of the base, exceptions are not allowed Hexagon recommends Data at Rest Encryption per CJIS Security Policy sect 5.10.1.2.2 Production Disaster Recovery Bill of Material Memory Memory Site 1 Totals vCPUs (3:1)Disk (TB)IOPS Site 2 Totals vCPUs (3:1)Disk (TB) Model VLM-3000 (Enterprise Plus License) Description Load Balancers IOPS Archive (No AAG) / Training Database Test Database SQL 2022 Standard Edition W/SA SQL 2022 Developer Edition SQL 2022 Enterprise Edition w/ SA AAG Database Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 3 Client Hardware Specifications OnCall Dispatch Advantage Workstations (Supervisor, Production, Backup, Test, Training) Recommended Specifications: Windows 10/11 (64-bit) or Apple Mac OS X Modern Web Browser (for OnCall Dispatch access) Processor: i5-2350M or greater (not ARM) Memory: 16GB min; 32GB recommended Internal Disk: 80GB or greater 1920 x 1080 resolution display OnCall Mobile Unit MDTs Recommended Specifications: Windows 10/11 Professional, 64-bit Processor: i5-2350M or greater (not ARM) Memory: 16GB min; 32GB recommended 500GB hard drive 1,024 x 768 resolution (touch screen recommended) RS-232 Serial\USB 1 Gb physical and Wireless (WiFi and/or Cellular) 4G or 5G is recommended of cellular wireless data connectivity, either built-in or attached using a USB port. Mobile Responder Recommended Specifications: Apple® Inc. devices (iPhone® and iPad®) with iOS or greater (Tested using iPhone 6s, iPad Pro, and iPad Air2) Google® Inc. Android devices with OS versions 9.0 or greater (Tested using Samsung Galaxy S9 and Pixel3 XL) Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 4 OnCall Dispatch Management & Mapping Environments vCenter Server #1 Linux OVA vCenter Server Standard System Management Server #1 Windows Server Production Disaster Recovery OnCall Management Environment OnCall Management Environment Mapping Staging Server Windows Server Mapping Server #1, 2, 3 (Production) Windows Server Qty: 3 Mapping Server #1, 2, 3 (DR) Windows Server Qty: 3 OnCall Mapping EnvironmentOnCall Mapping Environment Kemp Load Balancing Appliance Qty: 2 Hexagon Domain Domain Controller/DNS Server #1, 2 Windows Server Qty: 2 Hexagon Domain Domain Controller/DNS Server #1, 2 Windows Server Qty: 2 vCenter Server #2 Linux OVA vCenter Server Standard System Management Server #2 Windows Server Kemp Load Balancing Appliance Qty: 1 Hexagon Domain Domain Controller/DNS Server #3 Windows Server Zabbix Monitoring Server Zabbix Software (free download) Qty: 1 Graylog Monitoring Server Graylog Software (free download) Qty: 1 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 5 OnCall Dispatch Production Environment Communications/Interface Server #1a Windows Server HxGN OnCall Dispatch | RestAPI Xalt Runtime Engine COTS Interfaces: ANI/ALI Interface (included with OnCall Dispatch) HxGN OnCall Dispatch | Informer (Qty: 1) - NCIC - Query to OneSolution CAD - Query to OneSolution RMS HxGN OnCall Dispatch | Fire Station Printing - Rip and Run HxGN OnCall Dispatch | CAD Link - OneSolution RMS - OneSolution FTO HxGN OnCall Dispatch | Fire Link (Qty: 2) - ESO - FirstDue - Pagetrack - Firehouse HxGN OnCall Dispatch | Tracker CCU (Qty: 250) - for radio HxGN OnCall Dispatch | Call-Taker Interface (Qty: 2) - for RapidSOS - for Text to 911 HxGN OnCall Dispatch | Notifications - for PageGate Standard Interfaces: RapidSOS OnCall Call-Taker Interface Fire Station Alerting OnCall Dispatch Interface PLT OnCall Dispatch Interface - Motorola P25 External Alarms OnCall Dispatch Interface - ASAP to PSAP Custom Interfaces: Text to 911 Query to OneSolution CAD Query to OneSolution RMS Consulting Services: Eventide Recording Third Party Product: CommSys ConnectCIC (for NCIC/FCIC) - ASAP Application Server #1a, 2a, 3a, 4a Windows Server ISM Services included with OnCall Dispatch Qty: 4 CAD MS SQL AlwaysOn Cluster Archive Database Server #1a Windows Server Microsoft SQL Server 2022 SE with SA OnCall Analytics Reporting Server Windows Server Microsoft SQL Server 2022 EE with SA Power BI Report Server (included with SQL EE with SA) HxGN OnCall Analytics | Dispatch Advantage OnCall Analytics Data Warehouse/Platform Server Windows Server IIS (included with Windows Server) Microsoft SQL Server 2022 EE with SA Visual Studio 2019 SQL Server Data Tools (download) OnCall Message Queue Server #1a, 2a, 3a Windows Server RabbitMQ (OpenSource) Qty: 3 Communications/Interface Server #2a Windows Server HxGN OnCall Dispatch | RestAPI ANI/ALI Interface (included with OnCall Dispatch) Redundant copies are available for all proposed interfaces at an additional cost; however, implementation is subject to the customer’s ability to provide connection to the applicable system. Video Streaming Server #1 (Load Balanced) Windows Server Video Streaming and Configuration Server #1 Windows Server PostgreSQL HxGN Video Streamer VMS (Qty: 2) Web Server #1, 2, 3 Windows Server IIS (included with Windows Server) HxGN OnCall Dispatch | Advantage CCU (Qty: 11) HxGN OnCall Dispatch | Viewer CCU (Qty: 25) HxGN OnCall Dispatch | Advanced Mapping CCU (Qty: 11) HxGN OnCall Dispatch | Resource Management CCU (Qty: 11) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 11) HxGN OnCall Dispatch | Video Responder Advantage (Qty: 11) HxGN OnCall Dispatch | Mobile Unit CCU (Qty: 100) HxGN OnCall Mobile Server (Qty: 3) HxGN OnCall Dispatch | Mobile Responder CCU (Qty: 190) Qty: 1, 2, 3 Database Server #1, 2 Windows Server Microsoft SQL Server 2022 EE with SA Intergraph Licensing Server Qty: 2 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 6 OnCall Dispatch Disaster Recovery Environment Communications/Interface Server #1c (Cold Backup) Windows Server HxGN OnCall Dispatch | RestAPI Xalt Runtime Engine ANI/ALI Interface (included with OnCall Dispatch) HxGN OnCall Dispatch | Informer (Qty: 1) - NCIC - Query to OneSolution CAD - Query to OneSolution RMS HxGN OnCall Dispatch | Fire Station Printing - Rip and Run HxGN OnCall Dispatch | CAD Link - OneSolution RMS -OneSolution FTO HxGN ONCall Dispatch | FireLink (Qty: 2) - ESO - FirstDue - Pagetrack - Firehouse HxGN OnCall Dispatch | Tracker CCU (Qty: 250) - for radio HxGN OnCall Dispatch | Call-Taker Interface (Qty: 2) - for RapidSOS - for Text to 911 HxGN OnCall Dispatch | Notifications - for PageGate Standard Interfaces: RapidSOS OnCall Call-Taker Interface Fire Station Alerting OnCall Dispatch Interface PLT OnCall Dispatch Interface - Motorola P25 External Alarms OnCall Dispatch Interface - ASAP to PSAP Third Party Product: CommSys ConnectCIC (for NCIC) Backup interface licenses are available for all proposed interfaces. However, implementation is subject to customer’s ability to provide connectivity to the applicable system. Application Server #1b, 2b, 3b, 4b Windows Server ISM Services included with OnCall Dispatch Qty: 4 CAD MS SQL AlwaysOn Cluster OnCall Dispatch Database Server #3 Windows Server Microsoft SQL Server 2022 EE with SA Intergraph Licensing Server OnCall Message Queue Server #1c, 2c, 3c Windows Server RabbitMQ (OpenSource) Qty: 3 Web Server DR #1, 2, 3 Windows Server IIS (included with Windows Server) HxGN OnCall Dispatch | Advantage CCU (Qty: 11) HxGN OnCall Dispatch | Viewer CCU (Qty: 25) HxGN OnCall Dispatch | Advanced Mapping CCU (Qty: 11) HxGN OnCall Dispatch | Resource Management CCU (Qty: 11) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 11) HxGN OnCall Dispatch | Video Responder Advantage (Qty: 11) HxGN OnCall Dispatch | Mobile Unit CCU (Qty: 100) HxGN OnCall Mobile Server (Qty: 3) HxGN OnCall Dispatch | Mobile Responder CCU (Qty: 190) Mobile Responder does not have backup licenses available since it is a smartphone application. The production licenses would be redirected to the backup servers if the production servers were to be unavailable. Qty: 2, 3 Communications/Interface Server #2c Windows Server HxGN OnCall Dispatch | RestAPI ANI/ALI Interface (included with OnCall Dispatch) Video Streaming Server #1 (Load Balanced) Windows Server Video Streaming and Configuration Server #1 Windows Server PostgreSQL HxGN Video Streamer VMS (Qty: 2) Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 7 CAD Test & Training Environments Test Application Server #1, 2 Windows Server ISM Services included with OnCall Dispatch Qty: 2 Test OnCall Message Queue Server #1, 2, 3 Windows Server RabbitMQ (OpenSource) Qty: 3 OnCall Dispatch Test Environment Test Communications/Interface Server #1 Windows Server HxGN OnCall Dispatch | RestAPI Xalt Runtime Engine Xalt Developer Engine External Alarms OnCall Dispatch Interface Third Party Product: CommSys ConnectCIC (for ASAP) Test interface licenses are available for all proposed interfaces. However, implementation is subject to customer’s ability to provide connectivity to the applicable system. Training Database Server Windows Server Microsoft SQL Server 2022 SE with SA Intergraph Licensing Server OnCall Dispatch Training Environment Training Web Application Server Windows Server HxGN OnCall Dispatch | RestAPI HxGN OnCall Dispatch | Advantage CCU (Qty: 7) HxGN OnCall Dispatch | Resource Management CCU (Qty: 7) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 7) HxGN OnCall Dispatch | Mobile Unit CCU** (Qty: 7) Training interface licenses are available at an additional cost for all proposed interfaces. However, implementation is subject to customer’s ability to provide connectivity to the applicable system. Training OnCall Message Queue Server Windows Server RabbitMQ (OpenSource) E-Learning* Dynamo Curriculum HxGN OnCall Dispatch Admin (Qty: 12) - for core team training during the Project Dynamo Curriculum HxGN OnCall Analytics Admin (Qty: 6) - for core team training during the Project *Each license lasts for one year and can be renewed upon request. Test Web Server #1, 2 Windows Server IIS (included with Windows Server) HxGN OnCall Dispatch | Advantage CCU (Qty: 11) HxGN OnCall Dispatch | Viewer CCU (Qty: 25) HxGN OnCall Dispatch | Advanced Mapping CCU (Qty: 11) HxGN OnCall Dispatch | Resource Management CCU (Qty: 11) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 11) HxGN OnCall Dispatch | Video Responder Advantage (Qty: 11) HxGN OnCall Dispatch | Mobile Unit CCU (Qty: 100) HxGN OnCall Mobile Server (Qty: 2) HxGN OnCall Dispatch | Mobile Responder CCU (Qty: 190) Qty: 2 CAD Test MS SQL AlwaysOn Cluster Test Database Server #1, 2 Windows Server Microsoft SQL Server 2022 DE Intergraph Licensing Server Qty: 2 Test Communications/Interface Server #2 Windows Server HxGN OnCall Dispatch | RestAPI Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Color Legend Black – Base products Red – Optioned products Green – Customer-furnished products Orange County, NC OnCall Dispatch Hardware & Software Configuration February 2024 8 Notes Client Notes: 1. OnCall supports current Chrome, Edge, and Safari browsers. 2. OnCall Dispatch Advantage can use the Customer ’s map source via a URL provided by the Customer. However, Hexagon recommends the Customer have a dedicated highly available s eparate instance of the map for OnCall to access. General Notes: 1. Hexagon assumes that the Local Area Network (LAN), the wide area network (WAN), Active Directory, and Domain Name System (DNS) infrastructure will be provided and staged by the Customer. Each web client connection consumes roughly 2-5 Mbps, so the network between the clients and the web server must have sufficient capacity to handle all concurrent clients. The workstation used to access the website should be on a network with a minimum bandwidth of 100 Mbps or higher. 2. All workstations, PCs, laptops, and specified peripheral hardware provided by the Customer are assumed to meet the specifi cations delineated on this diagram. 3. Hexagon assumes that the Customer will provide WAN communications, including wireless network communications. 4. Hexagon recommends VMware for virtualized servers and as such that the mirrored databases do not reside on the same physic al host server. vSphere Enterprise Plus licensing is encouraged for using Distributed Resource Scheduling (DRS) to allow for affinity rules to keep databases separate and balance the system load during peak util ization. VMware and Microsoft require 10GB Ethernet connectivity for vMotion of SQL Always On Availability Group virtual machines. 5. The hardware specifications provided in this diagram do not account for the capacity that may be required for converted data. 6. This configuration depicts the system designed for automatic failover from the primary site to a secondary site. The capab ility for automatic failover between sites is dependent upon the Customer’s network having less than 10 millisecond (ms) latency between the servers across sites, including, the latency between all of the DBs in a cl uster and the Interface Servers 1a and 1b must be less than 10ms. In the event the Customer is unable to meet this network requirement, then the system should be updated to move automatic failover within the primary site only. 7. This Configuration Diagram illustrates the proposed hardware and software configuration at the time of submission. During implementation, the Hexagon Implementation Team, or a Hexagon subcontractor, may alter this configuration to reflect the negotiated system or alter the location of software to take advantage of efficiencies determined following submission. 8. Non-production interface licenses are available for proposed interfaces. However, implementation is subject to Customer ’s ability to provide connection to the applicable system. All third-party external interface connections required for non-production Environments are the responsibility of the Customer and/or third -party vendor(s). 9. The OnCall test environment is sized for functional testing. If the Customer desires to perform load testing in the test e nvironment, then the specifications in this configuration diagram will need to be re- evaluated and adjusted. 10. HxGN OnCall Mobile Server is a no-cost administration tool used to manage the Mobile Responder app. 11. CCU refers to concurrent client user 12. Hexagon assumes that the customer will provide all client access licenses (CALs) to maintain system compliancy with Micro soft policy. 13. Xalt Developer Note: Hexagon’s Xalt Developer Engine and associated training courses is included to allow the Customer to be able to create interfaces as they need. Xalt interfaces, whether Hexagon developed or Customer developed, will reside on the Production Interface Server. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 99 Attachment G – CAD/Mobile Functional Specifications Matrix In addition to the functionality listed in the attachment, Hexagon agrees to provide the following: For a Multi-Agency event, OnCall Dispatch Advantage will provide an option to the user to dispatch all the displayed units in the Recommend list, which includes units from other Agencies. [following this page] Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 1 Call Handling / CAD Event Creation Call Handling Import and attach/append, automatically upon user command, automatic number information (ANI) and automatic location information (ALI) to a CFS. HxGN OnCall Dispatch | Call- Taker 4 Call Handling / CAD Event Creation Call Handling Import (automatically) a CFS generated on an MDC. HxGN OnCall Dispatch | Mobile Unit 5 Call Handling / CAD Event Creation CAD Incident / Event Types Allow for system administrator-defined CAD incident types or nature codes. HxGN OnCall Dispatch | Viewer 6 Call Handling / CAD Event Creation CAD Incident / Event Types Provide the capability to create an event, assign a unit, and close the event with a disposition without going through the dispatch process steps. HxGN OnCall Dispatch | Viewer 7 Call Handling / CAD Event Creation CAD Incident / Event Types Provide the capability to flag a CFS as an “Advised Event” separate from the incident type/nature code. HxGN OnCall Dispatch | Viewer 8 Call Handling / CAD Event Creation Update Call for Service Event Data Enable the user to enter supplemental (new) information into the CFS event record of one or more user-specified CAD events. HxGN OnCall Dispatch | Viewer 9 Call Handling / CAD Event Creation Update Call for Service Event Data Display a notification of the event update at each appropriate CAD position whenever an active event record is updated, as determined by the system’s configuration. HxGN OnCall Dispatch | Viewer 10 Call Handling / CAD Event Creation Update Call for Service Event Data Create an automatic time/date stamp for every transaction related to an event, and store the responsible operator’s identification (ID), the console ID, and the nature of the change. HxGN OnCall Dispatch | Viewer Page 1 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 11 Call Handling / CAD Event Creation Update Call for Service Event Data Add audit records to the event history or store audit records in the CAD system’s audit log file in chronological order; and, provide a complete historical audit of all event activity (e.g., comments, unit status changes, license plate information, field updates). HxGN OnCall Dispatch | Viewer 12 Call Handling / CAD Event Creation Update Call for Service Event Data Store old entry information, with the appropriate date, time, operator ID, and console stamps if the new entry replaces existing information in the event record. HxGN OnCall Dispatch | Viewer 13 Call Handling / CAD Event Creation Update Call for Service Event Data Enable the audit information to be retrieved and printed in both summary and detailed formats when incident information is displayed. HxGN OnCall Dispatch | Operational Reports 14 Call Handling / CAD Event Creation Update Call for Service Event Data Support ease of entry for supplemental event information and changes to existing event information. HxGN OnCall Dispatch | Viewer 15 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to display a supplemental data entry screen by specifying either the event number or a unit assigned to the event. HxGN OnCall Dispatch | Viewer 16 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to display a data entry screen to change information previously entered into a CAD event by specifying either the event number or a unit assigned to the event. HxGN OnCall Dispatch | Viewer Page 2 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 17 Call Handling / CAD Event Creation Update Call for Service Event Data Provide agency-definable visual and audible alerts to notify field units and other appropriate CAD system users, including users of systems interfaced to CAD such as Mobile Data Computers, of event changes and supplemental information. HxGN OnCall Dispatch | Viewer 18 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to add supplemental information and/or change active events HxGN OnCall Dispatch | Viewer 19 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to update any field in the CFS event record (except user-designated fields, such as application-generated times and date stamps, operator identification information, ANI/ALI information, and CAD position that completed a CAD transaction). HxGN OnCall Dispatch | Viewer 20 Call Handling / CAD Event Creation Update Call for Service Event Data Document all changes and supplemental information in the event history HxGN OnCall Dispatch | Viewer 21 Call Handling / CAD Event Creation Update Call for Service Event Data Provide an event update/change data entry screen HxGN OnCall Dispatch | Viewer 22 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to update or change a unit’s most recent event by entering the unit’s identification or any unit that is currently assigned. HxGN OnCall Dispatch | Viewer 23 Call Handling / CAD Event Creation Update Call for Service Event Data Require confirmation from the user when attempting to update any field in a closed event.HxGN OnCall Dispatch | Viewer *Reopen command is used to update a closed event, and requires a comment/reason when executing 24 Call Handling / CAD Event Creation Update Call for Service Event Data Provide the user with acknowledgment that an update to a CAD event record was successfully completed. HxGN OnCall Dispatch | Viewer 25 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to supplement and/or change active events. HxGN OnCall Dispatch | Viewer Page 3 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 26 Call Handling / CAD Event Creation Update Call for Service Event Data Allow the user to supplement and/or change any field of a closed event without having to change the state of the event. HxGN OnCall Dispatch | Advantage *currently support remarks, disposition, and cross reference updates for closed event s 27 Call Handling / CAD Event Creation Determine Dispatch Need Provide the capability to close out the CFS record without assigning a resource, if it is determined that a CFS does not require the assignment of a resource(s). HxGN OnCall Dispatch | Essentials 28 Call Handling / CAD Event Creation Determine Dispatch Need Allow the user to append a disposition code and comments to events that are not assigned any resources. HxGN OnCall Dispatch | Essentials 29 Call Handling / CAD Event Creation Utilize Incident Disposition Allow the user to enter one or more dispositions, as dictated by agency policy, when a CAD event is closed. HxGN OnCall Dispatch | Essentials 30 Call Handling / CAD Event Creation Utilize Incident Disposition Close a CAD event record automatically if no resources remain assigned to the event. HxGN OnCall Dispatch | Essentials 31 Call Handling / CAD Event Creation Utilize Incident Disposition Provide the capability for a mobile unit to enter one or more dispositions when clearing from a CAD event. HxGN OnCall Dispatch | Mobile Unit 32 Call Handling / CAD Event Creation Utilize Incident Disposition Allow the system administrator to define disposition codes. HxGN OnCall Dispatch | Viewer 33 Call Handling / CAD Event Creation Assign Incident Classification and Priority Enable CAD users to select the appropriate incident/event type from a pre- defined list of codes based upon information received from reporting party. HxGN OnCall Dispatch | Viewer 34 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide, in a multiple dispatch agency or jurisdiction environment, the ability to create multiple CFS events with a single CFS event entry (e.g. a shooting incident type would create a law enforcement, EMS, and possibly a fire event). HxGN OnCall Dispatch | Viewer Page 4 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 35 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide the ability to generate a CFS event with only the location and incident type code entered.HxGN OnCall Dispatch | Viewer 36 Call Handling / CAD Event Creation Assign Incident Classification and Priority Allow the user to upgrade or downgrade the CFS event to fit the reported event by changing the priority for the event. HxGN OnCall Dispatch | Viewer 37 Call Handling / CAD Event Creation Assign Incident Classification and Priority Allow the user to utilize incident screening menus, such as a drop-down menu, to assist in determining the appropriate incident/event type code. HxGN OnCall Dispatch | Viewer 38 Call Handling / CAD Event Creation Assign Incident Classification and Priority Allow the user to interrupt the CFS event creation process and save entered information, sometimes known as call stacking, to process a higher priority incoming incident. HxGN OnCall Dispatch | Call- Taker 39 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide a warning notification of the held CFS event generated at an administrator-configured time. Any position can review current CFS events, retrieve a partial CFS record, and complete the CFS event entry. HxGN OnCall Dispatch | Call- Taker *stacked/partial events can only be retrieved by the position who saved on the stack 40 Call Handling / CAD Event Creation Assign Incident Classification and Priority The number of partial CFS events that can be stacked by a single position be an administrator- configurable system parameter. HxGN OnCall Dispatch | Call- Taker 41 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide the ability to override the event priority for each agency. HxGN OnCall Dispatch | Viewer 42 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide the ability to create and maintain incident screening menus or prompts that can be used to aid the call taker in determining the appropriate incident/event type code. HxGN OnCall Dispatch | Viewer Page 5 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 43 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide the ability to save one or more partially completed CFS events in order to enter a higher priority incident, keeping all entered data intact. HxGN OnCall Dispatch | Call- Taker 44 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide a warning (visual and/or audible) that a partially completed CFS event has been held for an administrator-defined period of time. HxGN OnCall Dispatch | Call- Taker 45 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide the ability to view a summary of all system- wide, partially-completed CFS events being held and awaiting completion. Include, at a minimum, the position and user ID that placed the CFS event on hold and the elapsed time that the CFS event has been on hold. HxGN OnCall Dispatch | Call- Taker 46 Call Handling / CAD Event Creation Assign Incident Classification and Priority Provide the ability to redirect assigned resources to a higher priority CFS event based on agency defined criteria. HxGN OnCall Dispatch | Essentials 47 Call Handling / CAD Event Creation Assign Incident Classification and Priority Store all active and partially completed CAD events in system administrator- configurable queues.HxGN OnCall Dispatch | Call- Taker 48 Call Handling / CAD Event Creation Assign Incident Classification and Priority Allow CAD users to be able to select a partially completed CFS event from a CAD event queue and complete the CFS entry process. HxGN OnCall Dispatch | Call- Taker 49 Call Handling / CAD Event Creation Check for Duplicate Incidents Store all transactions resulting from the duplicate event detection process in the system’s audit log.HxGN OnCall Dispatch | Call- Taker Page 6 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 50 Call Handling / CAD Event Creation Check for Duplicate Incidents Identify during the creation of a CFS event whether the event is a potential duplicate of an active CAD event or an event recently closed; and, notify the call taker of the results. HxGN OnCall Dispatch | Call- Taker 51 Call Handling / CAD Event Creation Check for Duplicate Incidents Check, as configured by the system administrator, by exact street address, street address block range, or geo-coordinates, the location of each new CFS event to determine whether another event exists. HxGN OnCall Dispatch | Call- Taker 52 Call Handling / CAD Event Creation Check for Duplicate Incidents Check, as configured by the system administrator, within a pre-defined search radius of the location of each new CFS event, to determine whether another event exists within the search radius. HxGN OnCall Dispatch | Call- Taker 53 Call Handling / CAD Event Creation Check for Duplicate Incidents Allow an authorized user to change the duplicate event search parameters (e.g. distance, exact street address match only, street address block range). HxGN OnCall Dispatch | Advantage 54 Call Handling / CAD Event Creation Check for Duplicate Incidents Present the user with the following information for each potential duplicate event if potential duplicates are located: o Incident ID o Type of incident o Location of the incident o Status of the incident HxGN OnCall Dispatch | Viewer Page 7 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 55 Call Handling / CAD Event Creation Check for Duplicate Incidents Allow the user the ability to create a new CFS event and link the event to the primary event records; or, to merge any new information contained in a duplicate event into the main event record associated with the identified duplicate CAD event. HxGN OnCall Dispatch | Viewer 56 Call Handling / CAD Event Creation Check for Duplicate Incidents Allow the call taker to re-open closed CAD events that are duplicates of a new event, add additional information to the re-opened CAD event records, and, if necessary, re- route them back through the dispatch process. HxGN OnCall Dispatch | Viewer 57 Call Handling / CAD Event Creation Check for Duplicate Incidents Cross-reference duplicate events to the primary event records, leave both events open, or abandon processing of the duplicate event. HxGN OnCall Dispatch | Viewer 58 Call Handling / CAD Event Creation Incident Information Provide the ability to create a CFS with minimum required fields (e.g. location and event type).HxGN OnCall Dispatch | Viewer 59 Call Handling / CAD Event Creation Incident Information Provide the ability to dispatch once location and nature are obtained. HxGN OnCall Dispatch | Essentials 60 Call Handling / CAD Event Creation Incident Information Provide the ability to alter/augment event as further information is obtained by the call taker.HxGN OnCall Dispatch | Viewer 61 Call Handling / CAD Event Creation Incident Information Include an automated connection/interface to the 9-1-1 telephone system to use ANI/ALI data to populate the incident entry screen form. HxGN OnCall Dispatch | Call- Taker 62 Call Handling / CAD Event Creation Incident Information Provide the ability to enter unlimited narrative with text wrap-around feature. HxGN OnCall Dispatch | Viewer 63 Call Handling / CAD Event Creation Incident Information Provide the ability to use ANI/ALI data to assist with CFS entry. HxGN OnCall Dispatch | Call- Taker Page 8 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 64 Call Handling / CAD Event Creation Determining Capture Locations Obtain all different versions (Standard, Standard Plus, Extended Plus) of ANI/ALI information automatically from interfaced phone systems without requiring the user to manually re-enter the information into a CAD event entry screen. HxGN OnCall Dispatch | Call- Taker 65 Call Handling / CAD Event Creation Determining Capture Locations Append 9-1-1 reported data to the record if the user has entered data into any field before accepting the 9-1-1 information, but not overwrite the data entered by the user. HxGN OnCall Dispatch | Call- Taker 66 Call Handling / CAD Event B358Creation Location Verification Provide the ability to enter a unique building and unit number to clearly identify the location (e.g. 100 West Ave., Bldg. 2, Unit 1). HxGN OnCall Dispatch | Viewer 67 Call Handling / CAD Event Creation Location Verification Depending on the permissions granted to the user, provide the ability to edit ALI 9-1-1 information in the event record if the information provided by the phone company is incorrect. HxGN OnCall Dispatch | Call- Taker 68 Call Handling / CAD Event Creation Location Verification Include the following fields for all records containing an address: street number; apartment/suite number; street; road type (Drive, Avenue, Street, Alley); direction; city, state, and/or zip code. HxGN OnCall Dispatch | Viewer 69 Call Handling / CAD Event Creation Location Verification Validate entered incident addresses against the CAD geofile. HxGN OnCall Dispatch | Viewer 70 Call Handling / CAD Event Creation Location Verification Provide various suggestions to assist users in selecting accurate incident locations. HxGN OnCall Dispatch | Viewer 71 Call Handling / CAD Event Creation Location Verification Allow each address or commonplace name to have an unlimited number of alias names. HxGN OnCall Dispatch | Viewer Page 9 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 72 Call Handling / CAD Event Creation Location Verification Allow authorized users to store multiple names for businesses and tenants for a given street address.HxGN OnCall Dispatch | Viewer 73 Call Handling / CAD Event Creation Location Verification Organize the display of possible address matches in an ergonomic, easily understood manner that aids users in identifying valid incident locations. HxGN OnCall Dispatch | Viewer 74 Call Handling / CAD Event Creation Location Verification Allow authorized users to configure their tactical map display to show jurisdictional boundaries (e.g. city boundaries) and to display potential valid incident locations by jurisdiction. HxGN OnCall Dispatch | Viewer 75 Call Handling / CAD Event Creation Location Verification Allow the user, in case the location entered by the user is unverifiable (e.g. the location does not exist in the geofile), the capability to exit or bypass the verification process and manually route the CFS event(s) to the appropriate dispatch position(s). HxGN OnCall Dispatch | Viewer 76 Call Handling / CAD Event Creation Location Verification Provide the ability to enter a partial street name, with a minimum number of characters, and be presented with a list of possible matches to pick from for an exact match. HxGN OnCall Dispatch | Viewer 77 Call Handling / CAD Event Creation Location Verification Provide the ability to enter a misspelled street name and be presented with a list of possible matches based on SOUNDEX6 and/or other methodology. HxGN OnCall Dispatch | Viewer 78 Call Handling / CAD Event Creation Location Verification Provide the ability to enter common street alias and abbreviations instead of the actual street name (e.g. MLK for Martin Luther King Blvd). HxGN OnCall Dispatch | Viewer Page 10 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 79 Call Handling / CAD Event Creation Location Verification Provide the ability to override the CAD system’s geofile by manually entering valid response area data. HxGN OnCall Dispatch | Viewer 80 Call Handling / CAD Event Creation Location Verification Provide the ability to enter a reason for an overridden location. HxGN OnCall Dispatch | Viewer 81 Call Handling / CAD Event Creation Location Verification Provide the ability to generate a report of geofile overrides. HxGN OnCall Dispatch | Advantage 82 Call Handling / CAD Event Creation Location Verification Provide the ability to display the incident location in relation to other active incidents on the system’s tactical map display during the CAD event entry process. HxGN OnCall Dispatch | Viewer 83 Call Handling / CAD Event Creation Retrieve Incoming Calls Include an interface to the 9-1-1 telephone system that, upon user command, causes the automatic transfer of an emergency call’s ALI information from the telephone system to an appropriate field of the CAD event data entry screen. HxGN OnCall Dispatch | Call- Taker 84 Call Handling / CAD Event Creation Retrieve Incoming Calls Allow call takers to initiate a CAD command/or function that will cause the CAD system to populate the CAD event data entry screen with call- back telephone number information if it is available. HxGN OnCall Dispatch | Call- Taker 85 Call Handling / CAD Event Creation Retrieve Incoming Calls Transfer, depending on PSAP policy, the telephone subscriber’s name to a field in the CAD event data entry screen’s reporting party’s name data field. HxGN OnCall Dispatch | Call- Taker 86 Call Handling / CAD Event Creation Retrieve Incoming Calls Include data fields within the CAD event data entry screen for reporting party’s name, address and callback number. HxGN OnCall Dispatch | Viewer Page 11 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 87 Call Handling / CAD Event Creation Involved Person Information Be capable of collecting the following information about each individual associated with an event: Age, Date of Birth, Eye Color, Hair color, Height, Name, Operators License Number, Operators License State, Race, Sex, Weight, Additional remarks (e.g. clothing description, scars/marks/tattoos) HxGN OnCall Dispatch | Viewer 88 Call Handling / CAD Event Creation Involved Person Information Initiate an automatic query, upon entry of information about an individual associated with an event, using the following guidelines at a minimum: If the name only is known, then a name query be initiated to local files capable of performing a lookup based only on a name, or If the minimum required fields contain enough data for state and federal queries, then the system initiate queries to local, state and federal databases. HxGN OnCall Dispatch | Informer 89 Call Handling / CAD Event Creation Involved Person Information Return all responses from local, state, and federal databases to the data entry originator.HxGN OnCall Dispatch | Informer Page 12 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 90 Call Handling / CAD Event Creation Involved Person Information Bring positive responses (e.g. possible “hits”) that require a review by the originator to the attention of the originator through the use of audible and visual indicators. HxGN OnCall Dispatch | Informer 91 Call Handling / CAD Event Creation Involved Vehicle Information Return all responses from local, state, and federal databases to the data entry originator.HxGN OnCall Dispatch | Informer 92 Call Handling / CAD Event Creation Involved Vehicle Information Bring positive responses (e.g. possible “hits”) that require a review by the originator to the attention of the originator through the use of audible and visual indicators. HxGN OnCall Dispatch | Informer 93 Call Handling / CAD Event Creation Involved Vehicle Information Be capable of collecting the following information about each vehicle associated with an event: o License plate o License plate state o License plate type o License plate year of expiration o Primary vehicle color o Vehicle Identification Number (VIN) o Vehicle make o Vehicle model o Vehicle year o Secondary vehicle color o Remarks HxGN OnCall Dispatch | Informer Page 13 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 94 Call Handling / CAD Event Creation Involved Vehicle Information Initiate an automatic query to local, state and federal databases, upon entry of information about a vehicle associated with an event, using the following guidelines at a minimum: o License plate number and license plate state o VIN and vehicle make HxGN OnCall Dispatch | Informer 95 Call Handling / CAD Event Creation Involved Vehicle Information Initiate a cascaded query, upon receipt of a response from the DMV containing the name of the registered owner of the vehicle, to local, state and federal databases, to check the wanted status, driver’s license status, and other statuses of interest about the registered owner. HxGN OnCall Dispatch | Informer 96 Call Handling / CAD Event Creation Premises Hazards and Previous History Have the capability to retrieve information about a premise and the surrounding/adjacent area as an automatic function during the creation of a CFS. HxGN OnCall Dispatch | Viewer 97 Call Handling / CAD Event Creation Premises Hazards and Previous History Have the capability to retrieve information about a premises and the surrounding/adjacent area as an ad-hoc query. HxGN OnCall Dispatch | Advantage 98 Call Handling / CAD Event Creation Premises Hazards and Previous History Display historical incident information based on a configurable date range pre-set by the systems administrator, and according to local SOP. HxGN OnCall Dispatch | Viewer 99 Call Handling / CAD Event Creation Premises Hazards and Previous History Display historical incident information based on a configurable geo-area range pre-set by the systems administrator, and according to local SOP. HxGN OnCall Dispatch | Viewer Page 14 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 100 Call Handling / CAD Event Creation Premises Hazards and Previous History Display historical incident information based on a configurable date range pre-set AND geo-area range pre-set by the systems administrator, and according to local SOP. HxGN OnCall Dispatch | Viewer 101 Call Handling / CAD Event Creation Premises Hazards and Previous History Be capable of storing information of interest to responders including, but not limited to: o Hazardous materials stored at the location o Firearms kept at the location o Information specific to individuals at the location, including, but not limited to: Warrants on file Serious medical information Impairments Potential dangers to first responders o Information specific to the address, including, but not limited to: Entry codes Knox Box information HxGN OnCall Dispatch | Viewer 102 Call Handling / CAD Event Creation CAD Event Creation Support the creation of a CFS event with a bare minimum amount of information to trigger the dispatch of resources when the matter is urgent. This includes the location of the event and the event type. o It must be possible to update CFS event as additional information is gathered from the reporting party. HxGN OnCall Dispatch | Viewer 103 Call Handling / CAD Event Creation CAD Event Creation Support the creation of new CFS events—in communications centers where separate call takers and radio dispatchers are employed—by either call takers or dispatchers depending on the source of the event information. HxGN OnCall Dispatch | Viewer Page 15 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 105 Call Handling / CAD Event Creation CAD Event Creation Spawn a copy of the CFS event—in agencies where multiple agencies and/or services are dispatched, or when an interface to another CAD system exists—for the additional agencies with a unique incident/event number for each; however, all copies of the CFS event be linked to each other so CAD users can ascertain that they are a single CAD event. HxGN OnCall Dispatch | Viewer 106 Call Handling / CAD Event Creation Determining Response Agency and Service Area Store all service agency and response area assignments in CFS events and the system’s audit log file. HxGN OnCall Dispatch | Viewer 107 Call Handling / CAD Event Creation Determining Response Agency and Service Area Validate the location of new a CAD event against the system’s geofile to verify the location is within the service area handled by the PSAP. HxGN OnCall Dispatch | Viewer 108 Call Handling / CAD Event Creation Determining Response Agency and Service Area Identify the new CAD event’s location and nature code, and use the system’s geofile to identify the appropriate service agencies that need to handle the event. HxGN OnCall Dispatch | Viewer 109 Call Handling / CAD Event Creation Determining Response Agency and Service Area Identify the appropriate service agencies to handle a CAD event, and use the system’s geofile to determine the appropriate response area(s) within each agency’s service area. HxGN OnCall Dispatch | Viewer Page 16 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 110 Call Handling / CAD Event Creation Determining Response Agency and Service Area Provide a method for CAD users to manually enter/assign the appropriate service agencies and response areas to CAD events if the CAD event’s location cannot be validated against the system’s geofile or if the validation process results in the assignment of an improper service agency or response area. HxGN OnCall Dispatch | Viewer 111 Call Handling / CAD Event Creation Determining Response Agency and Service Area Use the service agency and response to notify the appropriate dispatchers that they must process a CAD event. HxGN OnCall Dispatch | Viewer 112 Call Handling / CAD Event Creation Alarm Processing Provide a feature where the location of an alarm can be retrieved by the number displayed on the enunciator panel, if the PSAP monitors alarm enunciator panels. HxGN OnCall Dispatch | Viewer 116 Call Handling / CAD Event Creation Alarm Processing Spawn a copy of the CFS event to other agencies, if applicable. HxGN OnCall Dispatch | Viewer 120 Call Handling / CAD Event Creation CAD Event Routing Examine the location, event type and response plans (when dedicated dispatch positions are in operation) to route the CFS event to one or more dispatch positions as the CFS event entry is being performed by a call taker. HxGN OnCall Dispatch | Viewer 122 Call Handling / CAD Event Creation CAD Event Routing Display the dispatch position’s pending event queue in priority order and in chronological order once the CFS event has been routed by the CAD system. HxGN OnCall Dispatch | Viewer 123 Call Handling / CAD Event Creation Ability to Route to a “Decision Dispatcher” Be capable of routing a CFS to a decision dispatch position that will dispatch resources.HxGN OnCall Dispatch | Viewer Page 17 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 124 Call Handling / CAD Event Creation Ability to Route to a “Decision Dispatcher” Route the event (once the decision dispatcher has dispatched the event to the appropriate resources) to another dispatcher that takes responsibility for the event from that point forward. HxGN OnCall Dispatch | Essentials 125 Call Handling / CAD Event Creation Ability to Route to a “Decision Dispatcher” Be able to route CAD events to the appropriate decision dispatcher (when multiple “decision dispatchers” exist) based on parameters configured by the system administrator. HxGN OnCall Dispatch | Essentials 126 Call Handling / CAD Event Creation Ability to Route to a “Decision Dispatcher” Be able to route to the appropriate radio dispatcher (when multiple radio dispatchers exist to handle the remainder of the event) based on the actions by the decision dispatcher and/or predicated by event type and location. HxGN OnCall Dispatch | Essentials 127 Dispatch Support Run Cards / Response Plans Allow for dynamic and fixed/static response plans.HxGN OnCall Dispatch | Essentials 128 Dispatch Support Run Cards / Response Plans Allow for unlimited alarm levels.HxGN OnCall Dispatch | Essentials 129 Dispatch Support Run Cards / Response Plans Allow for the use of primary and secondary capabilities. HxGN OnCall Dispatch | Essentials 130 Dispatch Support Run Cards / Response Plans Allow for assignment to be by resource type, capability and equipment (e.g. thermal imager).HxGN OnCall Dispatch | Essentials 131 Dispatch Support Run Cards / Response Plans Allow for the use of personnel capabilities (e.g. personnel with Spanish speaking ability).HxGN OnCall Dispatch | Essentials Page 18 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 132 Dispatch Support Run Cards / Response Plans Allow for the use of resource groups made up of individual units [e.g. a Hazmat (hazardous material) group made up of several units and dispatched as a single “Hazmat team” (i.e. single unit)]. HxGN OnCall Dispatch | Essentials 133 Dispatch Support Run Cards / Response Plans Allow for the use of premises-based or address- based response plans. HxGN OnCall Dispatch | Essentials 134 Dispatch Support Run Cards / Response Plans Allow for the use of AVL systems for selecting units. HxGN OnCall Dispatch | Essentials 135 Dispatch Support Run Cards / Response Plans Support multiple agency response plans.HxGN OnCall Dispatch | Essentials 136 Dispatch Support Run Cards / Response Plans Allow for unit assignment based on time or distance to the incident. HxGN OnCall Dispatch | Essentials 137 Dispatch Support Run Cards / Response Plans Allow for adjustable plans that are based on time of day or day of week. HxGN OnCall Dispatch | Essentials 138 Dispatch Support Adjustable Dispatch Levels Allow for adjustable dispatch levels.HxGN OnCall Dispatch | Administrator 139 Dispatch Support Adjustable Dispatch Levels Allow for an unlimited number of dispatch levels.HxGN OnCall Dispatch | Administrator 140 Dispatch Support Adjustable Dispatch Levels Allow for a user-defined naming convention for the dispatch levels. HxGN OnCall Dispatch | Administrator 141 Dispatch Support Adjustable Dispatch Levels Enable adjustable dispatch levels to be individually activated (e.g. a fire response plan would change to Level 2, and an ALS response would change to a Level 3, or all plans could change to a defined level). HxGN OnCall Dispatch | Administrator 142 Dispatch Support Adjustable Dispatch Levels Have an easily viewable method to review current dispatch levels. HxGN OnCall Dispatch | Administrator Page 19 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 143 Dispatch Support Adjustable Dispatch Levels Alert the dispatcher when the required number or type of units are not dispatched (e.g. one police unit to a domestic call instead of two, or two fire engines to a commercial fire instead of four). HxGN OnCall Dispatch | Advantage 144 Dispatch Support Additional Attributes Provide a means to assign multiple attributes to units. HxGN OnCall Dispatch | Viewer 145 Dispatch Support Additional Attributes Provide a means to assign multiple attributes to personnel. HxGN OnCall Dispatch | Viewer 146 Dispatch Support Additional Attributes Provide a means to search for units or personnel attributes on the fly. HxGN OnCall Dispatch | Viewer 147 Dispatch Support Additional Attributes Provide a means to assign resources to multiple units (i.e. shared crews). HxGN OnCall Dispatch | Viewer 162 Dispatch Support Unit Rotation (Unit Load Balancing) Allow for customization based on the needs of the agency. (e.g. incident address, response type, assignment, resources required, unit-on-task-time, unit utilization, time of day and proximity if you have multiple available companies with the capability required). HxGN OnCall Dispatch | Administrator 163 Dispatch Support Unit Rotation (Unit Load Balancing) Make unit response recommendations based on the configuration of rules defined by the agency.HxGN OnCall Dispatch | Essentials 164 Dispatch Support Conditional Availability of Apparatus Have the capability to code the conditional availability of units. HxGN OnCall Dispatch | Essentials 165 Dispatch Support Conditional Availability of Apparatus Be able to prioritize an incident and recommend the type of units based on the prioritization of that event and the current status of the unit. HxGN OnCall Dispatch | Essentials 166 Dispatch Support Conditional Availability of Apparatus Have a unit recommendation feature with the flexibility to be overridden by the dispatcher.HxGN OnCall Dispatch | Essentials Page 20 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 167 Dispatch Support Special Dispatch Areas Define special dispatch area types and assign each a unique identifier. HxGN OnCall Dispatch | Administrator 168 Dispatch Support Special Dispatch Areas Assign a special dispatch area type to CAD geofile addresses, intersections, and blocks for each service agency (e.g. law enforcement, fire, EMS, utility). HxGN OnCall Dispatch | Administrator 169 Dispatch Support Special Dispatch Areas Specify a non-standard response for a location identified with a special dispatch area type.HxGN OnCall Dispatch | Administrator 170 Dispatch Support Special Dispatch Areas Define non-standard responses as being applicable only during certain days of the week and/or times of the day (i.e. window for utilization). HxGN OnCall Dispatch | Administrator 171 Dispatch Support Special Dispatch Areas Provide the capability that if one or more windows are defined but none of them are applicable, then the standard response is employed. HxGN OnCall Dispatch | Administrator 172 Dispatch Support Emergency Medical Dispatch / Incident Triage Include (or allow for the installation of) an EMD or incident triage program. HxGN OnCall Dispatch | Call- Taker Page 21 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 173 Dispatch Support Emergency Medical Dispatch / Incident Triage The CAD system or EMD or incident triage program: Allow for customization based on the needs of the agency (e.g. medical direction, operations). • guide or prompt the call taker through defined forms based on the information provided by the caller. • assist the call taker in identifying the: o Type of incident (i.e. law enforcement, fire, EMS, multi-agency) o Resources needed [e.g. law enforcement, ALS/BLS, engine(s), extrication] o Level of response (e.g. Alpha, Bravo, Charlie, Delta or priority) HxGN OnCall Dispatch | ProQA Interface Page 22 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 174 Dispatch Support Emergency Medical Dispatch / Incident Triage The CAD system or EMD or incident triage program: Provide the capability to allow a unit to be dispatched to the incident as soon as the address is confirmed and the nature of the incident is determined. • prompt the call taker to provide pre-arrival instructions to the caller or responding unit(s). • recommend a change, based on the information obtained and entered into the program, in: o Response priority (e.g. upgrade or downgrade to emergent, non-emergent) o Resources required (i.e. law enforcement, fire, EMS) HxGN OnCall Dispatch | ProQA Interface 175 Dispatch Support Be On the Look-Out / Attempt to Locate Support creation and distribution of any BOLO entered into the system. HxGN OnCall Dispatch | Advantage 176 Dispatch Support Be On the Look-Out / Attempt to Locate Provide a BOLO structure to include all necessary information such as the nature of the BOLO, priority, date, range of effectiveness, subject and/or vehicle information, hazard information, and contact information. HxGN OnCall Dispatch | Advantage 177 Dispatch Support Be On the Look-Out / Attempt to Locate Allow narrative fields for additional information HxGN OnCall Dispatch | Advantage 178 Dispatch Support Be On the Look-Out / Attempt to Locate Provide the means for BOLO information to be easily searchable, printable, and have the ability to automatically populate on an incident sheet referencing any particular name, address, or vehicle information. HxGN OnCall Dispatch | Viewer Page 23 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 179 Dispatch Support Be On the Look-Out / Attempt to Locate Flag the field (automatically) with configurable visual and audible alerts. HxGN OnCall Dispatch | Advantage 180 Dispatch Support Be On the Look-Out / Attempt to Locate Support a workflow record for initial BOLO creation and any additional edits. HxGN OnCall Dispatch | Advantage 181 Dispatch Support Dispatch Units Have the optional ability to assign one incident number to each unit responding to the incident.HxGN OnCall Dispatch | Essentials 182 Dispatch Support Dispatch Units Assign an incident number to each agency responding to the incident. HxGN OnCall Dispatch | Viewer 184 Dispatch Support Dispatch Units Capture every time stamp associated with each unit’s response and status change related to the incident. HxGN OnCall Dispatch | Essentials 185 Dispatch Support Dispatch Units Capture all status changes and their times for statistical and research purposes(e.g. out of service versus in service to calculate “lost unit hours”). HxGN OnCall Dispatch | Essentials 186 Dispatch Support Resource Alerting Alert via MDC.HxGN OnCall Dispatch | Mobile Unit 187 Dispatch Support Resource Alerting Generate (automatically) information appropriate for use with “rip and run” printers and/or alphanumeric pager devices when units are dispatched or on demand by a dispatcher. HxGN OnCall Dispatch | Fire Station Printing 188 Dispatch Support Resource Alerting Generate (automatically) information appropriate for use with email and/or SMS sent to a mobile device when units are dispatched or on demand by a dispatcher. HxGN OnCall Dispatch | Notifications Page 24 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 191 Dispatch Support Resource Alerting Support “rip and run” printing via IP network using protocols, such as Internet Printing Protocol (IPP), Line Printer Daemon (LPD), and Hewlett-Packard Printer Job Language (PJL), and via facsimile transmission based on operational requirements. HxGN OnCall Dispatch | Fire Station Printing 192 Dispatch Support Resource Alerting Support alphanumeric paging via TAP, WCTP, SMTP, and SNPP. HxGN OnCall Dispatch | Notifications *TAP not currently supported 193 Dispatch Support Resource Alerting Support sending SMS messages either directly via cellular modem or using a common carrier’s SMTP interface. HxGN OnCall Dispatch | Notifications 197 Resource / Unit Management Staffed vs Unstaffed Units Provide the ability to dynamically document that a unit is staffed or unstaffed before or after it is assigned to an incident. HxGN OnCall Dispatch | Essentials 198 Resource / Unit Management Cross-Staffing / Crew Counting / Shared Staffing / Contingent Staffing Take, based on a single shared crew assigned to multiple pieces of apparatus, the remaining piece(s) of apparatus out of service, when one piece of apparatus is assigned to an event. HxGN OnCall Dispatch | Essentials 202 Resource / Unit Management Additional Unit Status Include the various statuses needed for unit readiness or during patient care. HxGN OnCall Dispatch | Essentials 203 Resource / Unit Management Additional Unit Status Add parameters to the incident that relate to the response priority (i.e. lights and siren or non- emergency mode). HxGN OnCall Dispatch | Essentials 204 Resource / Unit Management Additional Unit Status Show if a unit is BLS or ALS.HxGN OnCall Dispatch | Essentials 205 Resource / Unit Management Strike Team / Task Force Designations Allow the dispatcher to group units into a task force or strike team (i.e. virtual unit). HxGN OnCall Dispatch | Essentials Page 25 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 206 Resource / Unit Management Strike Team / Task Force Designations Track (individually) all resources in the system’s database, and also make a record that the resources were part of a virtual unit so the virtual unit response data can be easily retrieved. HxGN OnCall Dispatch | Essentials 207 Resource / Unit Management Rostering Provide the capability to create rosters (i.e. assign personnel to a vehicle or position to facilitate on/off duty transactions). HxGN OnCall Dispatch | Administrator 208 Resource / Unit Management Rostering Allow the dispatcher to adjust the rosters and/or assignments (i.e. on-the-fly, during shifts, and above normal complements). HxGN OnCall Dispatch | Essentials 212 Resource / Unit Management Mileage Tracking Capture beginning and ending mileage for individual transports. HxGN OnCall Dispatch | Advantage 213 Resource / Unit Management Mileage Tracking Provide a method of integration with an AVL system for increased accuracy and efficiency.HxGN OnCall Dispatch | Advantage 214 Resource / Unit Management Mileage Tracking Use GIS/mapping to supplement driving directions based on shortest route beginning and ending address locations, with regard to environmental factors such as time of day, weather conditions, train schedules, and road/bridge blockages. HxGN OnCall Dispatch | Viewer 215 Resource / Unit Management Mileage Tracking Provide the ability for an authorized user to manually override an entry by a dispatcher or supervisor. HxGN OnCall Dispatch | Advantage 217 Resource / Unit Management Mileage Tracking Record the overridden information in an audit log.HxGN OnCall Dispatch | Advantage 218 Resource / Unit Management Hydrant Location and Status Display hydrant locations and related info on the map. HxGN OnCall Dispatch | Viewer 219 Resource / Unit Management Hydrant Location and Status Record, and display, with hydrant information, alternative water sources (e.g. ponds, creeks).HxGN OnCall Dispatch | Essentials Page 26 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 220 Resource / Unit Management Additional Unit Dispositions Enable the CAD administrator to define a list of available unit dispositions. HxGN OnCall Dispatch | Administrator 221 Resource / Unit Management Additional Unit Dispositions Require a disposition based on call type and jurisdiction. HxGN OnCall Dispatch | Administrator 222 Resource / Unit Management Additional Unit Dispositions Enable assisting units to report one or more dispositions when agency policy requires a disposition from each unit assigned to a CFS. HxGN OnCall Dispatch | Essentials 223 Resource / Unit Management Additional Unit Dispositions Facilitate the recording of dispositions by the dispatcher or the field unit if MDC- equipped. HxGN OnCall Dispatch | Essentials 224 Resource / Unit Management Additional Unit Dispositions Include a multiplication factor for each disposition when multiple instances of the same disposition apply (e.g. 10 traffic summons written could be recorded using a single disposition of “traffic summons issued,” times 10). HxGN OnCall Dispatch | Essentials 225 Resource / Unit Management Additional Unit Dispositions The CAD system NOT require a disposition if agency policy does not require the use of dispositions. HxGN OnCall Dispatch | Essentials 228 Resource / Unit Management Geo-fencing Provide geo-fence creation tools that allow the use of polygons, circles, ellipses, and rectangles.HxGN OnCall Dispatch | Advantage 229 Resource / Unit Management Geo-fencing Display details about a resource to aid in identification, location and purpose. HxGN OnCall Dispatch | Advantage 230 Resource / Unit Management Geo-fencing Facilitate the creation of multiple, coexisting, overlapping geo-fences. HxGN OnCall Dispatch | Advantage 231 Resource / Unit Management Geo-fencing Support unique geo-fence names and each geo- fence be visually distinct. HxGN OnCall Dispatch | Advantage 232 Resource / Unit Management Geo-fencing Generate an alert whenever a vehicle or resource enters and/or exits a geo-fence. HxGN OnCall Dispatch | Viewer Page 27 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 233 Resource / Unit Management Geo-fencing Include alerts that consist of: o Unique visual and audible identification o Resource identification o Geo-fence Identification o Current resource position o Timestamps of entry and exit of geo-fence areas o Ability to clear alerts and history from view while maintaining historic records as needed HxGN OnCall Dispatch | Viewer 234 Resource / Unit Management Geo-fencing Be able to alert personnel though technologies such as text messaging or email.GN OnCall Dispatch | Notificatio 235 Resource / Unit Management Geo-fencing Provide the ability to create, manage and record geo-fence areas to track the entry and/or exit of GIS based resources. HxGN OnCall Dispatch | Advantage 236 Resource / Unit Management Geo-fencing Provide informative and manageable alerts to appropriate personnel through visual and audible representation. HxGN OnCall Dispatch | Viewer 237 Resource / Unit Management Station Dispatch Provide the capability to dispatch a fire and/or EMS station to an incident regardless of the number of units or personnel that station has assigned to it or on duty. HxGN OnCall Dispatch | Essentials 239 Resource / Unit Management Vehicle / Unit Change Account for the number of personnel currently staffed on the unit. HxGN OnCall Dispatch | Viewer 240 Resource / Unit Management Vehicle / Unit Change Allow system supervisors and other authorized users the ability to modify vehicle and resource capabilities, as required, without adversely impacting the system (i.e. without having to shut the system down). HxGN OnCall Dispatch | Viewer Page 28 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 241 Resource / Unit Management Vehicle / Unit Change Allow easy modifications to unit crew capabilities to accommodate frequent changes throughout the day. HxGN OnCall Dispatch | Viewer 242 Resource / Unit Management Vehicle / Unit Change Track Units having multiple units with multiple capabilities, and attributes should be reflected as multiple types (e.g. a Quint, pumper, or ladder). HxGN OnCall Dispatch | Essentials 243 Resource / Unit Management Vehicle / Unit Change Recommend resources based on the appropriate type (e.g. a “Quint” type fire apparatus may be recommended as either a pumper or a ladder truck). HxGN OnCall Dispatch | Essentials 244 Resource / Unit Management Vehicle / Unit Change Allow the dynamic entry of personnel staffing specific units/apparatus. HxGN OnCall Dispatch | Viewer 245 Resource / Unit Management Vehicle / Unit Change Allow the staffing module to be accessed from the field by authorized users to dynamically reflect changing assignments. HxGN OnCall Dispatch | Viewer 246 Resource / Unit Management Vehicle / Unit Change Allow for tracking vehicle ID in addition to unit radio call sign (e.g. a given vehicle may be referred to as “Unit 1” one day and a different vehicle the next day. HxGN OnCall Dispatch | Viewer 247 Resource / Unit Management Automatic Driving Directions / Routing Present the destination address visually for validation and acceptance. HxGN OnCall Dispatch | Viewer 248 Resource / Unit Management Automatic Driving Directions / Routing Provide a route that considers current impedances (e.g. road closures, road construction, accidents, disable vehicles) HxGN OnCall Dispatch | Essentials 249 Resource / Unit Management Automatic Driving Directions / Routing Provide a route that considers speed limits, traffic lights, stop signs, and other traffic control variables. HxGN OnCall Dispatch | Essentials 250 Resource / Unit Management Automatic Driving Directions / Routing Provide a visual map that presents the entire route. HxGN OnCall Dispatch | Essentials Page 29 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 251 Resource / Unit Management Automatic Driving Directions / Routing Provide a visual map that centers the unit and presents a configurable radius around the unit (i.e. feet, miles, meters), and provides turn-by-turn navigation. HxGN OnCall Dispatch | Mobile Unit *configurable radius not provided 252 Resource / Unit Management Automatic Driving Directions / Routing Provide consistent route re-evaluation, and visually present alternate routes based on estimated drive time without interfering with current route. HxGN OnCall Dispatch | Mobile Unit *Re-routing is provided, but alternate routes are not presented 253 Resource / Unit Management Automatic Driving Directions / Routing Provide a directions list from unit current location to destination. HxGN OnCall Dispatch | Mobile Unit 254 Resource / Unit Management Automatic Driving Directions / Routing Account for one-way roads, highway overpasses, and other considerations that impact safety.HxGN OnCall Dispatch | Essentials 255 Resource / Unit Management Automatic Driving Directions / Routing Include traffic weights that are considerate of time- of-day, day-of-week, and day- of-year to account for rush hour and holiday congestion. HxGN OnCall Dispatch | Essentials 256 Resource / Unit Management Automatic Driving Directions / Routing Prevent audible alerts from interfering from other system notifications that may impact unit safety.HxGN OnCall Dispatch | Mobile Unit 257 Resource / Unit Management Automatic Driving Directions / Routing Allow for tracking of train schedules/locations that result in blocked crossings.HxGN OnCall Dispatch | Viewer 258 Resource / Unit Management Automatic Driving Directions / Routing Allow for tracking of train AVL data to factor blocked crossings. HxGN OnCall Dispatch | Viewer 259 Resource / Unit Management Bypassed Units Alert (automatically) the dispatcher in the case of a unit becoming available that is closer to a CFS in which the currently assigned unit is still in route and farther away. HxGN OnCall Dispatch | Resource Management Page 30 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 260 Resource / Unit Management Post-Dispatch Response Re- evaluation Notify the dispatcher when a response reevaluation is appropriate based on AVL data (i.e. units that should be considered for a CFS and units that could be cancelled if those under consideration are assigned to the event). HxGN OnCall Dispatch | Resource Management 261 Call / Incident / Event Management Display of Incident / Event Data Display CFS event data on the CAD monitor after being selected by the dispatcher. All CFS event data be accessible to the dispatcher. HxGN OnCall Dispatch | Viewer 262 Call / Incident / Event Management Display of Incident / Event Data Enable Windows tabs to be used to allow the dispatcher to select supplemental history about the incident (e.g. premises history, past event history, hazards, persons of interest) HxGN OnCall Dispatch | Viewer 263 Call / Incident / Event Management Display of Incident / Event Data Display (automatically) updates to the CFS event for the dispatcher. HxGN OnCall Dispatch | Viewer 264 Call / Incident / Event Management Display of Incident / Event Data Provide updated information that is easily discernible from the previously read data (e.g. newest information on the top, different font/color text). HxGN OnCall Dispatch | Viewer 265 Call / Incident / Event Management Display of Incident / Event Data Present an audible and/or visual indication to the dispatcher when a CFS event is updated by another source such as a call taker, another dispatcher, or a field unit. HxGN OnCall Dispatch | Viewer 266 Call / Incident / Event Management Display of Incident / Event Data Provide, upon receipt of an update, a method of ease, such as an ‘Update’ button, for the dispatcher to retrieve the CFS event that has been updated. HxGN OnCall Dispatch | Viewer Page 31 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 267 Call / Incident / Event Management Display of Incident / Event Data Remove CFS events as they are closed by the dispatcher from the CFS event display, without additional interaction from the dispatcher. HxGN OnCall Dispatch | Viewer 268 Call / Incident / Event Management Update Incident Status Provide the capability to record supplemental information updates in the CFS event as it is received from callers, field resources and other sources. HxGN OnCall Dispatch | Viewer 269 Call / Incident / Event Management Update Incident Status Retain a copy of any information updated prior to the update for audit purposes. HxGN OnCall Dispatch | Viewer 270 Call / Incident / Event Management Update Incident Status Provide a method to update the actual incident type versus the reported incident type.HxGN OnCall Dispatch | Viewer 271 Call / Incident / Event Management Dispatch Resource Decision Recommend resources, when the resource requirement is changed, based upon agency defined procedures, workload balancing, unit capability, and proximity of the resources. HxGN OnCall Dispatch | Essentials 272 Call / Incident / Event Management Update Assigned Resources Recommend readjusted resources that meet the requirements of the incident. HxGN OnCall Dispatch | Essentials 273 Call / Incident / Event Management Update Assigned Resources Record the modifications to the CFS event when changed by the dispatcher. HxGN OnCall Dispatch | Viewer 274 Call / Incident / Event Management Update Assigned Resources Record any changes to assigned resources as an update to the CFS event. HxGN OnCall Dispatch | Essentials 275 Call / Incident / Event Management Update Assigned Resources Provide the capability to recommend additional resources based on response plans and/or local policies. HxGN OnCall Dispatch | Essentials 276 Call / Incident / Event Management Update Supplemental Resources Tracking Allow the ability to divide the response area into multiple zones, based on user- defined criteria, to ensure a quick response to the request. HxGN OnCall Dispatch | Essentials Page 32 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 277 Call / Incident / Event Management Update Supplemental Resources Tracking Make recommendations for resources to prevent any one entity from being favored. HxGN OnCall Dispatch | Essentials 278 Call / Incident / Event Management Update Supplemental Resources Tracking Allow cancellation of or by-passing the recommendation, returning the skipped company to be placed back in the rotation either at the bottom or top of the rotation, depending on the circumstances. HxGN OnCall Dispatch | Essentials 279 Call / Incident / Event Management Update Supplemental Resources Tracking Provide the ability to skip a suggested resource, capturing the reason for the exception and placing the resource either back at the top of the queue or at the bottom, based on the reasoning. HxGN OnCall Dispatch | Essentials 280 Call / Incident / Event Management Update Supplemental Resources Tracking Provide the ability to create and maintain rotating and non-rotating service provider information (i.e. towing companies). HxGN OnCall Dispatch | Essentials 281 Call / Incident / Event Management Assign Units Allow the assignment of units by using drag-and- drop and point-and-click pull- down menus.HxGN OnCall Dispatch | Essentials 282 Call / Incident / Event Management Assign Units Re-queue the CFS that has had all units removed, but has not been handled. HxGN OnCall Dispatch | Essentials 283 Call / Incident / Event Management Assign Units Recommend a unit that is unavailable only if SOP permits units to be pre-empted for a higher priority event HxGN OnCall Dispatch | Essentials 284 Call / Incident / Event Management Assign Units Provide the ability to assign one or more units to an incident with a single command. HxGN OnCall Dispatch | Essentials 285 Call / Incident / Event Management Assign Units Provide the ability to dynamically, and without user intervention, change the unit recommendation if relevant incident information changes (i.e. type, location, alarm level). HxGN OnCall Dispatch | Essentials 286 Call / Incident / Event Management Assign Units Provide the ability to notify users that the unit recommendation has changed. HxGN OnCall Dispatch | Resource Management Page 33 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 287 Call / Incident / Event Management Assign Units Provide the ability to cancel a unit from an assignment: If the cancelled unit is the only unit assigned, then the CFS will be returned to the pending event queue. HxGN OnCall Dispatch | Essentials 288 Call / Incident / Event Management Assign Units Provide the ability to assign or add multiple units to a CFS event with a single command. HxGN OnCall Dispatch | Essentials 289 Call / Incident / Event Management Assign Units Provide the ability to assign a single unit to multiple CFS events. HxGN OnCall Dispatch | Essentials 290 Call / Incident / Event Management Assign Units Provide the ability to hold a CFS event for a specific unit. HxGN OnCall Dispatch | Essentials 291 Call / Incident / Event Management Assign Units Allow the dispatcher to override the system recommended units and assign other units. HxGN OnCall Dispatch | Essentials 292 Call / Incident / Event Management Update Incident Data Log the following information for all entries into the CFS event: date, time, user ID (or note if action was system generated), position (terminal) ID, action performed, and any notes associated with action. HxGN OnCall Dispatch | Viewer 293 Call / Incident / Event Management Update Incident Data Display additional CFS event information to the dispatcher for action. HxGN OnCall Dispatch | Viewer 294 Call / Incident / Event Management Update Incident Data Allow, at any time, additional incident information to be added to the CFS event, both prior to and after closing the incident. HxGN OnCall Dispatch | Viewer 295 Call / Incident / Event Management Update Incident Data Allow the user to display the added comments in reverse chronological order. HxGN OnCall Dispatch | Viewer 296 Call / Incident / Event Management Update Incident Data Provide the user the option of specifying the CFS event to update by entering the call sign of any assigned unit or by entering the incident number. HxGN OnCall Dispatch | Viewer 297 Call / Incident / Event Management Update Incident Data Permit multiple users, including MDC-equipped field resources, the ability to simultaneously update information to the CFS event. HxGN OnCall Dispatch | Viewer Page 34 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 298 Call / Incident / Event Management Update Incident Data Provide controls when two or more CAD users attempt to update the same field in the CFS event o For example, in the event that User A is saving modifications to a field, and that field has been modified by another user since User A retrieved the CFS event, the application notify User A that the field that is being modified has been changed since User A retrieved the record and confirm that User A wants to continue with the update. HxGN OnCall Dispatch | Viewer 299 Call / Incident / Event Management Update Incident Data Provide the ability for one or more CAD users to simultaneously add incident information to an active or closed CFS event. HxGN OnCall Dispatch | Viewer 300 Call / Incident / Event Management Update Incident Data Notify the entering party that the incident being updated has been closed. This will allow the entering party to reopen the incident for re- queuing to dispatch if necessary. HxGN OnCall Dispatch | Viewer 301 Call / Incident / Event Management Update Incident Data Provide the ability to update the CFS event by specifying the incident/event number or the call sign of assigned units. HxGN OnCall Dispatch | Viewer 302 Call / Incident / Event Management Assign Records Management System Incident / Case Number Facilitate an interface to an RMS to allow the transfer and tracking of incident data.HxGN OnCall Dispatch | Viewer 303 Call / Incident / Event Management Assign Records Management System Incident / Case Number Provide the ability to transfer the incident data to the RMS at a set time (incident closure) or at dispatcher discretion based upon the field unit’s needs. HxGN OnCall Dispatch | Viewer Page 35 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 304 Call / Incident / Event Management Assign Records Management System Incident / Case Number Coordinate the assignment of RMS incident/case numbers through a jointly used, shared list by the RMS and CAD system or through a list maintained in the CAD system. HxGN OnCall Dispatch | Viewer 305 Call / Incident / Event Management Assign Records Management System Incident / Case Number Provide the ability for the dispatcher to retrieve the RMS incident number at any point during the event or after the incident has been closed. HxGN OnCall Dispatch | Viewer 306 Call / Incident / Event Management Transfer Basic Incident Data to the Records Management System Provide the ability to automatically transfer CAD system CFS event data relating to an incident to an RMS for use by the agency. HxGN OnCall Dispatch | Viewer 307 Call / Incident / Event Management Transfer Basic Incident Data to the Records Management System Provide the ability to transfer data prior to the normal chronological transfer point to provide the public safety responders with an RMS incident number when needed, and if this method is required to retrieve an RMS incident number. HxGN OnCall Dispatch | Viewer 308 Call / Incident / Event Management Display Additional Incident Data Notify the appropriate CAD users via visual and/or audible indication when information is added or changed to a CFS event. HxGN OnCall Dispatch | Viewer 309 Call / Incident / Event Management Display Additional Incident Data Provide the ability to visually differentiate text notes in the CFS event added by different operators for the same incident (i.e. color and/or CAD user identification). HxGN OnCall Dispatch | Viewer 310 Call / Incident / Event Management Display Additional Incident Data Display additional CFS event data with the newest information displayed first. HxGN OnCall Dispatch | Viewer 311 Call / Incident / Event Management Display Additional Incident Data Display additional CFS event data with the newest information displayed in differently formatted text (e.g. color, font, formatting, such as bold, italics). HxGN OnCall Dispatch | Viewer *limited highlighting of changed data at the field level currently Page 36 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 312 Call / Incident / Event Management Display Additional Incident Data Provide the ability to view all additional CFS event data at one time. HxGN OnCall Dispatch | Viewer 313 Call / Incident / Event Management Display Additional Incident Data Provide the ability to automatically notify users monitoring or displaying the CFS event that information has changed. HxGN OnCall Dispatch | Viewer 314 Call / Incident / Event Management Display Additional Incident Data Provide the ability to dynamically, and without user intervention, display changes to a CFS event as they occur based on assigned user rights. HxGN OnCall Dispatch | Viewer 315 Call / Incident / Event Management Reopen Incident Ensure all changes to the CFS event are time/date stamped. HxGN OnCall Dispatch | Viewer 316 Call / Incident / Event Management Reopen Incident Notify the CAD user attempting to add information to a closed CFS event that the event is closed.HxGN OnCall Dispatch | Viewer 317 Call / Incident / Event Management Reopen Incident Provide the ability to add comments to a CFS event without reopening the original CFS event.HxGN OnCall Dispatch | Viewer 318 Call / Incident / Event Management Reopen Incident Provide the ability to reopen a CFS event by incident number, location, or unit ID. HxGN OnCall Dispatch | Viewer 319 Call / Incident / Event Management Reopen Incident Provide the ability to reopen closed CFS events and assign units. HxGN OnCall Dispatch | Viewer 320 Call / Incident / Event Management Reopen Incident Provide the ability to open a closed CFS event as a new CFS using information from the old CFS event, but with new time stamps. HxGN OnCall Dispatch | Advantage 321 Call / Incident / Event Management Add Destination Locations Have the ability to accurately track the destination of all units assigned to a particular incident within the CFS event, and to allow these locations and activities to change throughout the incident HxGN OnCall Dispatch | Advantage Page 37 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 323 Call / Incident / Event Management Patient Tracking Have the ability to track EMS patients from the scene to their destination or disposition. o This include the ability to capture patient identifying information. HxGN OnCall Dispatch | Viewer 324 Call / Incident / Event Management Patient Tracking Meet Federal HIPAA (Health Information Portability and Accountability Act) requirements for data security where appropriate. HxGN OnCall Dispatch | Viewer 326 Call / Incident / Event Management Linking an Audio File to a CAD Event Provide the ability to record multiple types of incoming media types and associate them with the CAD CFS event record for easy retrieval. HxGN OnCall Dispatch | Viewer 328 Call / Incident / Event Management Linking an Audio File to a CAD Event Allow the user to open a window to support streaming multimedia feeds (i.e.video and audio).HxGN OnCall Dispatch | Video Responder 329 Call / Incident / Event Management Linking an Audio File to a CAD Event Allow users to start, stop, pause, and rewind the multimedia feed.HxGN OnCall Dispatch | Video Responder 330 Call / Incident / Event Management Linking an Audio File to a CAD Event Allow for adequate start/stop capabilities. o If the multimedia feed is stopped or paused for less than 30 seconds and then restarted, then the multimedia feed start where the stop or pause occurred. o Stopping or pausing the data stream for up to 30 seconds not cause the loss of the data. o There be at least a 30-second cache of the multimedia data stream. HxGN OnCall Dispatch | Viewer *Audio file can be attached to the CAD event, but record and play capability are provided by external application Page 38 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 331 Call / Incident / Event Management Linking an Audio File to a CAD Event Allow multimedia data to be recorded into CFS event history; or, otherwise allow the recording of streaming media to a separate data repository with appropriate information that would allow the users to easily match multimedia files with specific incidents. HxGN OnCall Dispatch | Viewer 332 Call / Incident / Event Management Linking an Audio File to a CAD Event Allow authorized users to start/stop the recording process by the use of graphic command buttons or function keys. HxGN OnCall Dispatch | Video Responder Advantage 333 Call / Incident / Event Management Linking an Audio File to a CAD Event Support the resizing of the multimedia window and the auto-resizing of the video display portion of the window. HxGN OnCall Dispatch | Viewer 334 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Allow a dispatcher to hold or stack events to a busy unit, as well as units that are in-service. o If a unit is on an assignment, when the unit clears its assignment, then the system notify the dispatcher the unit is available. HxGN OnCall Dispatch | Essentials 335 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Provide the agency a method to define what events can be held. HxGN OnCall Dispatch | Essentials 336 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Allow several events to be placed on hold for a single unit. HxGN OnCall Dispatch | Essentials 337 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Allow a CFS event to be held for a unit that is not yet logged on. HxGN OnCall Dispatch | Essentials 338 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Record in the history of the CFS event when an event is placed on hold. HxGN OnCall Dispatch | Essentials 339 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Apply timers to all held CFS events and alert the dispatcher when a held event has exceeded the allowable time in a held status. HxGN OnCall Dispatch | Essentials Page 39 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 340 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit Provide dispatchers with the ability to pre-empt a unit and dispatch the unit to another event. o If all units are removed from the original event, then it be placed in the pending CFS events monitor. HxGN OnCall Dispatch | Essentials 341 Call / Incident / Event Management Multiple Simultaneous Incidents to Single Unit NOT limit the ability of the dispatcher to assign another unit to the incident or for field units to self-dispatch (assign) themselves to an event that has been placed on hold, if permitted by agency policy. HxGN OnCall Dispatch | Essentials 342 Call / Incident / Event Management Scheduled Events Provide the ability to automatically schedule the CFS event for future dispatch. HxGN OnCall Dispatch | Viewer 343 Call / Incident / Event Management Scheduled Events Allow scheduled events to be created by entering a CFS or by sending a message. HxGN OnCall Dispatch | Viewer 344 Call / Incident / Event Management Scheduled Events Be capable of displaying a list of all scheduled events. HxGN OnCall Dispatch | Viewer 345 Call / Incident / Event Management Scheduled Events Provide the ability for authorized users to activate a scheduled event at any time. HxGN OnCall Dispatch | Viewer 346 Call / Incident / Event Management Scheduled Events Send a message to the appropriate users when the scheduled activity occurs. HxGN OnCall Dispatch | Viewer 347 Call / Incident / Event Management Scheduled Events Support location override for scheduled incidents HxGN OnCall Dispatch | Viewer 348 Call / Incident / Event Management Secondary Incident Location Provide the ability to note responding apparatus has arrived “in staging,” which may be a remote secondary address associated with the primary incident location. HxGN OnCall Dispatch | Resource Management Page 40 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 349 Call / Incident / Event Management Secondary Incident Location Provide the ability to change a unit’s location from the primary address to a secondary address without clearing the unit from the incident or CAD record. HxGN OnCall Dispatch | Resource Management 350 Call / Incident / Event Management Secondary Incident Location Log a date/time stamped record of the change in the CFS event. HxGN OnCall Dispatch | Resource Management 351 Call / Incident / Event Management Single Discipline Incident to a Combined Discipline Incident Provide the ability to add another agency’s resources to a CFS event.HxGN OnCall Dispatch | Essentials 352 Call / Incident / Event Management Single Discipline Incident to a Combined Discipline Incident Provide the ability to assign an agency specific incident/event number to the CFS event.HxGN OnCall Dispatch | Essentials 353 Call / Incident / Event Management Single Discipline Incident to a Combined Discipline Incident Provide the ability to link added agency records with the initial CFS event.HxGN OnCall Dispatch | Essentials 354 Call / Incident / Event Management Single Discipline Incident to a Combined Discipline Incident Provide the ability to share incident information across multiple linked records.HxGN OnCall Dispatch | Essentials 355 Call / Incident / Event Management Single Discipline Incident to a Combined Discipline Incident Provide the ability to track the added resources for the duration of the incident.HxGN OnCall Dispatch | Essentials 356 Call / Incident / Event Management Timers Have, and allow configuration of, multiple timers based on unit status and CAD incident type, such as time on a particular call, time since last check- in, and time at the hospital or jail. HxGN OnCall Dispatch | Advantage 357 Call / Incident / Event Management Timers Have, and allow configuration of, timers for CAD system events, such as a priority 1 call overdue to be dispatched. HxGN OnCall Dispatch | Advantage 358 Call / Incident / Event Management Timers Allow for operators to manually place a timer alert on a CFS or a unit. HxGN OnCall Dispatch | Advantage Page 41 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 359 Call / Incident / Event Management Timers Minimally include “down to the second” timestamps (e.g. hh/mm/ss). HxGN OnCall Dispatch | Advantage 360 Call / Incident / Event Management Timers Allow configurable timers (i.e. ‘hh:mm:ss’, ‘mm:ss’, or ‘ss’). HxGN OnCall Dispatch | Advantage 361 Call / Incident / Event Management User Defined Status Timers Be equipped with predefined timers that can be configured by the system administrator.HxGN OnCall Dispatch | Advantage 362 Call / Incident / Event Management User Defined Status Timers Provide the ability for the system administrator to create customized definable timers.HxGN OnCall Dispatch | Advantage 363 Call / Incident / Event Management User Defined Status Timers Record timer activity to the CFS event log.HxGN OnCall Dispatch | Advantage 364 Call / Incident / Event Management User Defined Status Timers Produce both visual and audible alerts to the dispatcher when a timer is triggered. HxGN OnCall Dispatch | Advantage 365 Supplemental Resource Request and Tracking Request Supplemental Resource Be able to store, and easily retrieve, a file for standardized and ad hoc supplemental resources that may be recalled and requested as needed for services not available from the public safety agencies. HxGN OnCall Dispatch | Essentials 366 Supplemental Resource Request and Tracking Request Supplemental Resource Make request and “dispatch” of said resources on the basis of the unique type of service needed, the geographic proximity to the site of the needed service, or a rotation of the unique service providers of a given type—or, a combination of methods. HxGN OnCall Dispatch | Essentials 367 Supplemental Resource Request and Tracking Request Supplemental Resource Be able to create a unique or supplemental unit designation in real time. HxGN OnCall Dispatch | Essentials 368 Supplemental Resource Request and Tracking Request Supplemental Resource Be able to record the activities of unique or supplemental units in the same manner in which agency response units are tracked and their activities recorded. HxGN OnCall Dispatch | Essentials Page 42 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 369 Supplemental Resource Request and Tracking Request Supplemental Resource Allow for agency-configurable non-agency units to be recommended, such as the closest towing company recommendation when a unit is dispatched to an accident event type. The recommendation will take into account the rotation of towing companies. HxGN OnCall Dispatch | Essentials 370 Supplemental Resource Request and Tracking Request Supplemental Resource Rotation List Store, and provide for easy retrieval, a list of authorized providers of unique or supplemental supplies or services. HxGN OnCall Dispatch | Essentials 371 Supplemental Resource Request and Tracking Request Supplemental Resource Rotation List Provide multiple sources of contact for each authorized vendor. HxGN OnCall Dispatch | Essentials 372 Supplemental Resource Request and Tracking Request Supplemental Resource Rotation List Be able to display the list of authorized service providers based upon geographical proximity to the site of need, by rotation, or by agency preference based upon contractual agreement. HxGN OnCall Dispatch | Essentials 373 Supplemental Resource Request and Tracking Request Supplemental Resource Rotation List Record the transactions that occur with supplemental or unique resources. HxGN OnCall Dispatch | Essentials 374 Supplemental Resource Request and Tracking Notify Supplemental Resource Service Provide the ability to contact the supplemental resource; and, provide dispatch information by the dispatcher about the incident to which the resource is requested to respond. HxGN OnCall Dispatch | Essentials 375 Supplemental Resource Request and Tracking Notify Supplemental Resource Service Provide the ability to record the availability of the entity to provide its services. o A supplemental service that cannot be contacted or informs the agency of its inability to respond within a prescribed time be considered unavailable to provide the service. HxGN OnCall Dispatch | Essentials Page 43 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 376 Supplemental Resource Request and Tracking Notify Supplemental Resource Service Provide the ability to select a supplemental resource. HxGN OnCall Dispatch | Essentials 377 Supplemental Resource Request and Tracking Notify Supplemental Resource Service If a resource is unavailable, or unable to respond in a reasonable time frame, then the user contacts the next listed resource until one is found that is available. HxGN OnCall Dispatch | Essentials 378 Supplemental Resource Request and Tracking Enter and Update Supplemental Service Record Provide the ability to create a record of the supplemental service request.HxGN OnCall Dispatch | Essentials 379 Supplemental Resource Request and Tracking Enter and Update Supplemental Service Record Accommodate selection from the provided list either at random, by geographic proximity to the site of need, or by rotation. HxGN OnCall Dispatch | Essentials *random not available 380 Supplemental Resource Request and Tracking Enter and Update Supplemental Service Record Trigger the next provider in the rotation, when selected by rotation and upon creation of the record HxGN OnCall Dispatch | Essentials 381 Supplemental Resource Request and Tracking Enter and Update Supplemental Service Record Process the rotation regardless of the requested resource’s ability to respond.HxGN OnCall Dispatch | Essentials 382 Incident Disposition Determine Incident / Event Status Provide the ability to change the event status as the situation evolves or a resolution is achieved.HxGN OnCall Dispatch | Essentials 383 Incident Disposition Determine Incident / Event Status The MDC interface: Allow the field user to enter one or more event dispositions. HxGN OnCall Dispatch | Mobile Unit 384 Incident Disposition Determine Incident / Event Status The MDC interface: Allow the field user to update the CFS event in CAD and make that data available to the RMS. HxGN OnCall Dispatch | Mobile Unit Page 44 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 385 Incident Disposition Utilize Incident Management Have the ability to dynamically update the CFS event with notations, updates, status changes, and notifications. HxGN OnCall Dispatch | Essentials 386 Incident Disposition Utilize Incident Management Make the updated CFS data available for transfer to an RMS. HxGN OnCall Dispatch | Viewer 387 Incident Disposition Determine Report Functionality Provide the ability to automatically transfer incident/event data relevant to external RMS or reporting systems. HxGN OnCall Dispatch | CAD Link 388 Incident Disposition Determine Report Functionality Be able to determine, based upon incident type and/or disposition, whether an agency report is required. HxGN OnCall Dispatch | Essentials 389 Incident Disposition Determine Report Functionality Accommodate either a push or pull of incident/event data from/to the RMS.HxGN OnCall Dispatch | CAD Link *pull from RMS requires Informer 390 Incident Disposition Record Disposition Provide for the CFS event to contain the disposition of the incident.HxGN OnCall Dispatch | Essentials 391 Incident Disposition Record Disposition Provide for narrative to be added giving detail to the disposition. HxGN OnCall Dispatch | Essentials 392 Incident Disposition Send Data to Records Management System Provide the ability to exchange all CFS event information with an RMS. HxGN OnCall Dispatch | CAD Link 393 Incident Disposition Assign Agency-Specific Report Numbers Assign an agency-specific report (i.e. case) number—if a report is required, and if required by agency policy—in addition to the CAD incident/event number, before the CFS event data is transferred to the RMS. HxGN OnCall Dispatch | Viewer Page 45 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 394 Incident Disposition Assign Agency-Specific Report Numbers Allow for both the CAD CFS Event Number and the Agency Report Numbers to be fully configurable (e.g. “1 to n,” “mmddyyxxxx,” “mmddyyhhmmssxxx,” “FY12xxxxxx,” “2012- mmdd-xxxxx”). HxGN OnCall Dispatch | Administrator 395 Business Function: CAD System Administration Geofile Maintenance Validate all locations entered into or processed by the CAD system against the CAD system’s geofile.HxGN OnCall Dispatch | Viewer 396 Business Function: CAD System Administration Geofile Maintenance Provide an interactive, GUI-based address matching tool for assisting users to determine the location of incidents that do not have an exact geofile match for their initially- entered location. HxGN OnCall Dispatch | Viewer 397 Business Function: CAD System Administration Geofile Maintenance Be capable of determining X,Y coordinate values that represent the location of incidents whose locations have been validated. HxGN OnCall Dispatch | Viewer 398 Business Function: CAD System Administration Geofile Maintenance Be capable of displaying coordinates anywhere on the map with mouse over. HxGN OnCall Dispatch | Viewer 399 Business Function: CAD System Administration Geofile Maintenance Support coordinate-based operations including X/Y, Lat/Lon, and USNG. HxGN OnCall Dispatch | Viewer *X/Y not supported 400 Business Function: CAD System Administration Geofile Maintenance Make possible integration of the CAD system’s geofile with Global Positioning Satellite (GPS), AVL, and Automatic Person Location (APL) systems. HxGN OnCall Dispatch | Tracker 401 Business Function: CAD System Administration Geofile Maintenance Support X,Y coordinate-based geographic searches for such things as nearby hazardous materials, duplicate incidents, and premises information at or near an incident’s location. HxGN OnCall Dispatch | Advantage Page 46 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 402 Business Function: CAD System Administration Geofile Maintenance Be capable of importing geographic boundary information (e.g. station boundaries, jurisdictional boundaries, reporting districts, response zones, neighborhoods, precincts) from GIS and other geographic data sources. HxGN OnCall Dispatch | Administrator 403 Business Function: CAD System Administration Geofile Maintenance Be capable of importing topologically-structured street networks and other linear features (e.g. rivers, streams, utility right of ways, bus routes) from GIS and other geographic data sources. HxGN OnCall Dispatch | Viewer 404 Business Function: CAD System Administration Geofile Maintenance Be capable of importing point data (e.g. landmarks, parcel address points, business locations, retail store address points, fire hydrants) from GIS and other geographic data sources. HxGN OnCall Dispatch | Viewer 405 Business Function: CAD System Administration Geofile Maintenance Be capable of importing other types of geographic data (e.g. park boundaries, rectified aerial photography, trailer parks, apartment complexes) from GIS and other geographic data sources. HxGN OnCall Dispatch | Viewer 406 Business Function: CAD System Administration Geofile Maintenance Include location databases such as hazards, general premises information, street closures, and other user-definable GIS type data. HxGN OnCall Dispatch | Administrator *street closures are maintained by the GIS provider 407 Business Function: CAD System Administration Geofile Maintenance Support parcel-level GIS information and use this information for address/location validation.HxGN OnCall Dispatch | Viewer Page 47 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 408 Business Function: CAD System Administration Geofile Maintenance Support multiple layers of information; for example, the storage of building footprints, aerial photographs and other images (i.e. pictures of specific buildings) that are associated with specific areas and addresses. HxGN OnCall Dispatch | Viewer 409 Business Function: CAD System Administration Geofile Maintenance Maintain the CAD system’s geofile while the system is live and operational. HxGN OnCall Dispatch | Administrator 410 Business Function: CAD System Administration Geofile Maintenance Support boundary assignments (i.e. determining the response zone and jurisdiction for each incident) in real time by processing the incident’s X,Y coordinates against the RCL and/or address point file, and the appropriate boundary files. HxGN OnCall Dispatch | Viewer 411 Business Function: CAD System Administration Geofile Maintenance Support duplicate incident checks based upon the location of the incident. HxGN OnCall Dispatch | Viewer 412 Business Function: CAD System Administration Geofile Maintenance All incidents located within the CAD system’s duplicate incident search radius be checked as potential duplicates. HxGN OnCall Dispatch | Viewer 413 Business Function: CAD System Administration Geofile Maintenance Should meet i3 standards and functions in order to comply with NG9-1-1 requirements. HxGN OnCall Dispatch | Call- Taker Page 48 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 414 Business Function: CAD System Administration Geofile Maintenance Be able to support different search distance criteria for different types of incident situations and hazards (e.g. a search radius of 300 feet will be used for hazardous conditions, and a search radius of 1,320 feet will be used to identify potentially duplicate incidents). o CAD system administrators be able to modify these search distance parameters. o CAD users have the ability to select the unit of measurement necessary(feet versus meters). HxGN OnCall Dispatch | Viewer *unit of measurement cannot be changed 415 Business Function: CAD System Administration Geofile Maintenance Generate an audible and/or visual alert when any potential duplicate incidents are identified.HxGN OnCall Dispatch | Viewer 416 Business Function: CAD System Administration Geofile Maintenance Include the capability for manually editing and entering any geographic data required by, or imported into, the system’s GIS (given the appropriate user permissions). HxGN OnCall Dispatch | Administrator *Editing of the master Geofile data is a function of GIS provider; however, special address and commonplaces may be imported and then manually edited with the system. 417 Business Function: CAD System Administration Security Employ data security measures that are compliant with applicable state and federal security standards. HxGN OnCall Dispatch | Viewer *system wide 418 Business Function: CAD System Administration Security Employ data encryption that meets CJIS security policy standards for any exchange or transmittal of CAD data between remote devices and CAD system servers. HxGN OnCall Dispatch | Viewer *system wide Page 49 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 419 Business Function: CAD System Administration Security Provide appropriate safeguards to ensure that only authorized devices and users are allowed access to the CAD system and stored information. HxGN OnCall Dispatch | Viewer *system wide 420 Business Function: CAD System Administration Security Provide a security profile to control individual user access to the various modules, applications, functions, features, and data available within the CAD system. HxGN OnCall Dispatch | Administrator 421 Business Function: CAD System Administration Security Provide security to ensure that fire and EMS personnel do not have access to law incidents when CJIS data is restricted to only law enforcement user access. HxGN OnCall Dispatch | Administrator 422 Business Function: CAD System Administration Security Meet CJIS Security Policy requirements.HxGN OnCall Dispatch | Viewer *system wide 423 Business Function: CAD System Administration Security Validate each user’s credentials through a mandatory logon process before being granted access to any functions or data available within the CAD system. HxGN OnCall Dispatch | Viewer *system wide 424 Business Function: CAD System Administration Security Enable a user replacing an existing user to quickly log off the existing user and logon without the need to exit from CAD or re-start the CAD application (i.e. when two-factor authentication does not apply.) HxGN OnCall Dispatch | Advantage 425 Business Function: CAD System Administration Security Enable system administrators to create and maintain a centralized and indexed database containing information about each system user, including their unique user ID, password, contact information, and security profile. HxGN OnCall Dispatch | Administrator Page 50 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 426 Business Function: CAD System Administration Security Enable system administrators to define individual user access privileges and assign them to security groups. HxGN OnCall Dispatch | Administrator 427 Business Function: CAD System Administration Security Provide a method for authorized users to reset a user’s password. HxGN OnCall Dispatch | Administrator 428 Business Function: CAD System Administration Security Associate the user ID and workstation ID with all CAD system transactions, including data entry and report generation. (Excludes Workstation ID) HxGN OnCall Dispatch | Viewer *system wide 429 Business Function: CAD System Administration Security Limit access to the centralized user security database to only specifically authorized users.HxGN OnCall Dispatch | Administrator 430 Business Function: CAD System Administration Security Establish security profiles that are assigned to individual users or user groups based on personnel classifications (e.g. call taker, dispatcher, system administrator, supervisor). HxGN OnCall Dispatch | Administrator 431 Business Function: CAD System Administration Security Prohibit deletion of any data entered into a CFS event. HxGN OnCall Dispatch | Viewer *system wide 432 Business Function: CAD System Administration Security Provide application and module level security that enables certain users to access specific CAD system functions and application modules, while keeping other users from accessing these same functions and modules. HxGN OnCall Dispatch | Administrator 433 Business Function: CAD System Administration Security Provide data entry form security that enables certain users to access specific data entry forms, while keeping other users from accessing these same data entry forms. HxGN OnCall Dispatch | Administrator Page 51 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 434 Business Function: CAD System Administration Security Provide record type security that enables certain users to access specific CAD system record types, while keeping other users from accessing these same record types. HxGN OnCall Dispatch | Advantage 435 Business Function: CAD System Administration Security Provide transaction level security that enables certain users to access specific transaction types (e.g. criminal history queries to NCIC), while keeping other users from accessing these same transaction types. HxGN OnCall Dispatch | Administrator 436 Business Function: CAD System Administration Security Facilitate the use of unique user IDs and passwords to control CAD system access and privileges. HxGN OnCall Dispatch | Administrator 437 Business Function: CAD System Administration Security Be capable of using biometric identification (e.g. thumb print identification, retinal ID) to control system access and privileges. HxGN OnCall Dispatch | Viewer *system wide 438 Business Function: CAD System Administration Security Provide a “single entry” to enable logons to multiple authorized systems that are available through the system (e.g. NCIC, Nlets). HxGN OnCall Dispatch | Viewer *system wide 439 Business Function: CAD System Administration Security Limit access to system functions and data by physical device (e.g. PCs, terminals), as well as by user ID. HxGN OnCall Dispatch | Administrator *can limit by user id, but not physical device 440 Business Function: CAD System Administration Security Have the capability to automatically log-off CAD workstations based on inactivity periods set by the system administrator for specific user groups, users and workstations. HxGN OnCall Dispatch | Advantage *only available at the global level 441 Business Function: CAD System Administration Security Provide the ability to “lock out” a user after a system administrator defined number of failed attempted logons. HxGN OnCall Dispatch | Administrator Page 52 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 442 Business Function: CAD System Administration Security Require users to change their individual password after a system administrator configurable time limit for use of the same password expires or a set time period (e.g. 90 days). HxGN OnCall Dispatch | Administrator 443 Business Function: CAD System Administration Security Provide the ability for individual system users to change their passwords. HxGN OnCall Dispatch | Viewer 444 Business Function: CAD System Administration Security Provide the capability for individual user name change (e.g. getting married) and keep a link to historical data. HxGN OnCall Dispatch | Administrator 445 Business Function: CAD System Administration Logging Include a transaction audit database that contains all system transactions and that includes the logon identification (i.e. user ID and workstation ID), date and time stamp, transaction type, contents before ID, and contents after the transaction completes. HxGN OnCall Dispatch | Advantage 446 Business Function: CAD System Administration Logging Enable authorized system users to search the transaction audit database by date and time ranges, by application module, transaction type, specific tables and data fields within tables, specific data entry forms, individual users, user groups, workstation ID, and by various combinations of these factors. HxGN OnCall Analytics | Dispatch Essentials 447 Business Function: CAD System Administration Logging Enable authorized system users to create formatted reports and/or export the results of transaction audit database queries and searches. HxGN OnCall Analytics | Dispatch Essentials Page 53 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 448 Business Function: CAD System Administration Logging Enable authorized system users to generate statistical reports on transactions contained in the transaction audit database for all users, a subset of users and/or user groups, for a specified date and time range, and for various combinations of these factors. HxGN OnCall Analytics | Dispatch Essentials 449 Business Function: CAD System Administration Logging Prohibit any changes to the contents of the CAD transaction audit database. HxGN OnCall Dispatch | Viewer *system wide 450 Business Function: CAD System Administration Logging Store the date, time, workstation ID, and user ID associated with unsuccessful sign-on attempts.HxGN OnCall Dispatch | Viewer 451 Business Function: CAD System Administration Configuration Enable authorized system administrators to configure the CAD system to meet the requirements of the agencies using the system by creating and modifying CAD configuration parameters. HxGN OnCall Dispatch | Administrator 452 Business Function: CAD System Administration Configuration Enable authorized system administrators to modify CAD configuration parameters without the requirement for a programmer or other support from the manufacturer of the CAD system. HxGN OnCall Dispatch | Administrator 453 Business Function: CAD System Administration Configuration Include functionality for table driven and directly modifiable functionality by authorized system administrators. HxGN OnCall Dispatch | Administrator 454 Business Function: CAD System Administration Configuration Include functionality for interactive, menu-driven, GUI-based tool that allows authorized administrators to easily update and modify parameters. HxGN OnCall Dispatch | Administrator Page 54 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 455 Business Function: CAD System Administration Configuration Include functionality for on-line help that lists all of the available options for a configuration parameter, and a description of the impacts resulting from changing the parameter to each of its available options. HxGN OnCall Dispatch | Administrator 456 Business Function: CAD System Administration Configuration Include functionality for modifications to CAD configuration parameters when the CAD system is active without having to shut the entire CAD system down or restart it. HxGN OnCall Dispatch | Administrator 457 Business Function: CAD System Administration Configuration Include functionality for modifying agency and user specific workflows, such as when and under what circumstances a CFS event is automatically routed from a call taker to a dispatcher and which users (e.g. call takers, dispatchers, supervisors) receive system routed CFS events. HxGN OnCall Dispatch | Administrator 458 Business Function: CAD System Administration Configuration Include functionality for specifying the agencies that will be included in the CAD system, along with their attributes (i.e. fire department, volunteers, law enforcement agency). HxGN OnCall Dispatch | Administrator 459 Business Function: CAD System Administration Configuration Include functionality for specifying and modifying the type of resources available in the system.HxGN OnCall Dispatch | Administrator 460 Business Function: CAD System Administration Configuration Include functionality for specifying the incident types that will be processed by the system.HxGN OnCall Dispatch | Administrator 461 Business Function: CAD System Administration Configuration Include functionality for entering and modifying dispatch policies that specify the type of resources that are dispatched to specific incident types. HxGN OnCall Dispatch | Administrator Page 55 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 462 Business Function: CAD System Administration Configuration Include functionality for configuring different system dispatch policies for each incident type, priority and agency using the system. HxGN OnCall Dispatch | Administrator 463 Business Function: CAD System Administration Configuration Include functionality for specifying the type of alerts and timers available in the system and their specific attributes (e.g. on/off, time interval, triggers, display features). HxGN OnCall Dispatch | Administrator 464 Business Function: CAD System Administration Configuration Include functionality for entering and modifying the type of dispositions, priorities, and other CFS event related parameters of the CAD system. HxGN OnCall Dispatch | Administrator 465 Business Function: CAD System Administration Configuration Include functionality for specifying the starting point and formats of case numbers created by the CAD system for each agency using the system. HxGN OnCall Dispatch | Administrator 466 Business Function: CAD System Administration Configuration Include functionality for specifying the sort order, layout, color, font, and other appearance and operational attributes of the CAD system’s windows and menus. HxGN OnCall Dispatch | Administrator 467 Business Function: CAD System Administration Configuration Include functionality for modifying the look and feel of CAD workstations. HxGN OnCall Dispatch | Administrator 468 Business Function: CAD System Administration Configuration Include functionality for modifying the look and feel of the tactical map display available in the system (e.g. setting up the graphic information appearing at different zoom levels, predefined zoom levels for different incident types, icons). HxGN OnCall Dispatch | Administrator Page 56 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 469 Business Function: CAD System Administration Configuration Include functionality for modifying the display and functional characteristics of CAD system queues (e.g. pending incident queue, incident queue, active incident queue, stacked incidents queue). HxGN OnCall Dispatch | Administrator 470 Business Function: CAD System Administration Configuration Include functionality for modifying the display and functional characteristics of the CAD system’s resource recommendations. HxGN OnCall Dispatch | Administrator 471 Business Function: CAD System Administration Table Maintenance Include CAD tables that are maintained using entry windows.HxGN OnCall Dispatch | Administrator 472 Business Function: CAD System Administration Table Maintenance Include CAD table maintenance entry windows that have context-sensitive, field- level help. HxGN OnCall Dispatch | Viewer *field-level help not supported 473 Business Function: CAD System Administration Table Maintenance Enable changes made to CAD tables to become immediately effective and not affect overall CAD system availability nor require any CAD system down time. This does not preclude the refresh of individual workstations or other CAD devices as required by the CAD manufacturer. HxGN OnCall Dispatch | Administrator 474 Business Function: CAD System Administration Table Maintenance Allow agencies to define additional data elements based on their operational requirements.HxGN OnCall Dispatch | Advantage Page 57 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 475 Business Function: CAD System Administration Table Maintenance Provide the ability for tables to be defined to support the maintenance of the following CAD objects, including, but not limited to: o Agencies o BOLOs, including location, person, and vehicle o Clearance/disposition codes o Hazards o Hydrants o Incident/event types o Fire Stations o Memos o Messages (e.g. canned, scheduled) o Notifications o Personnel o Rosters o Run cards/response plans o Service types (i.e. law enforcement, fire, EMS) o Skills (personnel) o SOPs o Units o Unit attributes (e.g. ALS, BLS, Hurst tool) o Unit statuses (i.e. dispatched, en route, arrived, cleared) o Unit Types (e.g. i.e. patrol car, motorcycle, engine, ladder, pumper) o Vehicles HxGN OnCall Dispatch | Administrator 476 Business Function: CAD System Administration Communication Centre / PSAP Relocation Meet PSAP industry best practices and CJIS requirements.HxGN OnCall Dispatch | Viewer 478 Business Function: CAD System Administration Communication Centre / PSAP Relocation Account for a data-backup plan.HxGN OnCall Dispatch | Viewer Page 58 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 479 Business Function: CAD System Administration Communication Centre / PSAP Relocation Account for coordination of external inputs to the CAD system from third-party vendors (e.g. telephone, data, 9-1-1) for a minimal loss of functionality. HxGN OnCall Dispatch | Viewer 480 Business Function: CAD System Administration Communication Centre / PSAP Relocation Provide for access to a copy of the production system through the backup or disaster recovery environments. HxGN OnCall Dispatch | Viewer 481 Business Function: CAD System Administration CAD Catch Up Have the ability to manually open and create a CFS event sheet. HxGN OnCall Dispatch | Advantage 482 Business Function: CAD System Administration CAD Catch Up Provide the ability to log the entering individual’s information and time of entry. HxGN OnCall Dispatch | Advantage 483 Business Function: CAD System Administration CAD Catch Up Provide the ability for all information to be entered without any restrictions, and times/dates changed to reflect the actual time that notice of the CFS event was received. HxGN OnCall Dispatch | Advantage 484 Business Function: CAD System Administration CAD Catch Up Denote the manually-entered CFS event so there is a record that the CFS event was not entered when it was actually received. HxGN OnCall Dispatch | Advantage 485 Business Function: CAD System Administration CAD Catch Up Provide ability to manually designate the “starting” incident number (i.e. the last incident +1 for the starting number once the system is restarted). HxGN OnCall Dispatch | Administrator 486 Business Function: CAD System Administration CAD Catch Up Allow for simultaneous automatic and manual entry without degradation. HxGN OnCall Dispatch | Advantage 487 Business Function: CAD System Administration CAD Catch Up Include all the information in back entered records that a live incident/event sheet should require.HxGN OnCall Dispatch | Advantage 488 System Functions Notifications Enable the system administrator to define the rules for automatic CFS event notifications.HxGN OnCall Dispatch | Notifications Page 59 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 489 System Functions Notifications Provide the ability to create messages that are retained in the system and sent at pre-specified times. HxGN OnCall Dispatch | Advantage 490 System Functions Notifications Provide the ability to maintain a log of all messages processed by the system. HxGN OnCall Dispatch | Viewer 491 System Functions Notifications Allow the user to send and store messages to other users, groups, positions, or mobile devices. HxGN OnCall Dispatch | Viewer 492 System Functions Notifications Allow a message to be sent to multiple recipients and/or groups. HxGN OnCall Dispatch | Viewer 493 System Functions Notifications Log all sent messages.HxGN OnCall Dispatch | Viewer 494 System Functions Notifications Provide the ability to create and maintain automatic reminders of scheduled activities (e.g. radio tests): o Daily o Weekly o Monthly o Annually o User-defined (e.g. 30 minutes, 15 minutes, first day of the month) o Multiple activities or reminders per time slot HxGN OnCall Dispatch | Advantage 495 System Functions Contact List Allow a message to be sent to multiple recipients and/or groups.HxGN OnCall Dispatch | Viewer 496 System Functions Contact List Be able to log all sent messages.HxGN OnCall Dispatch | Viewer Page 60 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 497 System Functions Contact List Provide an emergency contacts list, to include: o Contact name o Street address o City o State o Zip o Telephone numbers o Relationship o User-defined/configurable fields HxGN OnCall Dispatch | Viewer 498 System Functions Premises Information / Hazards Provide the ability to enter a premises location by address, cross street or latitude/longitude.HxGN OnCall Dispatch | Administrator 499 System Functions Premises Information / Hazards Provide the ability to capture, maintain or interface to specific premises information types for operators: o Hazardous materials o Hazardous conditions o Lock codes o Dangerous animals o Handicap o Emergency contact information o Unit safety o Warrants o Alarms o Protective Orders, Sexual Offenders o Fire Pre-plans o Other user-defined premises fields/information o Electronic attachments (e.g. images, files) HxGN OnCall Dispatch | Administrator 500 System Functions Premises Information / Hazards Provide the ability to automatically create (i.e. upon closing of an incident) premises history based on pre-determined criteria. HxGN OnCall Dispatch | Viewer Page 61 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 501 System Functions Premises Information / Hazards Provide the ability to define valid date ranges for time-limited premises information at a given location (i.e. information valid between start date and end date), and to notify supervisor of pending expiration dates. HxGN OnCall Dispatch | Administrator 502 System Functions Premises Information / Hazards Provide the ability for supervisors to delete premises information for a given address or location based on expiration date and/or time of record, with prompted review prior to deletion (i.e. minimum of five years, on-line storage). HxGN OnCall Dispatch | Administrator 503 System Functions Premises Information / Hazards Provide the ability to define criteria for automatic premises information purges and activate or deactivate this feature. HxGN OnCall Dispatch | Backup 504 System Functions Premises Information / Hazards Provide the ability to verify that premises warning or hazard information has not been affected by changes to the geofile. HxGN OnCall Dispatch | Administrator *Special situation data can be edited and verified to confirm changes to premises warning or hazard information 505 System Functions Premises Information / Hazards Provide the ability to view premises information for a specific suite/apartment/unit, or to view all premises information for an entire building. HxGN OnCall Dispatch | Administrator 506 System Functions Premises Information / Hazards Provide the ability to automatically embed premises information into the event history at the time the event is created. HxGN OnCall Dispatch | Viewer 507 System Functions Premises Information / Hazards Create a permanent record of the premise's information in the event history. HxGN OnCall Dispatch | Viewer Page 62 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 508 System Functions Premises Information / Hazards Provide (or interface to) a “cautions” file to contain information pertaining to dangerous individuals possibly residing at that location or near proximity, and exceptional persons at the location, such as an emotionally disturbed person. o This include a caution type category and free form narrative. o The caution type be searchable. HxGN OnCall Dispatch | Viewer 509 System Functions Communications Center / Public Safety Answering Point Standard Operating Procedures Provide the ability to store and easily retrieve SOPs for the PSAP.HxGN OnCall Dispatch | Viewer 510 System Functions Communications Center / Public Safety Answering Point Standard Operating Procedures Provide a method where the retrieval of relevant SOPs is accessible from the CFS event information window and associated with the location, incident type, unit, or special skilled personnel responding. HxGN OnCall Dispatch | Viewer 511 System Functions Communications Center / Public Safety Answering Point Standard Operating Procedures Provide a SOP tool to prompt the user to ask for additional information, perform certain tasks, or relay critical information to responding units or other responders. HxGN OnCall Dispatch | Viewer 512 System Functions Agency-Specific Incident / Location / Unit Standard Operating Procedures Be able to store SOPs that are associated with incident types, properties and/or units.HxGN OnCall Dispatch | Viewer 513 System Functions Agency-Specific Incident / Location / Unit Standard Operating Procedures Make these SOPs available for viewing and/or transmitting when an associated incident type is encountered, the response is to a specific location with unique response/operational requirements, and/or specialized units are assigned to the incident. HxGN OnCall Dispatch | Viewer Page 63 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 514 System Functions Agency-Specific Incident / Location / Unit Standard Operating Procedures Include (optional) more sophisticated functionality (e.g. alert and check off of tasks, notifications made, or other issues capable of being tracked). HxGN OnCall Dispatch | Viewer 515 System Functions Remote Access Support remote access by users outside of the communications center. HxGN OnCall Dispatch | Viewer 516 System Functions Remote Access Provide access that includes permission-based views of CAD data by certain workstations and/or individuals. HxGN OnCall Dispatch | Viewer *not available by workstation 517 System Functions Remote Access Provide remote access that includes security- controlled, web-based access. HxGN OnCall Dispatch | Viewer 518 System Functions Remote Access Be capable of remote access from a separate location, such as a mobile command post or a secondary location. HxGN OnCall Dispatch | Viewer 519 System Functions CAD Workstation-to-CAD Workstation Messaging Provide short messaging from one CAD workstation to another. HxGN OnCall Dispatch | Viewer 520 System Functions CAD Workstation-to-CAD Workstation Messaging Include the ability to create message groups, whether they are dispatch workstations, mobile computers, groups within the PSAP, or other communications devices. HxGN OnCall Dispatch | Administrator 521 System Functions CAD Workstation-to-CAD Workstation Messaging Enable the system administrator to disable this function if desired on an agency basis. HxGN OnCall Dispatch | Administrator 522 System Functions CAD Workstation-to-CAD Workstation Messaging Log all messages.HxGN OnCall Dispatch | Viewer 523 System Functions CAD Workstation-to-CAD Workstation Messaging Provide the ability to create user definable “canned” messages for selection and distribution to other system users. HxGN OnCall Dispatch | Administrator 526 System Functions Narrative Field “Shorthand” / Auto Text Provide the ability to recognize character patterns and automatically fill in expanded text.HxGN OnCall Dispatch | Advantage Page 64 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 527 System Functions Narrative Field “Shorthand” / Auto Text Expand (automatically) the shorthand into a full description and save it into the narrative.HxGN OnCall Dispatch | Advantage 528 System Functions Narrative Field “Shorthand” / Auto Text Allow the agency to add agency-specific shorthand terms and their expansions. HxGN OnCall Dispatch | Advantage 529 System Functions Command Line / GUI Include the ability to be operated via a command line entry, mouse and keyboard, or both.HxGN OnCall Dispatch | Viewer 530 System Functions Date/Time Stamps Stamp date/time and log CAD activities, such as status changes, task accomplishments (i.e. Fire Attack Initiated, Time Fire Declared Under Control, Time at Patient), and notifications, as well as many other system transactions and the time they occur. HxGN OnCall Dispatch | Viewer 531 System Functions Date/Time Stamps Save original time stamps even if they are overridden. HxGN OnCall Dispatch | Viewer 532 System Functions Date/Time Stamps Protect time stamp overrides; and, any changes be documented on the incident, including the ID of the person performing the modification and the reason for the modification. HxGN OnCall Dispatch | Viewer 533 System Functions Date/Time Stamps Maintain all time stamps to be minimally accurate to the second (e.g. hh:mm:ss). HxGN OnCall Dispatch | Viewer 534 System Functions Unit Status Transitions Matrix Prohibit unit status transitions that do not conform to the business rules of the agency. HxGN OnCall Dispatch | Essentials 535 System Functions Single Sign-on for CAD and CAD Sub-systems Be designed to provide a single sign-on for CAD and its integrated sub-systems. HxGN OnCall Dispatch | Viewer 536 System Functions Multi-Agency / Multi- Jurisdictional Capability Have the ability to create a CFS event for user- defined multi-agency events and route the CFS event to the appropriate agency dispatch position(s). HxGN OnCall Dispatch | Viewer Page 65 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 537 System Functions Multi-Agency / Multi- Jurisdictional Capability Have the ability to create a linked CFS event for each required agency and route the CFS event(s) to the appropriate dispatch positions when an event involves more than one agency. HxGN OnCall Dispatch | Viewer 538 System Functions Multi-Agency / Multi- Jurisdictional Capability Have the capacity to create a multi-jurisdictional response; for example, should Jurisdiction X determine that Jurisdiction Y resources are needed on the scene, the fire dispatcher have the ability to forward/copy the CFS event without re-entering the event information to the appropriate Jurisdiction Y dispatcher based on CAD recommended or dispatched units. HxGN OnCall Dispatch | Viewer 539 System Functions Multi-Agency / Multi- Jurisdictional Capability Provide the ability to create and route a CFS event for dispatch even though the event is in another jurisdiction. HxGN OnCall Dispatch | Viewer 540 System Functions Multi-Agency / Multi- Jurisdictional Capability Provide the ability to transfer an active CFS event to another agency without closing the CAD CFS event within the originating agency. HxGN OnCall Dispatch | Essentials 541 System Functions Multi-Agency / Multi- Jurisdictional Capability Provide the ability to link cross-jurisdictional events using agency-definable parameters.HxGN OnCall Dispatch | Viewer 542 System Functions Multi-Agency / Multi- Jurisdictional Capability Update the originating jurisdiction’s CFS event information if the dispatcher in the receiving jurisdiction updates or supplements the event. HxGN OnCall Dispatch | Viewer 543 System Functions Multi-Agency / Multi- Jurisdictional Capability Have the ability to create agency-definable recommendations for cross jurisdictional responses and automated messaging based on user-definable parameters. HxGN OnCall Dispatch | Essentials Page 66 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 544 System Functions Multi-Agency / Multi- Jurisdictional Capability Provide the ability to identify other jurisdiction addresses and alert the CAD user with the jurisdiction’s name and contact information. HxGN OnCall Dispatch | Viewer 545 Reporting and Monitoring Dispatch Supervisor Support Provide the ability for a CAD supervisor, or another dispatcher with appropriate system permissions, to observe the activity of a given dispatcher including the pending events queue, active events, available units list, and map. HxGN OnCall Dispatch | Essentials 546 Reporting and Monitoring Dispatch Supervisor Support Enable a supervisor, or another dispatcher with appropriate system permissions, to co-dispatch the units under the control of another dispatcher. HxGN OnCall Dispatch | Essentials 547 Reporting and Monitoring Dispatch Supervisor Support Have the ability to add additional dispatchers “on- the-fly” for one or more services (law enforcement, fire service, and/or EMS), either globally or for predetermined geographical areas. HxGN OnCall Dispatch | Essentials 548 System Functions CAD Management Reporting Include standard reports that simultaneously use date, time, location, and/or incident type search parameters for report definitions.HxGN OnCall Dispatch | Operational Reports 549 System Functions CAD Management Reporting Include the capability of customizing standard reports and for creating user- defined reports.HxGN OnCall Dispatch | Operational Reports 550 System Functions CAD Management Reporting Provide access to all reports to the user, subject to permissions, from within the CAD system.HxGN OnCall Analytics | Dispatch Essentials Page 67 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 551 System Functions CAD Management Reporting Include reports in the CAD security/permissions function (i.e. individual reports can be made available/unavailable based on a user’s security profile). HxGN OnCall Analytics | Dispatch Essentials 552 System Functions CAD Management Reporting Provide all reports to users, subject to permissions, regardless of the application used to create user-defined or custom reports (i.e. internal to the CAD system or via a third- party reporting or analysis tool). HxGN OnCall Analytics | Dispatch Essentials 553 System Functions CAD Management Reporting Provide an ad hoc reporting capability.HxGN OnCall Analytics | Dispatch Essentials 554 System Functions CAD Management Reporting Provide a data exporting capability.HxGN OnCall Analytics | Dispatch Essentials 555 System Functions Training and Testing Include a training environment that accurately mirrors the live environment, including all tables and administrative configurations, and allows for call takers and dispatchers to train on specific services (i.e. law enforcement, fire service, and/or EMS) and on pre- configured geographic areas identical to that of the live environment. HxGN OnCall Dispatch | Viewer 556 System Functions Training and Testing Be clearly identifiable as the training environment (e.g. “TRAINING” prominently displayed on the screen). HxGN OnCall Dispatch | Viewer 557 System Functions Training and Testing Have a separate E9-1-1 test connection or canned script E9-1-1 information and provide realistic training regarding incoming E9-1-1 data. HxGN OnCall Dispatch | Call- Taker Page 68 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 558 System Functions Training and Testing Be able to be used, operated, started up, shut down, and updated to match the live application without affecting the live environment. HxGN OnCall Dispatch | Viewer 559 System Functions Training and Testing Be able to be used to test modifications and updates to the live CAD application prior to implementing the modifications and updates in the live environment. Some larger PSAPs may maintain a separate test environment for application development staff that is independent of the training environment. HxGN OnCall Dispatch | Viewer 560 System Functions Training and Testing Have a separate E9-1-1 test connection or canned script E9-1-1 information (i.e. wireline, cellular, no record found, and VoIP) and provide realistic training regarding incoming E9-1-1 data. HxGN OnCall Dispatch | Viewer 561 System Functions Training and Testing The provider(s) provide initial and ongoing maintenance costs for the CAD training environment (and separate test environment if requested by the agency) in the proposed system cost section HxGN OnCall Dispatch | Viewer 562 System Functions Snapshot / Incident Replay Include functionality to provide a detailed, system- wide snapshot report and/or graphic display of the system status to include all units and events, based on a user-specified date, and time and an incident replay, based on a user-specified date and time, specific incidents, or other CAD events. HxGN OnCall Analytics | Dispatch Advantage Page 69 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 563 Interfaces Essential Interfaces Enable incoming E9-1-1 ANI/ALI data to be automatically mapped to corresponding address and phone data fields based on the Master Street Address Guide (MSAG) standard in the CFS event entry form. HxGN OnCall Dispatch | Call- Taker 564 Interfaces Essential Interfaces Support all E9-1-1 ANI/ALI formats including wireline, WPH1 and WPH2, VoIP, and Multi-Line Telephone Systems (MLTS). HxGN OnCall Dispatch | Call- Taker 565 Interfaces Essential Interfaces Enable the capture of additional fields captured in the CFS event, including ESN, call type (landline, wireless), and ANI/ALI tracking ID (if available). HxGN OnCall Dispatch | Call- Taker 566 Interfaces Essential Interfaces Use GIS data, if available, to extrapolate the closest geographical attribute (address, intersection, common place). o The radius used to extrapolate the closest geographical attribute be a configurable item within the system. o If GIS data is used to create the caller location, then the offset used to determine the approximate location be displayed. HxGN OnCall Dispatch | Viewer 567 Interfaces Essential Interfaces Provide configurable query forms and response displays and be able to be custom-built to accommodate different federal, state and local database protocols. HxGN OnCall Dispatch | Informer 568 Interfaces Essential Interfaces Provide authorization to perform various queries, and the ability to read responses definable by the individual agency and by role to the field level. HxGN OnCall Dispatch | Informer Page 70 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 569 Interfaces Essential Interfaces Allow users to submit queries either with the query form or the command line (if applicable).HxGN OnCall Dispatch | Informer 570 Interfaces Essential Interfaces Allow users to automatically submit queries for persons and vehicles as part of other data entry processes, such as CFS event creation. HxGN OnCall Dispatch | Informer 571 Interfaces Essential Interfaces Enable the query request type and the database(s) to be queried to be specified from a predefined list, with automatic narrowing of pertinent databases based on user data input. HxGN OnCall Dispatch | Informer 572 Interfaces Essential Interfaces Provide intelligent updating of the query forms based on other CAD forms that contain person or vehicle data. HxGN OnCall Dispatch | Informer 573 Interfaces Essential Interfaces Provide a capability for entering new information into the selected external database(s) provided the external database(s) allow updating. HxGN OnCall Dispatch | Informer 574 Interfaces Essential Interfaces Provide a method for multiple queries to be submitted through a single form or command. This is sometimes referred to as query spawning or cascading. HxGN OnCall Dispatch | Informer 575 Interfaces Essential Interfaces Make query responses accessible either through the query response form or from the command line and be associated with a query response type. HxGN OnCall Dispatch | Informer Page 71 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 576 Interfaces Essential Interfaces Allow users to submit new queries based on data in the query response to logical links; and, also reference attachments that are associated with the response, which can be downloaded and viewed. Ideally, CAD will provide the capability to view common industry-standard multimedia file- types. HxGN OnCall Dispatch | Informer 577 Interfaces Essential Interfaces Provide the capability to alert dispatchers, PSAP supervisors, and street-level supervisors of “Hot Hit” responses to queries made by officers in the field, or data run that exists elsewhere in the CAD system (i.e. in a CFS event). HxGN OnCall Dispatch | Informer 578 Interfaces Essential Interfaces Provide optional audible and visual alerts that can be configured by the system administrator.HxGN OnCall Dispatch | Informer 579 Interfaces Essential Interfaces Log all queries and their responses (when permitted) for audit purposes. HxGN OnCall Dispatch | Informer 580 Interfaces Essential Interfaces Provide the ability to configure alerts for queries run by unauthorized personnel or devices, as well as the ability to monitor multiple queries of the same data or specified data. HxGN OnCall Dispatch | Informer 582 Interfaces Essential Interfaces Be capable of TCP/IP communication, using industry-standard messaging protocols such as SMS and SMTP. HxGN OnCall Dispatch | Notifications 583 Interfaces Essential Interfaces Provide the capability of pre-formatted messages, especially to paging and other handheld devices.HxGN OnCall Dispatch | Notifications 584 Interfaces Essential Interfaces Create (automatically) an alphanumeric page for selected CAD incidents. HxGN OnCall Dispatch | Notifications Page 72 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 585 Interfaces Essential Interfaces Allow a dispatcher to initiate an alphanumeric page for any paging group. o The information sent in the page be configurable by the agency and generally contain the incident number, type of incident, and location of the incident. HxGN OnCall Dispatch | Notifications 586 Interfaces Essential Interfaces Provide an administrative mechanism to define paging groups. HxGN OnCall Dispatch | Notifications 587 Interfaces Essential Interfaces Include multiple message types, including email, BOLOs, notifications, tactical command chat rooms, and others. HxGN OnCall Dispatch | Notifications 588 Interfaces Essential Interfaces Provide a capability to format and send messages using just-in-time information, such as incident dispatch information, BOLOs or emergency weather alerts, and configurable triggers for these messages (e.g. incident type, assigned resources or location) for configurable recipients (i.e. send the chief a page when a specific incident type occurs at a specified location). HxGN OnCall Dispatch | Notifications 589 Interfaces Essential Interfaces Ensure that messaging interfaces make use of the CAD address book. o The CAD address book to allow for defining the types of devices recipients are able to receive messages on; and should have the ability to define a default device, as well as what devices (one, some or all) to receive massages on by day/time/response mode. HxGN OnCall Dispatch | Viewer Page 73 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 590 Interfaces Essential Interfaces Provide the ability to include attachments associated with the message that can be downloaded and viewed by operators and recipients. Ideally, CAD should provide a capability to view common industry-standard multimedia file- types. HxGN OnCall Dispatch | Viewer 596 Interfaces Essential Interfaces Allow the user to view and manage data provided by the RMS from within the CAD application through a hyperlink or other means; for example, when a CFS event is created, the CAD system may receive an alert from the RMS that data related to a person, location, or vehicle is present in the system. Alternatively, attachments such as photos or video also be available to CAD users through a download or attachment to the CFS event. HxGN OnCall Dispatch | Informer 597 Interfaces Essential Interfaces Provide (optional) a mechanism to create, record and otherwise manipulate a report number (separate from the CAD incident number) for cross- referencing purposes in the two systems. HxGN OnCall Dispatch | Viewer 599 Interfaces Additional Interfaces Be capable (depending on agency policy) of providing silent dispatch orders to a mobile unit, in addition to providing the unit with details of the CFS event, pre-plan information, patient information, premises history information, and other types of relevant information. HxGN OnCall Dispatch | Mobile Unit Page 74 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 600 Interfaces Additional Interfaces Enable the mobile unit to, if authorized, self- initiate incidents, self-dispatch incidents from a queue, change its status, query CAD and RMS information, and query local and national databases, such as wanted-person checks. Many MDCs, especially those not integrated as part of a CAD system, will require a message switch to enable the transmission of data and access to external databases. HxGN OnCall Dispatch | Mobile Unit 601 Interfaces Additional Interfaces Be able to have summary incident and resource monitoring capability. HxGN OnCall Dispatch | Mobile Unit 602 Interfaces Additional Interfaces Provide the ability for street supervisors in multi- agency, multi-jurisdictional environments to choose what agencies or areas within individual agencies they wish to monitor. HxGN OnCall Dispatch | Mobile Unit 603 Interfaces Additional Interfaces Provide the ability for CAD users to drill down into the details of summary incident and resource data, and have the ability to configure what data is displayed, as well as how it is displayed in terms of layout, font, font size, and colors. HxGN OnCall Dispatch | Mobile Unit 604 Interfaces Additional Interfaces Provide a day/night mode for mobile users.HxGN OnCall Dispatch | Mobile Unit 605 Interfaces Additional Interfaces Provide an integrated mobile mapping client.HxGN OnCall Dispatch | Mobile Unit 606 Interfaces Additional Interfaces Provide incident and resource management and monitoring capabilities through the in-car mapping solution. HxGN OnCall Dispatch | Mobile Unit Page 75 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 607 Interfaces Additional Interfaces Provide the ability to view real-time AVL data for user-selected units from the mobile client, and the ability to interact with the units identified on the map display. o This capability include messaging and other unit- related functionality. HxGN OnCall Dispatch | Mobile Unit 608 Interfaces Additional Interfaces Provide drive directions from the current location to a dispatched incident (or any selected location).HxGN OnCall Dispatch | Mobile Unit 609 Interfaces Additional Interfaces Provide mobile search capability for resources and personnel by type of vehicle, status and location.HxGN OnCall Dispatch | Mobile Unit 610 Interfaces Additional Interfaces Enable mobile users to search for incidents and locations. HxGN OnCall Dispatch | Mobile Unit 612 Interfaces Locational Systems Interfaces interface with existing state GIS. HxGN OnCall Dispatch | Viewer 613 Interfaces Locational Systems Interfaces Have a seamlessly integrated computerized map, which is a digitized map (GIS database) supporting Tactical Map Display (TMD). HxGN OnCall Dispatch | Viewer 614 Interfaces Locational Systems Interfaces Contain a map-centric TMD, in which the GIS/map is fully integrated with the CAD system. o In the case of a separate TMD application linked to the CAD system, the TMD support the automatic display of units as derived from an AVL system. HxGN OnCall Dispatch | Viewer Page 76 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 617 Interfaces Locational Systems Interfaces Include geographic data to support, at a minimum, the following: o System and boundaries registered to the street centerline in the geofile o Boundary assignments (i.e. determining the response zone for each incident) completed in real time by processing the incident’s X,Y coordinates against the RCL and boundary files to determine the incident’s location and response zone o Parcel-level GIS information, in which the approximate location of the front door of all the parcels in the state are stored in the geofile o Address validation and to determine an incident’s location o Bulk data uploading o Weekly data updates o Metadata o FGDC standard format feed, like XML (eXtensible Markup Language) and KML (Keyhole Markup Language). HxGN OnCall Dispatch | Viewer 618 Interfaces Locational Systems Interfaces Support valid MSAG names and multiple “aliases” for street names, intersections, commonplace names, landmarks, and street or highway route numbers. HxGN OnCall Dispatch | Viewer 619 Interfaces Locational Systems Interfaces Stem geographically sensitive hazards, dispatch policies, and other system functions from validated locations. HxGN OnCall Dispatch | Viewer Page 77 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 620 Interfaces Locational Systems Interfaces Initiate a location verification step to add the coordinates of the incident location to the event and display an incident icon on the TMD as the CFS event is created. HxGN OnCall Dispatch | Viewer 621 Interfaces Locational Systems Interfaces Make a duplicate event check based upon the location and/or coordinates of the event, during the CFS event creation process. HxGN OnCall Dispatch | Viewer 622 Interfaces Locational Systems Interfaces Notify the event entry position via a prompt and show a list of the potential duplicate(s) if, during event creation, a potential duplicate event in the area is found. HxGN OnCall Dispatch | Viewer 623 Interfaces Locational Systems Interfaces Have a parameter (modifiable by the system administrator) specifying the distance in number of feet or other unit of measurement, from the location of the incident for duplicate checking. HxGN OnCall Dispatch | Viewer 624 Interfaces Locational Systems Interfaces Define location databases such as hazards, general premises information, street closures, and other user definable databases. HxGN OnCall Dispatch | Administrator *street closures are maintained by the GIS provider 625 Interfaces Locational Systems Interfaces Perform a distance search to identify the existence of location information (e.g. hazards) during the event creation process. HxGN OnCall Dispatch | Viewer 626 Interfaces Locational Systems Interfaces Support different search distance criteria for different types of locations. HxGN OnCall Dispatch | Viewer 627 Interfaces Locational Systems Interfaces Support coordinate-based operations; be capable of full integration with a GPS-based AVL system; and, be capable of accepting named standards driven GPS reporting devices, such as GPS-enabled smartphones and portable radios. HxGN OnCall Dispatch | Viewer Page 78 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 628 Interfaces Locational Systems Interfaces Allow the system administrator to be able to modify parameters. HxGN OnCall Dispatch | Viewer 629 Interfaces Locational Systems Interfaces Seamlessly integrate with the CAD system and provide detailed, accurate, real- time vehicle tracking. HxGN OnCall Dispatch | Tracker 630 Interfaces Locational Systems Interfaces Include the AVL ID (represented as an alias) for each unit user’s status. HxGN OnCall Dispatch | Tracker 631 Interfaces Locational Systems Interfaces Include the indication that AVL is enabled for each unit on the user’s status window. AVL can also be used for reporting, messaging, response and alerting functionalities. HxGN OnCall Dispatch | Viewer 632 Interfaces Locational Systems Interfaces Include a visual indication if units displaying on the map and in the queues are AVL equipped. o The visual indication if units displaying on the map and in the queues are AVL equipped be customizable by the system administrator. HxGN OnCall Dispatch | Viewer 633 Interfaces Locational Systems Interfaces Be able to play back a unit’s AVL travel history and see the unit icon move from location to location on a map window. HxGN OnCall Analytics | Dispatch Advantage 634 Interfaces Locational Systems Interfaces Be capable of integrating with the existing GIS database. HxGN OnCall Dispatch | Viewer 635 Interfaces Locational Systems Interfaces Have other interactive functionalities also available, such as the ability to create and view unlimited groups of vehicles. HxGN OnCall Dispatch | Viewer 636 Interfaces Locational Systems Interfaces Provide for an automated alert for when vehicle is out of service. HxGN OnCall Dispatch | Viewer 637 Interfaces Locational Systems Interfaces Provide for an automated alert function.HxGN OnCall Dispatch | Viewer Page 79 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 638 Interfaces Locational Systems Interfaces Provide the ability to determine and modify all such alerts HxGN OnCall Dispatch | Viewer 639 Interfaces Locational Systems Interfaces Provide minimal AVL reports that include: o Complete activity detail for specific date range o Vehicle last stop/end time for date range o Exception reports including all events that triggered an alert o Vehicle first start/begin time for date range o Miles per day, stops per day, average and summaries per vehicle HxGN OnCall Analytics | Dispatch Essentials 640 Interfaces Locational Systems Interfaces Pass unit status information to the AVL system whenever unit status is changed. HxGN OnCall Dispatch | Tracker 641 Interfaces Locational Systems Interfaces Pass any changes in unit location information to the AVL system if unit location changes are generated within the proposed system (as opposed to the AVL navigation system). HxGN OnCall Dispatch | Tracker 642 Interfaces Locational Systems Interfaces Display AVL updates on the map within two seconds of their receipt from the AVL controller.HxGN OnCall Dispatch | Tracker 643 Interfaces Locational Systems Interfaces Should be able to dispatch the nearest appropriate unit based on its AVL location using an appropriate routing engine to make that determination. HxGN OnCall Dispatch | Essentials Page 80 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 644 Interfaces Locational Systems Interfaces Support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of thematic maps18; for example, a map showing the relative crime rate in each law enforcement district/zone in a given county. HxGn OnCall Analytics - Power Visuals 645 Interfaces Locational Systems Interfaces Support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of automatic pin maps19; for example, the system produce a map showing the location of all auto thefts that occurred in a given county during the last two months. HxGN OnCall Analytics | Power Visuals 646 Interfaces Locational Systems Interfaces Support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of spatial data aggregation20; for example, generate crime rates by district statistics by aggregating individual crimes occurring in each district of the County. HxGN OnCall Analytics | Power Visuals 647 Interfaces Locational Systems Interfaces Support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of trend analysis/forecasting HxGN OnCall Analytics | Dispatch Essentials 648 Interfaces Locational Systems Interfaces Access other RMS informational files to accommodate the needs and requirements of the crime analysis function and display this information using “pin mapping” techniques. HxGN OnCall Analytics | Dispatch Essentials Page 81 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E HxGN OnCall Dispatch Capabilities Matrix (2309) - On Premises Date: 12 April 2024 # Section Category Capability Product Name 649 Interfaces Locational Systems Interfaces Validate all incident locations, whether obtained from an E9-1-1 controller or entered directly by the call taker for administrative line (ten-digit) calls, against the CAD system’s geofile to provide, at a minimum, cross streets, response areas, map page and coordinate, legal street names, and zip code. HxGN OnCall Dispatch | Viewer 650 Interfaces Locational Systems Interfaces Allow for the manual processing of the incident location, in the event a location cannot be properly validated against the geofile, so that a CFS event can be created if the location has been confirmed or known to exist within the local jurisdiction. HxGN OnCall Dispatch | Viewer 651 Interfaces Locational Systems Interfaces Produce (automatically) a report of all incident entries that did not validate on a scheduled basis.HxGN OnCall Dispatch | Viewer 652 Interfaces Locational Systems Interfaces Save original E9-1-1 ANI/ALI information as part of the CFS event if the user changes the original information (e.g. the incident is not at the caller’s location). HxGN OnCall Dispatch | Call- Taker 653 Interfaces Locational Systems Interfaces Allow for processing of non-validated locations and notify the dispatcher of the special address.HxGN OnCall Dispatch | Viewer 654 Interfaces Locational Systems Interfaces Identify the appropriate agency (i.e. law enforcement, fire and/or EMS), district, sector, reporting area, agency of jurisdiction, and any other geographic boundaries containing an address, once it has been validated. HxGN OnCall Dispatch | Viewer Page 82 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 100 Attachment H – Interface Descriptions COTS Interfaces ANI/ALI Interface The ANI/ALI interface works with the Call-taker component of OnCall Dispatch Advantage to provide Next Generation support for solicited multimedia data associated with a call. Call-Taker is designed to support new modes of communication, such as SMS and MMS text (photos and video) and allows the addition of new call types going forward. It provides global support for handling Next Generation data processed by the PSAP. OnCall Dispatch supports FCC Phase II requirements for cellular 911 calls and supports the creation of events based on a geographic coordinate location. The ANI/ALI packets for Phase II Wireless 911 calls include the coordinates (in lat/long or other standard coordinate system, as dictated by the NENA standard or FCC requirements), and uses this information to show the caller's geographic coordinate location on the map. The nearest civic address can also be estimated and displayed. The exact format of this data in the ANI/ALI packet must be supplied by the Customer (in conjunction with their phone system supplier). Assumptions: Hexagon assumes that the Customer's ANI/ALI controller supports NENA Format Versions 1 and 2 (Fixed Length ASCII), NENA version 3 (Tagged Delimited), and NENA version 4 (XML). These formats are documented in NENA documents NENA 02—010 v9 now “Legacy Data formats for ALI, MSAG &GIS” and NENA 04-001 v2 now “E9-1-1 PSAP Equipment”. The ANI/ALI interface component of the OnCall Dispatch System will provide the interface to an ANI/ALI controller, and will accept ANI/ALI packets containing ASCII, tagged delimited, or XML data via an Ethernet Network (TCP/IP) or an RS-232 connection Hexagon assumes that the ANI/ALI protocol packet provides the number, address and answering position of the call when answered. The FCC order released June 3, 2005 requires that all VoIP vendors, serving U.S. customers, must offer service to route 911 VoIP calls through the current E-911 infrastructure. This means that all VoIP 911 calls from registered subscribers will be received through the PSAP’s 911 trunks and handled by their ANI/ALI Controller. The PSAP is responsible for ensuring that their ANI/ALI Controller is capable of handling the ALI Database lookup for these calls. ANI/ALI packets for VoIP calls will be received by the CAD system, over the same CAD link, from the ANI/ALI Controller, as the landline and cellular calls. VoIP calls with a caller’s address will be handled like landline calls and VoIP calls with a location specified by coordinates will be handled like Phase II cellular calls. If the center requires an interface to a method of receiving ANI/ALI or other Data for VoIP calls other than the traditional ANI/ALI Controller, this interface will have to be rescoped as a custom interface. The Customer must provide complete specifications of the device or service providing the data. Given the current uncertainty in the telephony provider market on how SMS/MMS information will be transmitted, Hexagon assumes that the SMS/MMS information is being provided through the external SMS provider. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 101 Constraints: The Customer is also responsible for the maintenance and support of any hardware, software, or cabling required to provide the physical interface between the ANI/ALI Communications Server and the ANI/ALI Controller. Hexagon’s demarcation point, for responsibility for the ANI/ALI stream, is at the port or socket on the communications server. The Customer must supply a complete and accurate description of the ANI/ALI controller interface and data it provides for CAD field mapping. HxGN OnCall Dispatch | Informer The Informer interface automatically routes queries and responses between clients and the external systems, and if the external database supports unique routing codes for each query and response, Informer may be implemented to automatically initiate queries in response to actions executed within the OnCall Dispatch system. For example, defining an event as a vehicle stop and entering the license tag number within OnCall Dispatch may automatically initiate the “Vehicle Query by License Number.” The product can be further configured to automatically enter all query results in a centralized server log, as well as to automatically attach query results to the event. Using the OnCall Dispatch messaging capability, responses may also be forwarded. Informer can be configured to use and display HTML forms on its front-end client application. Informer can display HTML, XML/XSL or plain ASCII text responses on that same client. Informer is comprised of user dialogs and service components. The service components are: A module that runs in the OnCall environment, A provider that directly interfaces to external systems, and A bridge that handles communication between the two. These services are orchestrated to route requests and responses between OnCall and the external systems. The services are architected so the module, bridge and provider can be configured to run in the cloud or on-premise. For example, OnCall and the module could be configured to run in the cloud with the bridge and provider configured to run on-premise to facilitate communications with the external systems. The user dialogs are a standard feature that work within OnCall Dispatch | Essentials and OnCall Dispatch | Advantage. When configured, these dialogs present the OnCall user with an Informer Message view that will allow them to submit requests and view responses. The dialogs component also supports a command line interface from within the OnCall Dispatch products. A set of configurable OnCall dialogs are provided which are used to collect request data and submit it to external systems. Hexagon has included the NCIC transactions as listed above in Task 16 Informer includes three providers that can be configured to communicate with external systems. These are: Open Database Connectivity (ODBC) CommSys In addition, Informer provides: Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 102 Explicit sign on and sign off using authorizations defined in the OnCall database Transaction level security, which verifies user authorization for each query type Hit detection that allows responses to be searched for specific text. If found, notifications can be automatically distributed based on configurable designations Informer currently supports XML responses in TCP/IP packets. Assumptions: Implementation of the CommSys provider requires at a minimum the purchase of the CommSys ConnectCIC module and CommSys' Real Time Data Mining (RTDM) feature. Additional provider implementations can be developed through extra services. The connection to a state or national database may require additional hardware and software. Connection through TCP/IP or Web Site is highly preferred. Each distinct provider requires OnCall Dispatch | Informer implementation installation and configuration services. A single license supports a given site. However, each distinct database connection requires custom OnCall Dispatch | Informer implementation development services. HxGN OnCall Dispatch | Fire Station Printing For Rip and Run The OnCall Dispatch | Fire Station Printing (FSP) Interface provides support for remote fire station turnout by printing run cards when units from a station are dispatched. The product can also be configured to print incident summary reports when units from a station are cleared from an incident. Assumptions: Hexagon assumes that the connection method for FSP is one of the currently supported connection methods and not through the radio system. The printer may be connected to a PC that is on the OnCall network or it may be a standalone printer directly connected to the OnCall network. In either case the printer should be dedicated to printing run-cards since there is no provision for interrupting the printer to print a run-card if it is being used for other purposes. Each distinct implementation to a different controller requires a separate copy of FSP and the associated services. FSP requires Xalt Integration as a prerequisite. Constraints: The Customer is responsible for providing any phone lines, modems, printers, PCs (in the fire station), or network hardware as needed. HxGN OnCall Dispatch | ProQA The OnCall Dispatch | ProQA Interface for Paramount application is a protocol-based product that provides a standard certified set of determination questions and answers that Police, Fire and EMS can use to identify the necessary resources required when responding to an event. OnCall Dispatch | ProQA Interface for Paramount is an add-in to the OnCall Dispatch | Call-Taker application (included with OnCall Dispatch Advantage). Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 103 Key Features: Multi-discipline launching Pre-alerts Transfer of location information to OnCall Dispatch | Call-Taker Configured to spill key questions into the Event information remarks field. We also provide a Pre-Alert capability, if ProQA is configured to send the chief complaint code and the answers to the initial questions to CAD before the user starts answering the Key Questions. CAD can then create the event or create and automatically accept the event dependent on the configuration. Per the Priority Dispatch Paramount website, Hexagon (as Intergraph Corporation) is listed at the platinum level. Upon determination by the operator that Paramount medical is needed, the operator clicks the Medical button, or issues the medical command. The interface brings the Paramount Medical application to the foreground and places focus in first editable control. The operator then progresses through the paramount application as normal. Upon reaching a determinant code, the operator clicks the flashing alert symbol in Paramount causing the data to be sent to OnCall Dispatch | Advantage. The Paramount application will populate location, caller information, an event-type and sub-type, and the key questions as configured by the Paramount medical admin utility, will spill into the event remarks. OnCall Dispatch | Advantage can optionally automatically accept the event or allow the operator to make further edits and then accept the event. The operator then places the event into update to allow Paramount to make any further changes as the operator completes the case in Paramount. Upon completion of the Paramount case, the operator would accept any changes into the OnCall Dispatch event. OnCall Dispatch records the Paramount case number as part of the event record so that the case is permanently linked to the event. If the Paramount button (or command) is clicked for an event that already had Paramount run against it, the case summary is displayed in Paramount. A single agency event can only have one Paramount case number associated with it. Assumptions: The OnCall Dispatch system supports ProQA version 13.0. SMS Texting is not currently supported for Paramount 5.1. HxGN OnCall Dispatch | CAD Link OneSolution RMS OneSolution FTO OnCall Dispatch | CAD Link interface will facilitate the automatic periodic transfer of event and unit information from OnCall Dispatch to external systems such as Police Records Management, Electronic Patient Care, and Fire Records Management systems using XML files ASCII delimited files. The third- party vendor (or the Customer) is then responsible for importing the information into the designated database. The CAD Link interface includes support for configurable event profiles; these are sets of event criteria for matching data field values within the OnCall events to be exported and a configurable target directory for Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 104 exported output files. The profiles act as event filters, determining which OnCall events are to be exported to which file system directories (inboxes). Assumptions: Hexagon assumes this is for the transfer of CAD event and unit data only to the specified systems. Additional services are required from the third-party vendor to consume and distribute the incident information provided via CAD Link. The Customer will be responsible for any data mapping The Customer will provide a technical resource as well as any necessary subject matter experts The Customer will provide a test system for installation and testing Hexagon will configure CAD Link to output to a single location where the Customer is responsible for consuming the data The Customer is responsible for ensuring that any third-party vendor technical resources are available to support the testing of this interface. Hexagon assumes that the third-party vendor will be utilizing XML protocols for this interface. This is a one-way interface. CAD Link exports OnCall Dispatch incident-related data, but it does not import data. Any import is the responsibility of Customer or of the third-party vendor. Constraints: OnCall Dispatch events must be closed before they are candidates for export by CAD Link. CAD Link does not provide features for obtaining "next available case numbers," "location verification," or any other OnCall Dispatch-related functionality or interface; it only provides export of specified event data for closed OnCall Dispatch events. HxGN OnCall Dispatch | Fire Link ESO FirstDue Firehouse Pagetrack Hexagon’s Fire Link product interfaces to various Fire RMS applications facilitating the automatic transfer of event and unit data from OnCall Dispatch generated during a Call for Service. The designated third- party RMS vendor (or the Customer) is then responsible for importing the information into the relevant fields/tables of the target database. Fire Link automates data transfers to the external system at periodic intervals as follows: Event information is generated when the first unit’s status changes to that specified by the user. Valid status changes include Dispatch, Enroute, OnScene, Transport, Transport Arrive and Clear. Unit information is generated for each unit whose status changes to that specified by the user. More than one status can be specified for sending unit information. Event information that includes event closing data, is generated when the event is closed. The Fire Link Interface is available in two options (if using more than one option, then a separate Fire Link Interface is required for each option): Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 105 Vendor-defined XML output to FIREHOUSE Software by ESO For the FIREHOUSE FireRMS interface, Fire Link will transfer event and resource data to FIREHOUSE’s Custom Hexagon CAD Monitor, which in turn will populate the FIREHOUSE RMS Database. This is an ASCII File Transfer. Standard XML output for all other FRMS vendors Assumptions: The transmission protocol between Fire Link and the remote FireRMS is TCP/IP. Fire Link interfaces to a single database. Fire Link requires Xalt Integration as a prerequisite. Constraints: The Customer is responsible for providing complete and accurate documentation on the systems to be interfaced. The Customer is responsible for acquiring and installing a data import capability into their current Fire RMS(s). For the interface to FIREHOUSE RMS, the Customer is responsible for providing the FIREHOUSE RMS communications and associated equipment. The Customer is also responsible for acquiring and installing the Custom Hexagon CAD Monitor data import capability into their current Fire RMS. Hexagon cannot be held accountable for incompatibilities in its interface which are due to changes in input/output formats or data requirements of the vendor’s product. HxGN OnCall Dispatch | Tracker For radios HxGN OnCall Dispatch | Tracker accepts incoming Global Positioning Satellite (GPS) data directly from a GPS device, location servers or mobile data devices. HxGN OnCall Dispatch | Tracker functions as an extension to the dispatch environment, periodically updating vehicle and personnel locations in OnCall maps and monitors. Supported GPS Devices: Devices running Mobile Unit or Mobile Responder Radios transmitting GPS data in the following message formats Trimble TAIP messages, UDP connection NMEA messages, UDP connection OpenSky messages, UDP connection Harris GPS Radio Types M-803, M5300, M7200, M7300, P5400, P5500, P7200 transmit OpenSky GLR1/GLP1 messages over UDP OMA/MLP (web service) Non-Supported GPS Devices Smartphones not running Mobile Responder or Mobile Unit Harris radios that do not support OpenSky messages Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 106 M7100, P7100, XG-100M, XG-75, XG-100P Certain GPS devices also accept commands from external systems to control the frequency of location reports. HxGN OnCall Dispatch | Tracker can be configured to send the appropriate commands to these devices, setting the frequency of location reports based upon unit type, unit status, and the type of event the unit is currently assigned to. When OnCall Dispatch | Tracker is used with our mobile solution on MDCs, Mobile Unit uses the in- vehicle map and high-speed access to the GPS receiver to match the vehicles route to the map to determine the address of the vehicle. This approach is necessary because mapping information is seldom as accurate as the GPS device. The map is often several hundred feet off from the true location. This approach is more accurate than the more common method of using a server to attempt to place a point on the map based on a single position report. The computed location is used to pre-populate forms requiring a location such as on-view incidents and unit emergency. The officer can override the location if required as a final check before submitting the command. The selected GPS receivers may support commands to change their delta time and/or delta distance reporting rates dynamically. AVL information may be used in the CAD system in the Recommend Unit processing. Depending on the existing AVL solution, the OnCall Dispatch | Tracker interface supports three different modes of operation: passive, poll, and poll list: Passive mode interfaces to a radio system, data terminal system, or location server and directly receives location reports from radio, MDT, or GPS devices. In the passive mode, OnCall Dispatch | Tracker exerts no control over the behavior of the location reporting devices and only receives these location reports, processes their contents, and forwards them to OnCall Dispatch when needed. This mode is useful when the devices are not capable of responding/honoring the poll rate commands that are issued to them from OnCall Dispatch | Tracker. This mode is also used when the GPS devices in service are capable of regulating their own polling. In poll list mode, OnCall Dispatch | Tracker may interface with a location server or controller; that is, a software/hardware solution that performs the actual polling of vehicles and devices. The location server/controller may also perform other functions, such as differential correction. This could be some software application running on a different server (Windows, Linux, and so forth) or some other type of hardware controller (a “black box”) that communicates with the devices OnCall Dispatch | Tracker needs to set the poll rates for. In this mode, OnCall Dispatch | Tracker does not communicate directly with these devices but instead goes through an intermediate “solution” that communicates with the devices. Essentially, this is an indirect mode of communication where OnCall Dispatch | Tracker must go through third-party “solution” to communicate with the devices. OnCall Dispatch | Tracker builds a list of devices internally that it packages up and sends to the location server or controller (“solution”) when it sets poll rates in the “poll list” mode. All devices are then divided among poll groups which are configured in the AVL Poll Group dialog. OnCall Dispatch | Tracker assigns each unit to one of these poll groups based on specified parameters of the unit. As in the poll mode, these may include a unit’s type (agency/dispatch group), unit status, event type and/or last reported velocity. Each poll group has an associated polling interval. For example, a poll group may be defined to be all vehicles whose status is ‘ON SCENE’ and whose last reported velocity is less than 10 miles per hour; the polling interval for this group could be set to 600 seconds (10 minutes). When OnCall Dispatch | Tracker determines that the last location report for a vehicle in this polling Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 107 group is more than 10 minutes old, it will generate a new poll request to the controller. The poll group with the largest polling interval defines the maximum polling cycle for the fleet. The poll list mode is used to minimize the contention for radio frequency bandwidth. The location server/controller sends out the location queries to each device in the polling list along with a time- slot during which it expects to receive the corresponding location report. In this manner, the controller seeks to guarantee that no two vehicles will attempt to transmit a location report simultaneously. Poll mode requires the devices to be programmable by an external source. This programmability allows the reporting behavior of the device to be by varying parameters, such as delta distance and/or delta time that are transmitted directly to each device. In poll mode, all devices are divided among a certain number of poll groups. OnCall Dispatch | Tracker assigns each unit or device to one of these poll groups based on certain parameters of the unit. OnCall Dispatch | Tracker actively changes these parameters by assigning new values based on a unit’s type (agency/dispatch group), status (Available, On-Scene, and so forth) and an event type. For systems that include velocity in the location report, the last reported velocity may also be used to determine the location reporting behavior. Assumptions: Licensing is by device OnCall Dispatch | Tracker is a zero-cost product when bidding Hexagon mobile clients (Mobile Unit and Mobile Responder) Pricing is only required when connecting to non-Hexagon devices such as radios and third party mobile clients OnCall Dispatch | Tracker must be installed and licensed to track any device even if there is no cost to the Customer The OnCall Dispatch | Tracker interface establishes communications between a third-party AVL controller/message switch and the OnCall Dispatch System. Hexagon assumes that communication with the AVL controller/message switch will be achieved via TCP/IP or serial line (RS-232) communication protocol. The OnCall Dispatch | Tracker interface supports NMEA, OpenSky, BlueTree, Sierra Wireless RNAP, and TAIP protocols and devices that support these protocols should be compatible with OnCall Dispatch | Tracker. If the Customer is currently running AVL hardware that OnCall Dispatch | Tracker does not support, additional services must be purchased to develop a custom AVL interface. Hexagon recommends that the Customer purchase a device such as the Sierra Wireless, Trimble TrimFleet, or Airlink modems that supports one of the above protocols. Hexagon assumes that the Customer uses one of the supported GPS Receiver/Systems. If the Customer requires Hexagon to interface to a GPS Receiver/System that is not supported, additional development services will need to be quoted. Constraints: The Customer is responsible for providing Hexagon with a complete and accurate description of the interface to the AVL controller/message switch. If the Customer has AVL hardware that OnCall Dispatch | Tracker currently does not support, Hexagon reserves the right to bid additional services to develop a custom AVL interface. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 108 Hexagon cannot be held accountable for incompatibilities that occur in this interface as the result of changes to input/output formats or data requirements associated with the third-party vendor’s product. HxGN OnCall Dispatch | Notifications For PageGate OnCall Dispatch | Notifications provides connectivity between the dispatching environment and multiple internal and external communication endpoints. It allows for the definition of customer-specific rules for notifying interested parties based on activities in the CAD system. These include a third-party paging controller, email application, and SMS text. Dependent on the protocol supported by the system, OnCall Dispatch | Notifications uses either SNPP level 1 (Simple Network Paging Protocol), SMPP (Short Message Peer to Peer), SMTP (Simple Mail Transfer Protocol), or WCTP (Wireless Communication Transfer Protocol). This product serves as an extension to the OnCall Dispatch functionality. Alphanumeric messages and/or tone pages can be transmitted from the dispatch environment over the third-party paging terminal to the destination paging unit. OnCall Dispatch | Notifications must be customized to adapt to the third-party paging terminal available. Notifications may be sent through the OnCall messaging system, which supports group messaging and logs messages sent, or may be sent automatically when a unit is dispatched to an event. The OnCall Dispatch | Notifications interface provides the ability to send information or general tone alerting from the OnCall Dispatch system to pagers and units equipped with pagers as well as email. The system can send general text and dispatch/event information to alphanumeric pagers and units equipped with alphanumeric pagers. Tone-only pagers can also be used for ‘tone out’ type pages. Because most paging systems only support one-way communications, OnCall Dispatch | Notifications cannot confirm receipt of a message but can confirm that the paging controller acknowledged the message. The SMTP software driver module (SDM) provides the ability to send email messages. The SMTP SDM will distribute paging messages as directed by the paging system interface (PSI) application. The PSI application is designed to listen for Send Message packets from Hexagon’s CAD software application (OnCall Dispatch). Once the PSI application captures a Send Message packet, it forwards the message and its contents to the SDM of interest. The SMTP SDM is an integral part of the complete PSI application and its inclusion helps to complete the functionality for a working paging system interface to the OnCall Dispatch application. The OnCall Dispatch | Notifications interface consists of three parts: The User Interface portion (client) Communication server paging process (server) Controller/hardware specific driver software (SDM) necessary to control communication to a particular paging system controller All run time input to the paging system will come from the OnCall Dispatch system. Automatic dispatch paging is only by unit within the OnCall Dispatch system. Pagers may be associated with: Units Personnel Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 109 Stations Functionality includes three (3) basic functions: 1 Automatic Dispatch Pages ─ Automatic sending of dispatch messages or tone alerts to appropriate pagers associated with units during a normal dispatch. Dispatch messages sent by OnCall Dispatch workstations will be analyzed and processed for paging units equipped with pagers. This is an automatic feature. Once a dispatch packet is received, the paging server will use the unit ID in the packet to look up the pager ID from the OnCall Dispatch Database. Therefore, only logged-on units can be sent dispatch pages automatically. This pager ID will be used to match records in other page-related tables to locate the actual device specific code to be sent to the proper paging controller. Additionally, dispatch related conditions can be placed against these pages for conditional paging. Entering Messages through Send Message ─ Manually sending user-entered text or pre- formatted text messages to alphanumeric pagers. Through the Send Message dialog box in OnCall Dispatch, users may manually enter or use pre-entered, pre-formatted messages to be sent to alphanumeric pagers. A pick list of pre-formatted messages can be configured. As these messages are manually entered and not the result of a dispatch operation, these type pages do not have conditional capabilities. For example, all pager IDs entered or resolved from a unit ID will be paged. Manually Sending Dispatch or Event Info ─ Manually sending dispatch or event information to alphanumeric pagers. The paging interface can also re-send dispatch type pages to alphanumeric pagers via the Send Message dialog box in OnCall Dispatch. By selecting or entering an event number, the software will build a dispatch page just as it does for the actual dispatch. This text message can then be modified or amended prior to sending the message. Because this is a manual page and not the result of a dispatch, no conditions capabilities can be evaluated for the individual page IDs. Assumptions: Hexagon assumes that the paging system uses one of the supported protocols. Each license of OnCall Dispatch | Notifications allows any number of potential pagers. The connection of the Paging Controller is assumed to be RS-232 or Network based (TCP/IP). Connection may be made through a dedicated or dial up line. Hexagon assumes use of a single paging controller type. If additional controller types are used, Hexagon’s bid must be re-evaluated. OnCall Dispatch | Notifications currently does not support voice paging; it only supports alphanumeric text. Hexagon assumes the Customer is responsible for providing any phone lines, modems, internet connections, etc. required to establish the connection with the paging terminal(s). Constraints: Each distinct paging controller type requires a separate license of OnCall Dispatch | Notifications. However, the Customer may implement multiple paging providers using the same protocol, and these would be considered a single paging controller for licensing purposes. SMTP provides the ability to send email messages and is the link between the Microsoft® Windows® Exchange server and the OnCall Dispatch | Notifications system. OnCall Dispatch | Notifications does not support bidirectional communications. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 110 The Customer is responsible for providing complete and accurate documentation for the paging system interface. Hexagon cannot be held accountable for incompatibilities that occur in this interface as the result of changes to input/output formats or data requirements associated with the third-party vendor’s product. Avigilon VMS Interface Hexagon will develop a custom interface to meet this requirement. This interface requires the following Hexagon Products: HxGN Video Streamer (each separate VMS requires a license of Video Streamer) Avigilon VMS Interface HxGN OnCall Video Responder This interface also requires the following: .Net 6.0.21 or later installed on the computer that will host the Configuration Server. PostgreSQL 15.3-3 full version. PostgreSQL 15.3-3 Command-line Tools on the computer where the Streaming server will be hosted. Video output must be to be an h.264 over RTSP stream. Controls include the following: Stream live video Pan-tilt-zoom (PTZ) Controls Device auto discovery is not included in this effort. Instructions for bulk loading devices through a CSV template will be provided to the customer and the customer will be responsible for providing that information prior to implementation of the Video Streamer solution. Standard Interfaces RapidSOS OnCall Call-Taker Interface The RapidSOS OnCall Call-Taker Interface is an OnCall Call-Taker direct link based interface, for the purpose of receiving location accuracy information from the caller’s device about the caller and offer updates on demand via the RapidSOS Web Portal. The interface will also support launching the RapidSOS portal using the phone number as a parameter to obtain additional information about the caller if desired. Assumptions: Call-taker interface requires OnCall Dispatch | Call-Taker (included as a component of Dispatch Advantage) as a prerequisite. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 111 Hexagon has also included pricing for the “connector” between RapidSOS and the Call-Taker Interface API (HxGN OnCall Dispatch | Call-Taker Interface) Fire Station Alerting OnCall Dispatch Interface The Fire Station Alerting OnCall Dispatch Interface provides support for third-party Fire Station Alerting Solutions. The Interface sends unit and event information to the Fire Station Alerting solution to trigger station alarms, unit dispatch, and other services provided by the vendor as defined by their API. Where appropriate, this interface can be configured to be bi-directional to record alert acknowledgements either by message to the dispatcher or logged to the event remarks. Vendors supported in this product include: US Digital Design’s Phoenix G2 (Version 2.5) Purvis (Version 2.1) Westnet FIRST-IN (API Version 1.0.6. 1.0.7, 1.0.7a and 1.0.8) Assumptions: The Fire Station Alerting software will support sending a notification of alert failure to the event remarks. If there is a method for station crews to submit an acknowledgement of the alert manually, and the Phoenix G2 can send that acknowledgement to the interface, the interface will change the unit status from Dispatched to Acknowledged. Constraints: The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. PLT OnCall Dispatch Interface The PLT Radio OnCall Dispatch Interface is an integration between Hexagon OnCall Tracker and a P25 Radio System to support receiving GPS data from the radio systems and report them to OnCall Dispatch as Tracker messages. This functionality is specific to the Person Level Tracking (PLT) Features in OnCall Dispatch. This functionality requires that the Motorola ASTRO P25 radio controller utilizing the LRRP MUPS API over UNS servers be installed prior to Hexagon implementation services. If Customer requires interfacing to Motorola via Motorola's IMW Web Service, enhancement development may be required as well as obtaining permission from Motorola specifically for each customer/agency. The vendors supported are: Motorola ASTRO P25 Harris StatusAware P25 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 112 Assumptions: Additional third-party licensing may be necessary; the Customer should consult with their radio provider for additional information. The XML format required by the external systems must be provided to Hexagon. Constraints: The Customer is responsible for providing complete and accurate description of the API needed to interface, and for any software/hardware/data required to implement communications with the external systems. External Alarms OnCall Dispatch Interface The APCO ASAP Standard is supported with this interface. It allows OnCall to interface with the APCO International Automated Secure Alarm Protocol (ASAP) Alarm System (also called “ASAP to PSAP”). The Automated Secure Alarm Protocol (ASAP) program is a computer-aided dispatch system designed by the Central Station Alarm Association (CSAA) and the Association of Public Safety Communications Officials (APCO Int'l). Because ASAP Alarm system operates on the National Law Enforcement Teletype System (NLETS) backbone – state specific development services may be required for each implementation to convert the APCO standard NLETS message into the State CJIS Message Switch format. This interface requires CommSys ConnectCIC with ASAP Option and consulting services from The Monitoring Association (TMA) through CommSys. TMA requires a test connection license of ConnectCIC to support post production testing and modifications from TMA's alarm (i.e. changes to alarm payload, addition or removal of participating Alarm vendors or central monitoring stations) Assumptions: Hexagon has also proposed consulting services for the Customer to coordinate deployment with the Monitoring Association directly. Custom Interfaces Text to 911 Hexagon will develop a custom interface to meet this requirement. Assumptions: This interface requires OnCall Dispatch | Call-Taker Interface and Vesta i3 Event Viewer log interface API/SDK. The Customer is responsible for obtaining licensing from Vesta/Motorola for API/SDK. The Customer responsible for any costs associated licensing from Motorola/Vesta. Interface is limited to the capabilities identified in the Vesta i3 Event Viewer log interface API/SDK for supporting ANI/ALI spill, plus SMS/MMS to 911. Video calls to 911 are not supported at this time. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 113 Query to OneSolution CAD Hexagon will develop a query interface to the Customer’s legacy OneSolution CAD via the Informer interface. Queries supported include Person (by name/date of birth or OLN), Vehicle (by plate or VIN), and Location (street address or commonplace name). Assumptions: The system supports an ODBC connection, SQL-based inquiries or HTTP/REST connection. The Customer will provide the exact SQL or GET syntax for the three inquiries listed. This is required during the Custom Interface Requirements Gathering Task. Nested inquiries are excluded. Images are excluded. Test records will be provided by the Customer/Legacy CAD system technical point of contact. This is required during the Custom Interface Requirements Gathering Task. Test records will return production-equivalent response data. Response examples will be provided during the Custom Interface Requirements Gathering Task. A test connection/environment will be obtained by the Customer before the scheduled interface delivery milestone. Query to OneSolution RMS Hexagon will develop a query interface to the Customer’s OneSolution RMS via the informer interface. Assumptions: The following inquiries are included: Person Inquiry by (NAM, DOB, SEX) or (OLN), State Vehicle Inquiry by (LIC), State Gun Inquiry by SER, MAKE, Caliber, Model Article/Property Inquiry by SER, MAKE, MODEL The system supports an ODBC connection, SQL-based inquiries. The Customer will provide the exact SQL for the inquiries listed. This is required during the Custom Interface Requirements Gathering Task. Nested inquiries / follow up inquiries are excluded. Images are excluded. Test records will be provided by the customer/ ODBC system technical point of contact. This is required during the Custom Interface Requirements Gathering Task. Test records will return production-equivalent response data for each inquiry. The data requested in the select statements for the listed inquiries will not exceed the maximum number of fields listed below: Person Inquiry: 20 fields Vehicle Inquiry: 20 fields Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 114 Gun: 8 fields Article/Property: 8 fields The inquiries will be supported from the Person, Vehicle, Article, and Gun forms that are included in the interface for OnCall Dispatch Informer and Mobile Unit. No additional forms are included in this bid to support the inquiries. SQL and response examples will be provided during the Custom Interface Requirements Gathering Task. This is required before software development begins. A test connection, including a compatible ODBC driver, will be obtained by the Customer before the Custom Interface Product Installation and Configuration Task. Consulting Services Eventide Recording Hexagon will provide consulting services to advise Eventide on how to use RestAPI to pull the data they require. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 115 Attachment I – Glossary of Terms Capitalized terms that are not defined below or within the body of the SOW, shall have the same meaning as set forth in the Master Terms Glossary. “Acceptance” to mean acceptance of a Task in accordance with Task Acceptance Process. “Agreement” shall have the same meaning as set forth under the header “Terms and Conditions.” “Benchmark Criteria” or “Specifications” means the objective criteria which identifies an intended outcome as reflected in, as applicable, an ICD, a Design Document, or Software Requirements (whichever document having last addressed the functionality in question being dispositive) “Blocker Defect” means a Test Case has failed to satisfy the Benchmark Criteria that would correspond to a Level One Defect or Level Two Defect, or a Level One or Level Two Defect. “Code Freeze” means a point in the Project where Customer may not make any change, configuration change, or other modification to the Software implemented as part of the Project. “Core Team(s)” means all of the respective Subsystem Core Teams pertaining to the Project, which depending on the Project will collectively include: the Dispatch Core Team, and the Mobile Core Team(s). “COTS Interfaces” means those Interfaces specifically identified in COTS Interface Questionnaire Completion Task in the SOW “Customer Responsibilities” means (1) those specific tasks and obligations identified in the SOW as being the responsibility of the Customer and (2) those obligations, not stated in the SOW, but which would otherwise be reasonably considered as being Customer obligations and responsibilities. “Custom Interfaces” means those Interfaces specifically identified in the applicable Task “Customization” means a modification of the source code of Software. “Cutover Plan” means a document reflecting the Activities and actions necessary to Cutover the System. “Design Document” means a document articulating the design and intended output of a Customization. “Documentation” means, whether in printed or electronic format, all documents (digital or hardcopy) delivered by Hexagon as part of the Project. Unless otherwise specified, it shall mean COTS Documentation. “End User License Agreement” means the End User License Agreement set forth at https://legaldocs.hexagon.com/sig/Licenses/EULA_SA_SIG-Eng_062023.pdf, which is incorporated by reference herein. “Facility” means a Customer provided facility/building/room that: (i) Can accommodate up to twelve (12) Customer participants; (ii) Has a projector and screen for displaying the content being presented, (iii) has Project Workstations for each participant; and a Customer workstation available for Hexagon’s use while in the Facility. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 116 “Functional Testing” means that testing process described in the Customer Functional Testing Task(s). “GIS” means geographic information system “Initial Schedule” means the initial iteration of the Project Schedule, which is contained in Attachment C of the SOW. “Interface Control Document” or “ICD” means a document reflecting the design and requirements of a Custom Interface or certain I/Informer Interfaces, if any. “Help Desk Portal” the electronic portal through which Customer may access the Help Desk to among other actions, log Services Requests, review the Knowledge Base, “Hexagon Project Manager” means the person authorized by Hexagon to coordinate and manage the providing of Hexagon Services and Deliverables for the Project on behalf of Hexagon, in addition to being responsible for other duties specified in the Agreement and SOW. “Master Terms Glossary” means that certain Common Terms Glossary set forth at https://www.hexagonsafetyinfrastructure.com/-/media/Legal/Hexagon/SI/TPS/CTG 06-2021.pdf “Network Infrastructure” means the provision of adequate network and internet connectivity to provide sufficient operational bandwidth for the operation of the System in a manner consistent with the Product System Specifications together with all industry-standard network security, monitoring, and protection. “Permissive Defect” means a substantially failed Test Case that would correspond to a Level Three or Level Four Defect, or a Level Three or Level Four Defect. “Project Assumptions” means assumptions regarding the Project, which are listed in the SOW. Changes in any of the assumptions will affect the scope, schedule, and/or cost of the Project. “Project Team” means the applicable Core Team and other resources assigned to provide information or services in connection with the Project, or applicable part thereof. “Project Workstation” means a computer workstation (expressly excludes tablets or other smart devices) that has: (i) a modern web browser installed and ready for use; (ii) Internet access; (iii) at least one (1) external monitor with a resolution no smaller than 1920x1080 (understanding two (2) external monitors are recommended); (iv) the ability to connect to the web conference audio; and (v) a headset. “Required Facilities” means a facility provided by the Customer that: (i) can accommodate up to twelve (12) Customer participants with workstations and monitors meeting the specifications for the Software described herein for each participant and (ii) has a projector and screen for displaying the content being presented. If the Customer’s policies preclude connecting Hexagon-owned equipment to their network, a computer workstation for use by Hexagon for presenting content shall be made available. “Server Setup Worksheet” means a document reflecting, among other details, the identification of servers, IP addresses, and node names for the System. “Site Configuration Document” means a document reflecting the configurations made to the OnCall System. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 117 “Software Requirements” means the functionality and capabilities affirmatively included in the OnCall Software as expressly specified in OnCall Functional Matrix (Attachment G, as appropriate to the Subsystem). “SR” or “Service Request” a request logged into Hexagon’s Help Desk Portal identifying a request for Hexagon to address a Defect, question, provide an Update, or provide an enhancement request, among other requests. “Subject Matter Expert” or “SME” means a person(s) who has particular knowledge about a specific topic(s). “System Administrator(s)” means a person or persons having the appropriate education, training, and/or experience in information technology to provide first tier support of the System. “Task Prerequisites” means those events, deliverables, or accomplishments that are required to occur prior to the commencement of the applicable Task, except as may otherwise be agreed to through Conditional Acceptance. “Test Case” means a set of conditions and parameters agreed to by the Parties which the Parties shall use to test whether the intended functionality identified in the Benchmark Criteria is reflected in the System. “Test Case Failure” means a situation in which an executed Test Case has substantially failed in meeting the passage criteria set forth in the applicable portion of the Benchmark Criteria. “Updated Initial Project Schedule” means the Initial Project Schedule updated by the Parties’ Project Managers during Project Kickoff Meeting Task and reflecting the actual Notice to Proceed date. “VPN” means virtual private network. “Warranty Period” means that one (1) year period beginning at Cutover for a Subsystem during which the applicable Project Software is subject to the warranty described in Attachment K. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 118 Attachment J – GIS Requirements for the HxGN OnCall Dispatch System HxGN OnCall Dispatch requires integration with a third-party mapping provider for GIS information. These third-party mapping services fall into three (3) main areas: Map Tile Services, Geocoding Services, and Routing Services. The selection, provisioning, and administration of its mapping services configuration of its map, maintenance and support of its map, and adherence to the requirements set forth herein is the responsibility of Customer. Hexagon shall not be responsible for resolving or addressing issues or Defects arising from Customer’s non-conformance with requirements contained herein. Map Service The map contains the area of responsibility for the dispatch system and is accessed by HxGN OnCall Dispatch through published map web services. Many maps may be accessible and configured as base maps and/or translucent overlays to the base maps. The GIS provider will be responsible for providing map services. Customer shall utilize one of the following mapping services: ArcGIS, Bing, Tile Map Services, WMS, and WMTS. These services must be configured by the Customer or its mapping services provider in a highly available manner. An interruption in availability of these map services will negatively impact the availability of the map, routing or geocoding within the System and its resulting performance. Geocoding/Address Locator Service A Web geocoding service resolves address strings and street names to longitude/latitude coordinates (geocoding) and returns an address string for a point selected from the map or precision coordinate key- in (reverse-geocoding). The Customer and/or its mapping services provider will be responsible for providing geocoding services. The Customer shall utilize one of the following mapping services: ArcGIS, Bing, and Pelias, supported for geocoding services. These services must be configured by the Customer or its mapping services provider in a highly available manner. An interruption in availability of these geocoding services will negatively impact the availability of the address verification within the System and its resulting performance. Additionally, the network latency, which is the responsibility of Customer, between the System and the mapping services shall be thirty (30) milliseconds or less on all requests to this service. Routing Service A routing service is used to determine the best route between two (2) or more points on the map based on time and distance. The routing service can also return driving directions for the calculated route. Some services have the capability to react to real-time traffic conditions, thereby increasing the accuracy of route results and providing more efficient workflows which strive to mimic real world conditions. The Customer and/or its mapping services provider will be responsible for providing routing services. Customer shall utilize one of the following mapping services: ArcGIS, Bing, or Valhalla. This service must be configured by the Customer or its mapping services provider in a highly available manner as an interruption in availability of this routing service will negatively impact the availability of the routing service including unit recommendations within the System and its resulting performance. Additionally, the network latency, which is the responsibility of Customer, between the System and the mapping services shall be thirty (30) milliseconds or less on all requests to this service. Hexagon requires the Customer to provide a set of services that are dedicated for the purpose of supporting the OnCall environment. While the environment may be similar in some respects to existing Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 119 environments in place by the Customer, OnCall requires a dedicated environment to mitigate potential performance and reliability issues that could arise due to other users accessing a shared environment. Hexagon’s Services expressly exclude ESRI related services, including, but not limited to, building or modifying of ESRI environments, providing consulting services related to ESRI environments, or other services related to ArcGIS software. The Customer is solely responsible for the use and creation of ArcGIS environments in conjunction with OnCall Dispatch. As you leverage ESRI as the mapping solution to integrate with OnCall, Customer may at its discretion seek additional guidance from ArcGIS professionals, materials published by ESRI, including the following link (https://enterprise.arcgis.com/en/server/latest/deploy/windows/single-machine-high-availability-active- active-deployment.htm) related to building a highly available GIS solution, or other appropriate resources. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 120 Attachment K – Warranty Pursuant to the GSA Contract, Hexagon warrants the Hexagon Software provided in this Order shall materially conform to its Specifications for one (1) year from Cutover of the applicable Subsystem, provided that in the event of a nonconformity during the Warranty Period, Hexagon shall address the reported Defect in accordance with below. Support Provisions Should a Defect arise, Hexagon shall provide support as follows, which represents the exclusive remedy of any Defect occurring during the Warranty Period. During the Warranty Period, Hexagon shall provide Maintenance Services consisting of the following. Reasonable commercial efforts to aid in the diagnosis of Defects are included within Maintenance Services. Hexagon shall provide reasonable commercial efforts to aid in correction of Defects. Defect corrections provided by Hexagon shall, unless otherwise agreed by Hexagon, be delivered within Hexagon’s product releases, and in accordance with Hexagon’s standardized release cycles. Additionally, the following are available during the Warranty Period: Out-of-the-box functionality support via the support help desk (telephone or eService via the Designated Portal; and, access to any available Hexagon problem knowledge base online self- help tool. Phone support is available Monday through Friday from 0700-1700 Central Time, excluding Hexagon-observed holidays provided that for Level One Defects, telephone support is available at all times of the day, including holidays and weekends. Access to available Updates of Covered Software Products. Hexagon will notify through the Help Desk when Updates are made available for any Covered Software Products. Updates are shipped to Customer upon Customer’s request logged in the Designated Portal site. Hexagon is not obligated to produce any Updates. For avoidance of doubt, a Customer’s entitlement to Updates shall not include entitlement to any therein embedded or otherwise related module or function which is licensed and priced separately from Covered Products for which Customer has purchased an entitlement to Updates. Provision of support during the Warranty Period is conditioned upon the following: System Requirements. Customer is responsible for ensuring: the System Equipment and Network Infrastructure meet minimum system requirements specified by Hexagon and provided as Attachment E; its systems, software, and data are adequately backed up. Customer will permit Hexagon to electronically access Customer’s system via Secure Access Tool. Customer will ensure availability of its own system technical support personnel so that Hexagon can fulfill its Maintenance Services obligations. When reporting problems to Hexagon’s support help desk, Customer will provide a complete problem description, along with all necessary documents and information that is available to Customer and required by Hexagon to diagnose and resolve the problem. Customer will grant all necessary access to all required systems as well as to the Covered Products, and any other reasonable assistance needed. Customer will carry out any reasonable instructions and will install any necessary patches, Defect corrections, or Updates. Customer will appoint a minimum of two and a maximum of five contact people who are each authorized to make use of the Maintenance Services (“Authorized Contacts”). Customer is obligated to select only those personnel for this task who are suitable for it by means of training and function, and who have knowledge of Customer’s operating system, network, and hardware and software. Customer agrees to promptly notify Hexagon of any Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 121 replacement of an Authorized Contact. Customer must ensure Authorized Contacts have adequate expertise, training, and experience to provide professionally accurate descriptions of malfunctions and facilitate Hexagon’s efficient response. Authorized Contacts must have successfully completed Hexagon product training as provided in the Project. Customer will enter and/or log requests for assistance in such systems, and utilizing such forms, as Hexagon may designate from time to time. Response Times. The following reflect the response times corresponding to the Defect classification. Priority Response Time Level One Immediate or within 30 minutes of notification Level Two Within one hour of notification Level Three M-F, 7:00AM-7:00PM Central Time – Immediate* or within eight hours of notification during normal business hours Level Four M-F, 7:00AM-7:00PM Central Time – Immediate* or within eight hours of notification during normal business hours Exclusions The following are outside the scope of the Maintenance Services provided during the Warranty Period: Installation of any Covered Product, Update, or interface software; Network configuration; Configuration or customization of Covered Products to Customer or other third party requirements (except as necessary to remedy a Defect); System-level tuning and optimization and system administration support; Training; Services required because the Authorized Contact is not available or is not trained; On-site services (unless waived by Hexagon, in its sole discretion); Services required due to modifications of Covered Products by Customer; Services required due to use other than in the ordinary manner intended for the Covered Products, or use in a manner that contravenes terms hereunder, or Customer’s disregard of the installation and operating instructions according to the Documentation provided with the Covered Products; Services required due to failure of software or hardware that is not a Covered Product; Services required due to Customer’s use of hardware or software that does not meet Hexagon specifications or failure of Customer to maintain or perform industry standard maintenance on Customer’s hardware or software; Services required due to software or portions thereof that were (i) incorrectly installed or configured (other than by Hexagon), (ii) used in an environment inconsistent with the support Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 122 environment specified by Hexagon, and/or (iii) used with peripherals, operational equipment or accessories not conforming to Hexagon’s specifications; Services required due to cases of force majeure, especially lightning strikes, fire or flood, third- party criminal acts, or other events not caused through Hexagon’s fault; Services required due to Customer’s failure to fulfill the Customer Obligations; and/or Services required due to faulty or incomplete Customer data. Disclaimer Any product information Hexagon has shared with Customer during the proposal and/or contract activities to date was to provide an understanding of Hexagon’s current expected direction, roadmap, or vision and is subject to change at any time at Hexagon’s sole discretion. Hexagon specifically disclaims all representations and warranties regarding future features or functionality to be provided in any Software or Deliverable(s). Hexagon does not commit to developing the future features, functions, and/or products discussed in this material beyond that which is specifically committed to being provided by Hexagon pursuant to a valid Order. Customer should not factor any future features, functions, or products into its current decisions since there is no assurance that such future features, functions, or products will be developed. When and if future features, functions, or products are developed, they may be made generally available for licensing by Hexagon. EXCEPT AS SPECIFICALLY SET FORTH IN THIS ATTACHMENT OR THE GSA CONTRACT, HEXAGON DISCLAIMS (TO THE FULLEST EXTENT PERMITTED BY LAW) ALL WARRANTIES ON PRODUCTS FURNISHED PURSUANT TO THE AGREEMENT, INCLUDING ALL WARRANTIES OF MERCHANTABILITY, DURABILITY, FITNESS FOR A PARTICULAR PURPOSE, HIGH RISK USE, AND NON-INFRINGEMENT. ALL WARRANTIES PROVIDED PURSUANT TO THIS MASTER AGREEMENT ARE VOID IF FAILURE OF A WARRANTED ITEM RESULTS DIRECTLY OR INDIRECTLY FROM AN UNAUTHORIZED USE OR MISUSE OF A WARRANTED ITEM, INCLUDING, WITHOUT LIMITATION, USE OF A WARRANTED ITEM UNDER ABNORMAL OPERATING CONDITIONS OR UNAUTHORIZED MODIFICATION OR REPAIR OF A WARRANTED ITEM OR FAILURE TO ROUTINELY MAINTAIN A WARRANTED ITEM. THE WARRANTIES SET FORTH IN THIS ATTACHMENT ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED AND REPRESENT THE FULL AND TOTAL WARRANTY OBLIGATION AND/OR LIABILITY OF HEXAGON. HEXAGON DOES NOT WARRANT THAT ANY COVERED PRODUCTS AND UPDATES PROVIDED UNDER THIS WARRANTY WILL MEET CUSTOMER’S REQUIREMENTS OUTSIDE OF THE BENCHMARK CRITERIA, AND UNDER NO CIRCUMSTANCES DOES HEXAGON WARRANT THAT ANY COVERED PRODUCTS AND UPDATES WILL OPERATE UNINTERRUPTED OR ERROR OR DEFECT FREE. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 123 Attachment L – Regional Provisions The following terms, including any sub-attachments to this Attachment L, modify provisions set forth above to accommodate regional requirements. To the extent there is any conflict between the terms specified below and the terms set forth in the remainder of the SOW, the following shall control. 1. A Business Day includes up to eight (8) Business Hours, including breaks, during a twenty-four (24) hour period. 2. Upon Customer request, Hexagon personnel may undergo a criminal background check consisting of biographical information necessary to initiate an NCIC query and fingerprinting. To the extent the Customer requires Hexagon personnel to undergo such criminal background check, the Customer shall arrange for such criminal background check and fingerprinting and be responsible for all costs associated with the criminal background check and fingerprinting. Any remote personnel shall only be required to provide biographical information necessary to initiate a NCIC query and a fingerprint card completed by any law enforcement agency. 3. Per CJIS security policy, customers who wish to access U.S. national databases using mobile devices must use data encryption that is FIPS 140-2 certified and meets other CJIS requirements. The Customer is responsible for ensuring that their data communications infrastructure and devices comply with CJIS and applicable State requirements. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 124 Attachment L-1 – CJIS Security Addendum FEDERAL BUREAU OF INVESTIGATION CRIMINAL JUSTICE INFORMATION SERVICES SECURITY ADDENDUM The goal of this document is to augment the CJIS Security Policy to ensure adequate security is provided for criminal justice systems while (1) under the control or management of a private entity or (2) connectivity to FBI CJIS Systems has been provided to a private entity (contractor). Adequate security is defined in Office of Management and Budget Circular A-130 as “security commensurate with the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information.” The intent of this Security Addendum is to require that the Contractor maintain a security program consistent with federal and state laws, regulations, and standards (including the CJIS Security Policy in effect when the contract is executed), as well as with policies and standards established by the Criminal Justice Information Services (CJIS) Advisory Policy Board (APB). This Security Addendum identifies the duties and responsibilities with respect to the installation and maintenance of adequate internal controls within the contractual relationship so that the security and integrity of the FBI's information resources are not compromised. The security program shall include consideration of personnel security, site security, system security, and data security, and technical security. The provisions of this Security Addendum apply to all personnel, systems, networks and support facilities supporting and/or acting on behalf of the government agency. 1.00 Definitions 1.01 Contracting Government Agency (CGA) - the government agency, whether a Criminal Justice Agency or a Noncriminal Justice Agency, which enters into an agreement with a private contractor subject to this Security Addendum. 1.02 Contractor - a private business, organization or individual which has entered into an agreement for the administration of criminal justice with a Criminal Justice Agency or a Noncriminal Justice Agency. 2.00 Responsibilities of the Contracting Government Agency. 2.01 The CGA will ensure that each Contractor employee receives a copy of the Security Addendum and the CJIS Security Policy and executes an acknowledgment of such receipt and the contents of the Security Addendum. The signed acknowledgments shall remain in the possession of the CGA and available for audit purposes. The acknowledgement may be signed by hand or via digital signature (see glossary for definition of digital signature). 3.00 Responsibilities of the Contractor. 3.01 The Contractor will maintain a security program consistent with federal and state laws, regulations, and standards (including the CJIS Security Policy in effect when the contract is executed and all Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 125 subsequent versions), as well as with policies and standards established by the Criminal Justice Information Services (CJIS) Advisory Policy Board (APB). 4.00 Security Violations. 4.01 The CGA must report security violations to the CJIS Systems Officer (CSO) and the Director, FBI, along with indications of actions taken by the CGA and Contractor. 4.02 Security violations can justify termination of the appended agreement. 4.03 Upon notification, the FBI reserves the right to: a. Investigate or decline to investigate any report of unauthorized use; b. Suspend or terminate access and services, including telecommunications links. The FBI will provide the CSO with timely written notice of the suspension. Access and services will be reinstated only after satisfactory assurances have been provided to the FBI by the CGA and Contractor. Upon termination, the Contractor's records containing CHRI must be deleted or returned to the CGA. 5.00 Audit 5.01 The FBI is authorized to perform a final audit of the Contractor's systems after termination of the Security Addendum. 6.00 Scope and Authority 6.01 This Security Addendum does not confer, grant, or authorize any rights, privileges, or obligations on any persons other than the Contractor, CGA, CJA (where applicable), CSA, and FBI. 6.02 The following documents are incorporated by reference and made part of this agreement: (1) the Security Addendum; (2) the NCIC 2000 Operating Manual; (3) the CJIS Security Policy; and (4) Title 28, Code of Federal Regulations, Part 20. The parties are also subject to applicable federal and state laws and regulations. 6.03 The terms set forth in this document do not constitute the sole understanding by and between the parties hereto; rather they augment the provisions of the CJIS Security Policy to provide a minimum basis for the security of the system and contained information and it is understood that there may be terms and conditions of the appended Agreement which impose more stringent requirements upon the Contractor. 6.04 This Security Addendum may only be modified by the FBI, and may not be modified by the parties to the appended Agreement without the consent of the FBI. 6.05 All notices and correspondence shall be forwarded by First Class mail to: Information Security Officer Criminal Justice Information Services Division, FBI 1000 Custer Hollow Road Clarksburg, West Virginia 26306 Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 126 Attachment M – Special Terms and Conditions 1. Payment Terms Agreement Amount. The maximum amount payable under this Agreement is Two Million Seven Hundred Twenty-Nine Thousand Three Hundred Ninety-Nine dollars and Thirty-Four Cents ($2,729,399.34) will be due pursuant to the payment schedule in the Orange County Statement of Work during the implementation phase of the new CAD system. This amount includes maintenance for the first year of operation of the new system, beginning upon Subsystem Cutover and continuing for one year. This amount shall not be exceeded without duly executed written amendment to this Agreement. 2. Insurance. 2.1 Policies and Coverage Amounts. Hexagon agrees to procure and maintain in force during the term of the Master Agreement, at its own cost, the following policies and amounts of coverage: 2.1.1 Workers' Compensation Insurance as required state statute or regulation. 2.1.2 Commercial General Liability Insurance with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) each occurrence and ONE MILLION DOLLARS ($1,000,000) general aggregate. The policy shall be applicable to all premises and operations. The policy shall include coverage for bodily injury, broad form property damage, and personal injury. 2.1.3 Automobile Liability Insurance with minimum combined single limits for bodily injury and property damage of not less than ONE MILLION DOLLARS ($1,000,000) for any one occurrence, with respect to each of Hexagon's owned, hired or non-owned vehicles assigned to or used in performance of the services or work under the Master Agreement. 2.1.4 Umbrella/Excess Coverage with minimum combined single limits of ONE MILLION DOLLARS ($1,000,000) per occurrence. 2.1.5 Errors and Omissions (with Cyber Liability coverage within the policy) with a minimum of ONE MILLION DOLLARS ($1,000,000) per occurrence. 2.2 Certificate of Insurance. If required or requested: a Certificate of Insurance shall be completed by Hexagon’s insurance agent(s) as evidence that policies providing the required coverage amounts, conditions, and minimum limits are in full force; and, the completed Certificate of Insurance shall be sent to the contact person identified in the Primary Contracting Document. 2.3 Insurance Deductible. Hexagon shall be solely responsible for any deductible losses under the policies required above. 3 Indemnification Provisions. 3.1 Hexagon will defend, at its expense, a third party action, suit, or proceeding against Customer ("Claim"), and indemnify Customer from any judgments, settlements, and reasonable attorney's fees resulting therefrom, to the extent such Claim is (i) attributable to bodily injury, death, or physical damage to tangible property caused by Hexagon's negligent acts or omissions arising under the Master Agreement; or (ii) based upon an allegation that a Software Product, Customized Software, Cloud Application, or Services Deliverable as of its delivery date under the this SOW, infringes a valid United States: patent, copyright, or trademark, or misappropriates a third party's trade secret ("Infringement Claim"). 3.2 Hexagon's defense and indemnification obligations are conditioned upon: 3.2.1 Customer providing prompt written notice to Hexagon of any Claim; Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 127 3.2.2 Hexagon having primary control of the defense of any actions and negotiations related to the defense or settlement of any Claim, understanding Hexagon may not settle a claim without Customer’s consent if such settlement assigns fault or culpability to Customer; and 3.2.3 Customer cooperating fully in the defense or settlement of any Claim. 3.3 Hexagon will have no obligation to defend Customer or to pay any resulting costs, damages, or attorneys' fees for any Infringement Claims alleging direct or contributory infringement of the Software Product, Cloud Program, or Service Deliverable (i) by the combination of or integration with a product, process, or system not supplied by Hexagon; (ii) by material alteration by anyone other than Hexagon or its subcontractors; (iii) by use after Customer has been notified of possible infringement; (iv) by use after modifications are provided to Customer; (v) by use after a return for refund as described below is ordered by Hexagon; (vi) if the creation of which was pursuant to specifications provided by Customer; or (vii) by use other than as specified in the Documentation associated with the Software Product. 3.4 In connection with any Infringement Claims, Hexagon, at its own expense and option, may either (i) obtain rights for Customer to continue using the allegedly infringing Hexagon supplied item; (ii) replace the item with a non-infringing alternative, or modify the allegedly infringing elements of the item, while maintaining substantially similar software functionality or data/informational content; or (iii) refund to Customer a prorated portion of the license fees paid by Customer for the infringing item(s); provided that proration for perpetually licensed software shall be based on a five (5)-year, straight-line depreciation basis beginning from the initial date of delivery. In the event of a prorated return, Customer will uninstall, cease all use of and return to Hexagon the infringing item(s). 3.5 In no event will the indemnification for Infringement Claims apply to any Beta Software, or sample, hot fix, royalty free, or evaluation software delivered pursuant to the SOW. 3.6 The terms of this agreement and the GSA contract are subject to North Carolina public records law, as set out in Chapter 132 of the North Carolina General Statutes. Should Hexagon fail to consent to disclosure pursuant to a legitimate records request under these laws, Hexagon agrees to indemnify and hold harmless Orange County and its officers, employees, and agents from all costs, damages and expenses incurred in connection with refusing to disclose the records. 4. Dispute Resolution: Neither party may initiate binding arbitration. Any disputes shall be resolved by nonbinding mediation in Hillsborough, North Carolina or within twenty-five (25) miles thereof. If such mediation fails either party may initiate litigation to resolve the dispute. Regardless of the outcome of said litigation each party is responsible for its own costs and fees, including attorneys’ fees. 5. Waiver of Jurisdiction Hexagon waives any claim or right to assert that venue of litigation shall lie in Alabama. 6. Non Appropriation. Hexagon acknowledges that Orange County is a governmental entity, and the validity of this agreement is based upon the availability of public funding under the authority of its statutory mandate. In the event that public funds are unavailable and not appropriated for the performance of Orange County’s obligations under this Agreement, then this Agreement shall automatically expire without penalty to Orange County immediately upon written notice to the Provider of the unavailability and non- appropriation of public funds. Notwithstanding the above, Orange County will pay Hexagon for all conforming services rendered, and equipment or parts provided, up to the date of termination. 7. North Carolina Provisions. Provider shall at all times remain in compliance with all applicable local, state, and federal laws, rules, and regulations including but not limited to all state and federal anti- discrimination laws, policies, rules, and regulations and the Orange County Non-Discrimination Policy and Orange County Living Wage Policy (each Orange County policy is incorporated herein by reference and may be viewed at http://www.orangecountync.gov/departments/purchasing_division/contracts.php.) that are not otherwise inconsistent with the GSA Agreement. Any violation of this requirement is a breach of Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Orange County, NC On-Premise OnCall Dispatch Implementation Statement of Work 128 the Order and County may immediately terminate the Order without further obligation on the part of the County. This paragraph is not intended to limit and does not limit the definition of breach to discrimination. By executing the Order Provider certifies that Provider has not been identified, and has not utilized the services of any agent or subcontractor identified, on the list created by the State Treasurer pursuant to G.S. 147-86.58. By executing the Agreement Provider certifies that Provider has not been identified, and has not utilized the services of any agent or subcontractor identified, on the list created by the State Treasurer pursuant to G.S. 147-86.81. By executing the Agreement Provider affirms Provider is and shall remain in compliance with Article 2 of Chapter 64 of the North Carolina General Statutes. In addition to this Addendum, should any documents, exhibits, or other addenda be attached to the Agreement, the terms of this Addendum shall have priority in any conflict with or among the terms of the Agreement and such referenced documents, exhibits, or other addenda. 7.1 Signatures: This Agreement together with any amendments or modifications may be executed electronically. All electronic signatures affixed hereto evidence the intent of the Parties to comply with Article 11A and Article 40 of the North Carolina General Statutes Chapter 66. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Holder Identifier : 7777777707070700077763616065553330763735764015474607762215770634132071660557146323320752405777247455007744415716234754077260711364101320774225115623657407724275512274570077727252025773110777777707000707007 6666666606060600062606466204446200620020426224022006222004060040202062202260422620020622222424204222006222006240260200062020042620600000622222424020262006222064000460060066646062240664440666666606000606006Certificate No : 570107706043 CERTIFICATE OF LIABILITY INSURANCE DATE(MM/DD/YYYY) 08/15/2024 IMPORTANT: If the certificate holder is an ADDITIONAL INSURED, the policy(ies) must have ADDITIONAL INSURED provisions or be endorsed. If SUBROGATION IS WAIVED, subject to the terms and conditions of the policy, certain policies may require an endorsement. A statement on this certificate does not confer rights to the certificate holder in lieu of such endorsement(s). THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CERTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURER(S), AUTHORIZED REPRESENTATIVE OR PRODUCER, AND THE CERTIFICATE HOLDER. PRODUCER Aon Risk Services Northeast, Inc. Providence RI Office 100 Westminster Street, 10th Floor Providence RI 02903-2393 USA PHONE(A/C. No. Ext): E-MAILADDRESS: INSURER(S) AFFORDING COVERAGE NAIC # (866) 283-7122 INSURED 35300Allianz Global Risks US Insurance Co.INSURER A: 22322Greenwich Insurance CompanyINSURER B: 25682The Travelers Indemnity Co of CTINSURER C: 41483Farmington Casualty CompanyINSURER D: 25674Travelers Property Cas Co of AmericaINSURER E: INSURER F: FAX(A/C. No.):(800) 363-0105 CONTACTNAME: Intergraph Corporation 305 Intergraph Way Madison AL 35758 USA COVERAGES CERTIFICATE NUMBER:570107706043 REVISION NUMBER: THIS IS TO CERTIFY THAT THE POLICIES OF INSURANCE LISTED BELOW HAVE BEEN ISSUED TO THE INSURED NAMED ABOVE FOR THE POLICY PERIOD INDICATED. NOTWITHSTANDING ANY REQUIREMENT, TERM OR CONDITION OF ANY CONTRACT OR OTHER DOCUMENT WITH RESPECT TO WHICH THIS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLICIES DESCRIBED HEREIN IS SUBJECT TO ALL THE TERMS, Limits shown are as requested POLICY EXP (MM/DD/YYYY)POLICY EFF (MM/DD/YYYY)SUBRWVDINSR LTR ADDL INSD POLICY NUMBER TYPE OF INSURANCE LIMITS COMMERCIAL GENERAL LIABILITY CLAIMS-MADE OCCUR POLICY LOC EACH OCCURRENCE DAMAGE TO RENTED PREMISES (Ea occurrence) MED EXP (Any one person) PERSONAL & ADV INJURY GENERAL AGGREGATE PRODUCTS - COMP/OP AGG X X X GEN'L AGGREGATE LIMIT APPLIES PER: $1,000,000 $100,000 $10,000 $1,000,000 $1,000,000 $2,000,000 A 06/01/2024 06/01/2025USL02303224 PRO- JECT OTHER: AUTOMOBILE LIABILITY ANY AUTO OWNED AUTOS ONLY SCHEDULED AUTOS HIRED AUTOS ONLY NON-OWNED AUTOS ONLY BODILY INJURY ( Per person) PROPERTY DAMAGE (Per accident) X BODILY INJURY (Per accident) $1,000,000C06/01/2024 06/01/2025 COMBINED SINGLE LIMIT (Ea accident)HECAP-162D6025-TCT-24 EXCESS LIAB X OCCUR CLAIMS-MADE AGGREGATE EACH OCCURRENCE DED $4,000,000 $4,000,000 $4,000,000$25,000 06/01/2024UMBRELLA LIABA 06/01/2025USL02303324 RETENTIONX X PRODUCTS - COMP/OP AGG E.L. DISEASE-EA EMPLOYEE E.L. DISEASE-POLICY LIMIT E.L. EACH ACCIDENT $1,000,000 X OTH-ERPER STATUTED06/01/2024 06/01/2025 AOS UB3N06483824I3RE 06/01/2024 06/01/2025 $1,000,000 Y / N (Mandatory in NH) ANY PROPRIETOR / PARTNER / EXECUTIVE OFFICER/MEMBER N / AN AR, AZ, FL, GA, MA,MN, NE WORKERS COMPENSATION AND EMPLOYERS' LIABILITY If yes, describe under DESCRIPTION OF OPERATIONS below $1,000,000 UB0N26927324I3K AggregateUS00110058EO24A06/01/2024 06/01/2025 E&O/Cyber $683,911Deductible Cyber LiabilityB $5,000,000 DESCRIPTION OF OPERATIONS / LOCATIONS / VEHICLES (ACORD 101, Additional Remarks Schedule, may be attached if more space is required) The Customer, its officials, officers, employees, and agents are included as Additional Insured in accordance with the policy provisions of the General Liability and Automobile Liability policies when required by written contract. CANCELLATIONCERTIFICATE HOLDER AUTHORIZED REPRESENTATIVEOrange County PO Box 8181 Hillsborough NC 27278 USA ACORD 25 (2016/03) ©1988-2015 ACORD CORPORATION. All rights reserved The ACORD name and logo are registered marks of ACO SHOULD ANY OF THE ABOVE DESCRIBED POLICIES BE CANCELLED BEFORE THE EXPIRATION DATE THEREOF, NOTICE WILL BE DELIVERED IN ACCORDANCE WITH THE POLICY PROVISIONS. Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E Revised 01/24 1 ORANGE COUNTY—INTERNAL USE ONLY ______________________________________________________________________________ Finance Information Vendor Name: Hexagon Safety, Infrastructure, & Geospatial Vendor Contact Person: Michael Dunkwu Phone: 571-368-8328 Address: 305 Intergraph Way City Madison State: AL Zip: 35758 Department: Emergency Services Amount: $2,729,399.34 Purpose: CAD Replacement Budget Code(s): 6175003580000017004, 357551308000000 Vendor # 68660 Vendor Status with NCSOS: ACTIVE Vendor is a BOCC consultant: Yes No Contract Details Contract Type: New Amendment (Original Contract: ) (Most Recent Amendment ) Effective Date Upon Execution End Date 1 year from cutover to production use Notice Date (Notice Purpose ) Award Approved by Board (Agenda Date: 09/05/2024); Made or Administered by Signature Authority - BOCC Express Delegation (Agenda Date: ) - Policy 9.4: Under $5,000; Service Under $90,000; Construction Under $250,000 - Budget Policy Section XV (Capital Improvement Proj ect: Public Safety Software Enhancements) Bidding Informal Bidding ($30k-$90k); Formal RFP ($90k+); Other (<$30k); Exception(#GSA/Sole Source) Department Affirmation This agreement is approved as to technical form and content and I as Department Director affirmatively state work on this project has not been initiated prior to execution of the agreement. This agreement is approved as to technical form and content. Services related to this agreement have alread y begun or been completed. Description of the nature of the emergency condition that was addressed: Department Director’s Signature ________________________________________ Date: ________ Information Technologies This agreement has been reviewed and is approved as to information technology content and specifications: Office of the Chief Information Officer___________________________________ Date: ________ Inapplicable because no hardware/software purchases or related services Risk Management This agreement is approved for sufficiency of insurance standards, specifications, and requirements: Office of the Risk Management Officer___________________________________ Date: _________ Financial Services This instrument has been pre-audited in the manner required by the Local Government Budget and Fiscal Control Act: Office of the Chief Financial Officer ____________________________________ Date: _________ Legal Services This agreement is approved as to legal form and sufficiency: Office of the County Attorney __________________________________________Date: ________ Clerk to the Board All Docusign contracts must be copied to the Clerk upon completion: occlerkdocs@orangecountync.gov The following signature block is for hard copies only and is not required for Docusign contracts: Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E 9/13/2024 9/19/2024 9/23/2024 9/25/2024 9/26/2024 Revised 01/24 2 Received for record retention: Office of the Clerk to the Board __________________________________________Date:_________ Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E