Sunnyvale City Council
July 23, 2024

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 72
Training Phase

31. Hexagon-Led Training
Task Description
During the Training phase, Hexagon resources will conduct Administrative and Train-the-Trainer sessions for City of Sunnyvale -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
 HxGN OnCall Dispatch | Mobile Unit Train-the-Trainer – Qty: 1  HxGN OnCall Dispatch | Mobile Responder Train-the-Trainer – Qty: 1  HxGN OnCall Analytics | Dispatch User Training – Qty: 1  HxGN OnCall Analytics | Dispatch System Administrator Training – Qty: 1 It is recommended that City of Sunnyvale 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 and OnCall Records upon Cutover.

The City of Sunnyvale is solely responsible for training its Users. The City of Sunnyvale shall complete its User Training no later than forty-five (45) 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
 City of Sunnyvale 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 City of Sunnyvale has installed and configured at least one (1) workstation per student attending the session.
 City of Sunnyvale Functional Testing Tasks for each Subsystem are complete.

Task Assumptions
 The City of Sunnyvale 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.
 Training documentation provided by Hexagon with this SOW will be standard COTS Documentation and help files and will not be customized to the City of Sunnyvale’s site-specific Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 73
configuration. All Documentation will be provided in electronic format. Should printed copies be required, the City of Sunnyvale is responsible for providing them.

Hexagon Team Participation and Responsibilities
Hexagon shall:
 Conduct Hexagon Training Classes.

City of Sunnyvale Team Participation and Responsibilities City of Sunnyvale 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 City of Sunnyvale.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 74

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 City of Sunnyvale 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.

City of Sunnyvale Team Participation and Responsibilities City of Sunnyvale 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.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 75
Cutover Phase

33. Cutover Plan
Task Description
Hexagon and the City of Sunnyvale 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 City of Sunnyvale personnel in the month prior to Cutover. The Cutover Plan covers topics including City of Sunnyvale 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 City of Sunnyvale for review. The City of Sunnyvale 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 City of Sunnyvale personnel to refine the Cutover Plan; and  Review and approve the final Cutover Plan.

City of Sunnyvale Team Participation and Responsibilities City of Sunnyvale 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 City of Sunnyvale has reviewed and approved the final Cutover Plan.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 76

34. System Readiness Review
Task Description
During this Task Hexagon technical resources, the Hexagon Project Manager, and the City of Sunnyvale Project 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 City of Sunnyvale.
 Establishment and approval of a schedule for Cutover Activities; and  Identification and scheduling of Hexagon and City of Sunnyvale 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 City of Sunnyvale 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 City of Sunnyvale to determine suitable Cutover schedule.

City of Sunnyvale Team Participation and Responsibilities City of Sunnyvale 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.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 77

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 City of Sunnyvale 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 City of Sunnyvale’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 resource are on site Monday to Friday of the week of Cutover. Upon Cutover, the City of Sunnyvale’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 City of Sunnyvale System Administrator. At times where the Hexagon resources are not otherwise available after the Project is complete, the City of Sunnyvale shall contact Hexagon’s HelpDesk in accordance with the Maintenance Terms within the Agreement.

Cutover also marks the commencement of the Warranty Period for the Project Software as described in Attachment K.

Task Deliverables

 Cutover of OnCall Dispatch Subsystem

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 will provide resources on site.

Hexagon Team Participation and Responsibilities
Hexagon shall:
 Hexagon shall provide technical resource(s) on site to support Cutover during the week of Cutover.

City of Sunnyvale Team Participation and Responsibilities City of Sunnyvale shall:
 Ensure availability of trained Users;
 Ensure availability of Core Team during Cutover Activities;  Assume System Administration and management for the System upon Cutover;  Ensure availability of all third-party vendors impacted by the Cutover; Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 78
 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 Subsystem.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 79

36. Post-Cutover Support
Task Description
During this Task, Hexagon resources will provide Post-Cutover support to City of Sunnyvale. The “Post- Cutover Support Period” is the twenty (20) Business Days beginning the Monday following Cutover. It is designed to provide the City of Sunnyvale with dedicated, quickly accessible support for questions and Defects encountered in the twenty (20) 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 City of Sunnyvale 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 that are not level 1, 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.
 All Level 1 Defects have been resolved
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.
 The first and third weeks of Post-Cutover Support will have a Hexagon resource on site. The second and fourth weeks of Post-Cutover Support will be performed remotely.  Defects will be reported via Hexagon’s designated CRM tool.  The City of Sunnyvale System Administrator remains the primary point of contact and initial troubleshooting point of contact for all issues during this Task.  The City of Sunnyvale System Administrator maintains responsibility for core system administration tasks.

Hexagon Team Participation and Responsibilities
Hexagon shall:
 Provide twenty (20) Business Days of Post-Cutover support in accordance with this SOW; and  Address Defects within the Post Cutover Support Period.  Resolve all Level 1 Defects
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 80
City of Sunnyvale Team Participation and Responsibilities City of Sunnyvale shall:
 Ensure Defects are recorded in Hexagon’s CRM tool in a timely manner and in accordance to the mutually agreed upon Project Schedule.

Task Acceptance Criteria
This Task is complete when the Post-Cutover Support Period has expired and all Level 1 Defects have been resolved.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 81
Terms and Conditions
The terms and conditions governing this SOW are set forth in the executed Master Agreement, whereby the SOW is an Exhibit to the Master Agreement.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 82
Attachment A – Pricing Summary

ONCALL DISPATCH (ON-PREMISE) TOTAL
OnCall Dispatch Project Costs:

HxGN OnCall Dispatch Software $810,007
HxGN OnCall Dispatch Services $ 1,575,984
Custom Interfaces:

CAD Interface to CryWolf (Bi-Directional) $34,392
CAD Informer Query to CJIC $23,110
CAD Informer Query to Alameda Warrant System (AWS) $14,609 CAD Informer Query to Tiburon RMS $29,218
Create Custom Field for Tow $5,724
Create Custom Field for Supervised Release (SRF) $5,724 Create Custom Field for Rap Sheet Query $18,507
OnCall Analytics Custom Reports Creation $88,131
Create Custom Field for SVS $7,932
Third Party:

CommSys ConnectCIC $ 32,313
Kemp Load Balancer $32,090

One-Time Software and Services $2,677,741
Perpetual Software Extended Warranty/Maintenance - Year 1 $216,862 Total One-Time Software and Services (including Extended Warranty): $2,894,603

Annual Recurring Maintenance:

Year 2 Maintenance $227,705
Year 3 Maintenance $239,091
Year 4 Maintenance $251,045
Year 5 Maintenance $263,597
Year 6 Maintenance $276,777
Year 7 Maintenance $290,616
Year 8 Maintenance $305,147
Year 9 Maintenance $320,404
Year 10 Maintenance $336,424
Project Options:

HxGN OnCall Dispatch - Smart Advisor & Services $49,778 Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 83
Pricing Assumptions:
 This offer is valid until July 31, 2024.
 Based on the request for 10 years of maintenance, Hexagon pricing assumes the first year to be the Extended Warranty (1st year maintenance) period, and Years 2-10 as the following 9 years of recurring maintenance.
 Total One-Time Software and Services includes a 12-month Extended Warranty Period (first year maintenance) which begins at sub-system cutover to live operations.  Any commercial-off-the-shelf (COTS) product information provided by Hexagon in this document is intended 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. Except as set forth in a resulting contract, Hexagon does not commit to develop the future features, functions, and products discussed in this material. Sunnyvale should not factor any future features, functions, or products into its current buying decision since there is no assurance that such future features, functions, or products will be developed unless specified in the resulting contract.  Project services costs include project management, implementation, configuration, integration, travel, and training courses.
 The optional pricing for HxGN OnCall Dispatch Smart Advisor includes one-time services, software licenses, and 1st year maintenance/extended warranty. Optional pricing expires 30 days following contract signing. The third party CommSys software pricing provided could potentially change based on the final number of agencies and sworn officers in the resulting contract.  Third parties and interfaces included in the one-time project fee include support/maintenance; some start at cutover and others upon shipment. All have been included in the pricing appropriately.
 The third-party Kemp Load Balancer products procured by Hexagon is provided with a pre-paid 5- year pass-through 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 three (3) attendees for 2025 and 2027. HxGN Live attendance fees do not include travel and lodging costs.  The pricing in the above tables is exclusive of any applicable sales/use tax. Any applicable tax will be added to the pricing above at time of invoicing.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 84
Bill of Materials Descriptions
Below is a copy of the Bill of Materials from Hexagon’s Phase 2 on-premise proposal document. A column has been added to provide a description of each line item.

PRODUCT QTY DESCRIPTION
OnCall Software

HxGN OnCall Dispatch - Advantage CC 7 Concurrent user licenses for OnCall Dispatch software; refer to Section 2 in
Hexagon’s on-premise proposal
document for the full description
HxGN OnCall Dispatch - Advantage CC -
Test License
7 Concurrent user test licenses for OnCall
Dispatch software
HxGN OnCall Dispatch - Advantage CC -
Training License
2 Concurrent user training licenses for
OnCall Dispatch software
HxGN OnCall Dispatch - Essentials CC
for Animal Control
1 Concurrent user licenses for OnCall
Dispatch software; refer to Section 2 in
Hexagon’s on-premise proposal
document for the full description
HxGN OnCall Dispatch -Essentials CC -
Test License for Animal Control
1 Concurrent user test licenses for OnCall
Dispatch software
HxGN OnCall Dispatch -Essentials CC –
License for Animal Control- BCK
1 Concurrent user backup licenses for
OnCall Dispatch software
HxGN OnCall Dispatch - Viewer CC 4 Concurrent user licenses for the Viewer software; provides access to live dispatch
information and basic capabilities to users
outside the control room. Refer to Section
2 in Hexagon’s on-premise proposal
document for the full description.

HxGN OnCall Dispatch - Viewer CC - Test
License
4 Concurrent user test licenses for OnCall
Dispatch | Viewer software
HxGN OnCall Dispatch - Advanced
Mapping
7 Concurrent 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 - Advanced
Mapping - Test License
7 Concurrent user test licenses for the
Advanced Mapping add-on pack
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 85

PRODUCT QTY DESCRIPTION
HxGN OnCall Dispatch - ESRI Map
Control
7 Concurrent user licenses for ESRI Map
Control add-on pack; enables customers
to perform road closures from within
OnCall Dispatch Advantage
HxGN OnCall Dispatch - ESRI Map
Control - TST
7 Concurrent user test licenses for ESRI
Map Control add-on pack
HxGN OnCall Dispatch - Resource
Management
7 Concurrent 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 - Test License
7 Concurrent user test licenses for the
Resource Management add-on pack
HxGN OnCall Dispatch - Resource
Management - TRN License
2 Concurrent user training licenses for the
Resource Management add-on pack
HxGN OnCall Dispatch - ProQA Interface 7 Concurrent user licenses for the ProQA Interface add-on; refer to Section 2,
Interface Descriptions in Hexagon’s on-
premise proposal document for the full
description
HxGN OnCall Dispatch - ProQA Interface
- Test
7 Concurrent user test licenses for the
ProQA Interface add-on
HxGN OnCall Dispatch - ProQA Interface
- Training
2 Concurrent user training licenses for the
ProQA Interface add-on
HxGN OnCall Dispatch - Dashboard CC 3 Concurrent user production licenses for HxGN OnCall Dispatch | Dashboard, a
configurable browser-based dashboard
solution that delivers concise, dynamic
summaries of PSAP operations
HxGN OnCall Dispatch - Dashboard CC -
Test License
3 Concurrent user test licenses for HxGN
OnCall Dispatch | Dashboard, a
configurable browser-based dashboard
solution that delivers concise, dynamic
summaries of PSAP operations
HxGN OnCall Dispatch - Customer Rules
Engine - Advantage
7 Concurrent user licenses for the
Customer Rules Engine product which will
allow OnCall Dispatch users to take
advantage of custom business rules
Hexagon creates for the City using a
simple drag-and-drop editor. Refer to
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 86

PRODUCT QTY DESCRIPTION
Section 2 in Hexagon’s on-premise
proposal document for the full description
HxGN OnCall Dispatch - Customer Rules
Engine - Adv - TST
7 Concurrent user training licenses for the
Customer Rules Engine add-on
HxGN OnCall Dispatch - Customer Rules
Engine - Adv - TRN
2 Concurrent user training licenses for the
Customer Rules Engine add-on
HxGN OnCall Dispatch - Customer Rules
Engine - Editor
1 Concurrent user license for the Customer
Rules Engine Editor product which
Hexagon will use to create custom rules
for the City
HxGN OnCall Dispatch - Customer Rules
Engine - Editor - TST
1 Concurrent user test licenses for the
Customer Rules Engine Editor
HxGN OnCall Dispatch - Customer Rules
Engine - Server
2 Server component required for the
Customer Rules Engine product in the
production environment
HxGN OnCall Dispatch - Customer Rules
Engine - Server - TST
2 Server component required for the
Customer Rules Engine product in the
test environment
HxGN OnCall Dispatch - Customer Rules
Engine - Server - TRN
1 Server component required for the
Customer Rules Engine product in the
training environment
HxGN OnCall Dispatch - Mobile Unit 65 Concurrent user licenses for Mobile Unit software; MDT dispatch software for field
users (police officer, firefighter, etc.)
HxGN OnCall Dispatch - Mobile Unit -
Test
65 Concurrent user test licenses for Mobile
Unit software
HxGN OnCall Dispatch - Mobile Unit -
Training
5 Concurrent user training licenses for
Mobile Unit software
HxGN OnCall Mobile Server 2 Server component required for Mobile Responder software
HxGN OnCall Mobile Server - Test 2 Test server component required for Mobile Responder software
HxGN OnCall Dispatch - Mobile
Responder Client CC
20 Concurrent user licenses for Mobile
Responder software; smartphone/tablet
app that provides field personnel access
to streamlined response and law
enforcement workflows
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 87

PRODUCT QTY DESCRIPTION
HxGN OnCall Dispatch - Mobile
Responder Client CC - Test
20 Concurrent user test licenses for Mobile
Responder software
HxGN OnCall Dispatch - Backup NL 1 Server product that provides support for maintaining one or more near real-time
backups of an OnCall database server
HxGN OnCall Dispatch - RestAPI NL 2 Provides third parties direct interaction with OnCall via an industry standard
RestAPI
HxGN OnCall Dispatch - RestAPI NL -
Test
2 Test license for RestAPI
HxGN OnCall Dispatch - RestAPI NL -
Training
1 Training license for RestAPI
HxGN OnCall Dispatch - Advantage CC -
Backup License
7 Concurrent user backup licenses for
OnCall Dispatch | Advantage software
HxGN OnCall Dispatch - Resource
Management - Backup License
7 Concurrent user backup licenses for
OnCall Dispatch | Resource Management
HxGN OnCall Dispatch - Advanced
Mapping - Backup License
7 Concurrent user backup licenses for
OnCall Dispatch | Advanced Mapping
HxGN OnCall Dispatch - Viewer CC -
Backup License
4 Concurrent user backup licenses for
OnCall Dispatch | Viewer
HxGN OnCall Dispatch - ESRI Map
Control - BCK
7 Concurrent user backup licenses for
OnCall Dispatch | Esri Map Control
HxGN OnCall Dispatch - ProQA Interface
- Backup
7 Concurrent user backup licenses for
OnCall Dispatch | ProQA
HxGN OnCall Dispatch - Customer Rules
Engine - Adv - BCK
7 Concurrent user backup licenses for
OnCall Dispatch | Customer Rules Engine
Advantage
HxGN OnCall Dispatch - Customer Rules
Engine - Editor - BCK
1 Concurrent user backup license for
OnCall Dispatch | Customer Rules Engine
Editor
HxGN OnCall Dispatch - Mobile Unit -
Backup
65 Concurrent user backup licenses for
OnCall Dispatch | Mobile Unit
HxGN OnCall Dispatch - Customer Rules
Engine - Server - BCK
2 Backup licenses for OnCall Dispatch |
Customer Rules Engine Server
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 88

PRODUCT QTY DESCRIPTION
component required for Customer Rules
Engine
HxGN OnCall Dispatch - Dashboard CC -
Backup License
3 Concurrent user backup licenses for
OnCall Dispatch | Dashboard
HxGN OnCall Dispatch - RestAPI NL -
Backup
2 Backup licenses for RestAPI
HxGN OnCall Dispatch - Informer -
Backup
1 Backup licenses for Informer interface
HxGN OnCall Dispatch - Notifications -
Backup
1 Backup license for Notifications interface
HxGN OnCall Dispatch - CAD Link
Interface - Backup
1 Backup license for CAD Link interface
HxGN OnCall Dispatch - Fire Link
Interface - Backup
1 Backup license for Fire Link interface
HxGN OnCall Dispatch - Call-Taker
Interface - BCK
1 Backup license for Call-Taker interface
HxGN OnCall Dispatch - PTT - Backup 1 Backup license for PTT interface HxGN OnCall Dispatch - Fire Station
Printing - Backup
1 Backup license for Fire Station Printing
interface
Body Worn Camera OnCall Interface -
BCK
1 Backup license for Body Worn Camera
interface
CAD to CAD OnCall Dispatch Interface -
BCK
1 Backup license for CAD to CAD interface
RapidSOS OnCall Call-Taker Interface -
BCK
1 Backup license for RapidSOS OnCall
Call-Taker interface
Fire Station Alerting OnCall Dispatch
Interface - BCK
1 Backup license for Fire Station Alerting
interface
Xalt - Integration Runtime Engine NL 1 Lightweight, general purpose integration platform to connect third party
applications, systems, and devices with
OnCall Dispatch enabling the exchange of
data
Xalt - Integration Runtime Engine NL -
Test License
1 Test license for Xalt
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 89

PRODUCT QTY DESCRIPTION
HxGN OnCall Analytics - Dispatch
Advantage NL 4 Core
1 License for OnCall Analytics – Dispatch
Advantage; provides complete reporting
and analysis capabilities for HxGN OnCall
Dispatch data
HxGN OnCall Dispatch - Informer 1 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
Section 2, Interface Descriptions in
Hexagon’s on-premise proposal
document for the full description.

HxGN OnCall Dispatch - Notifications 1 Interface license for Notifications; provides connectivity between the
dispatching environment and multiple
internal and external communication
endpoints. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

HxGN OnCall Dispatch - CAD Link
Interface
1 Interface license for CAD Link; facilitates
the automatic periodic transfer of event
and unit information from OnCall Dispatch
to external systems such as Tiburon
RMS. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

HxGN OnCall Dispatch - Fire Link
Interface
1 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) such as ImageTrend.

Refer to Section 2, Interface Descriptions
in Hexagon’s on-premise proposal
document for the full description.

HxGN OnCall Dispatch - Call-Taker
Interface
1 Interface license for Call-Taker Interface;
enables Call-Taker (included with OnCall
Dispatch | Advantage) to connect to
various external systems such as
RapidSOS
HxGN OnCall Dispatch - PTT 1 Interface license for PTT; interfaces to a radio system controller (such as Motorola
MCC7500) over a network connection
(TCP/IP) or a serial (RS-232) connection
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 90

PRODUCT QTY DESCRIPTION
to provide PTT information to a dispatcher
workstation. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

Fire Station Alerting OnCall Dispatch
Interface
1 Interface license for Fire Station Alerting;
interfaces between OnCall Dispatch and
fire station alerting vendors (such as
Zetron) to provide a method for OnCall
Dispatch to send audible alerts to fire
stations. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

HxGN OnCall Dispatch - Fire Station
Printing
1 Interface license for Fire Station Printing;
provides support for remote fire station
turnout by printing run cards when units
from a station are dispatched. Refer to
Section 2, Interface Descriptions in
Hexagon’s on-premise proposal
document for the full description.

Body Worn Camera OnCall Interface 1 Interface license for Body Worn Camera OnCall Interface; provides real-time unit
and event data transfer from OnCall
Dispatch to third-party body worn camera
providers such as Axon. Refer to Section
2, Interface Descriptions in Hexagon’s on-
premise proposal document for the full
description.

CAD to CAD OnCall Dispatch Interface 1 Interface license for CAD to CAD OnCall Dispatch Interface; provides real-time unit
and event data transfer to and from
OnCall Dispatch and third-party CAD
systems such as Santa Clara County’s
I/CAD 9.4. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

Anti-Bias Reporting 1 Interface license for California AB953 / RIPA. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

Custom Interfaces

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 91

PRODUCT QTY DESCRIPTION
RapidSOS OnCall Call-Taker Interface 1 Interface license for RapidSOS OnCall Call-Taker Interface; 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. Refer to Section 2, Interface
Descriptions in Hexagon’s on-premise
proposal document for the full
description.

CAD Interface to CryWolf (Bi-Directional) 1 Custom interface to CryWolf. Refer to Section 2, Interface Descriptions in
Hexagon’s on-premise proposal
document for the full description.

CAD Informer Query to CJIC 1 Custom interface to query CJIC. Refer to Section 2, Interface Descriptions in
Hexagon’s on-premise proposal
document for the full description.

CAD Informer Query to Alameda Warrant
System (AWS)
1 Custom interface to query AWS. Refer to
Section 2, Interface Descriptions in
Hexagon’s on-premise proposal
document for the full description.

CAD Informer Query to Tiburon RMS 1 Custom interface to query Tiburon RMS.

Refer to Section 2, Interface Descriptions
in Hexagon’s on-premise proposal
document for the full description.

Create Custom Field for Tow 1 Effort to create the custom field for Tow entry into CLETS. This is related to one of
the custom rules the City has requested
which are described in Section 2,
Customer Rules Engine of Hexagon’s on-
premise proposal document.

Create Custom Field for Supervised
Release File (SRF) 1
Effort to create the custom field for SRF
into CLETS. This is related to one of the
custom rules the City has requested
which are described in Section 2,
Customer Rules Engine of Hexagon’s on-
premise proposal document.

Create Custom Field for Rap Sheet Query 1
Effort to create custom field / form for the
ability to query Rap Sheet. Rap Sheet
query has also been added to the list of
CommSys transactions which are
included in the CommSys ConnectCIC
Installation Task.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 92

PRODUCT QTY DESCRIPTION
OnCall Analytics Custom Reports Creation 1
Effort to create the 18 custom reports as
described in OnCall Analytics Custom
Reports Creation Task. The example
reports provided by the City of Sunnyvale
are included as Attachment M.

Third Party

CommSys ConnectCIC 1 Middleware product for the interface to NCIC for state and local transactions
Kemp Load Balancer VLM-3000 (includes
5-year support) 3 Kemp load balancers required for OnCall web servers
Optional
HxGN OnCall Dispatch - Smart Advisor
12 Production license for HxGN OnCall
Dispatch | Smart Advisor, a system-wide
capability that leverages advanced
statistics, machine learning (ML), and
artificial intelligence (AI) to provide real-
time, proactive notifications to HxGN
OnCall Dispatch. This quantity represents
the total of OnCall Dispatch | Advantage,
OnCall Dispatch | Essentials, and OnCall
Dispatch | Viewer concurrent users.

HxGN OnCall Dispatch - Smart Advisor
Mobile
65 Production license for HxGN OnCall
Dispatch | Smart Advisor, a system-wide
capability that leverages advanced
statistics, machine learning (ML), and
artificial intelligence (AI) to provide real-
time, proactive notifications to HxGN
OnCall Dispatch. This quantity represents
the total of OnCall Dispatch | Mobile Unit
concurrent users.

Smart Advisor Unit Agents 1 Production license for OnCall Dispatch | Smart Advisor Unit Agents which would
allow Smart Advisor to monitor defined
areas for unit coverage and alert users
when an area has dropped below the
minimum coverage

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 93
Attachment B – Payment Schedule
The total fee for this Order and upon which the milestones are based is: $2,894,603

Milestone Payment Schedule
MS (#) Milestone Deliverable MS (%)
1 Upon Completion of Task 1: Project Kickoff Meeting 15.00% 2 Upon Completion of Task 9: Virtual Server and OnCall Installation 20.00% 3 Upon Completion of Task 11: OnCall Dispatch System Build 1 15.00% 4 Upon Completion of Task 17: OnCall Dispatch Configuration Consulting 1 15.00% 5 Upon Completion of Task 19: OnCall Dispatch Configuration Consulting 3 10.00% 6 Upon Completion of Task 21: OnCall Dispatch - Mobile Unit Configuration Consulting Session 10.00%
7 Upon Completion of Task 30: City of Sunnyvale Functional Testing 10.00% 8 Upon Completion of Task 36: Post-Cutover Support 5.00% Total 100.00%

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 94
Attachment C – Initial Project Schedule

TASK NAME DURATION BUSINESS DAYS

SINCE START
City of Sunnyvale, CA On-Premise OnCall Dispatch Project 536 days 0 days Planning Phase 157.75 days 0 days
Project Kickoff Meeting 7 days 20 days
COTS Interface Questionnaire Completion 10.5 days 30.75 days Customer completes COTS Interface Questionnaires 10 days 30.75 days OnCall Dispatch & Mobile Unit Launch 7 days 32 days
OnCall Dispatch GIS Requirements Review 1.13 days 32 days Custom Interface Requirements Gathering 37.88 days 27 days OnCall Dispatch Custom Interface Requirements
Gathering (ICDs) 37.88 days 27 days
CAD Informer Query to Tiburon RMS 17.13 days 27 days
Customer reviews ICD 10 days 28.63 days
Customer approves ICD 5 days 39.13 days
CAD Interface to CryWolf Bi-directional 17.13 days 28.63 days Customer reviews ICD 10 days 30.5 days
Customer approves ICD 5 days 40.75 days
CAD Informer Query to Alameda Warrant System (AWS) 16.13 days 30.5 days Customer reviews ICD 10 days 31.38 days
Customer approves ICD 5 days 41.63 days
Custom Web Application for AB953 Regulations 32.63 days 31.38 days Customer reviews ICD 10 days 47.75 days
Customer approves ICD 5 days 59 days
CAD Informer Query to CJIC 17.13 days 47.75 days
Customer reviews ICD 10 days 48.88 days
Customer approves ICD 5 days 59.88 days
Custom Interface Development 113.63 days 44.13 days
Load Balancer Equipment Ordering 0.25 days 27 days
Staging Phase 99.38 days 27.25 days
Physical Infrastructure Installation 1 day 35.25 days
Virtual Server and OnCall Software Staging 10.39 days 36.25 days OnCall Dispatch GIS Consulting 21.13 days 46.64 days
OnCall Dispatch System Build 1 15.23 days 67.77 days
OnCall Dispatch System Build 1 3 days 70 days
Customer Build Out of Remaining Data 10 days 73 days
OnCall Dispatch Deployment and Response Planning
Workshop 15 days 88 days
OnCall Dispatch Deployment and Response Planning
Workshop 3 days 90 days
Customer Build Out of Remaining Data 10 days 93 days
OnCall Dispatch System Build 2 18 days 108 days
OnCall Dispatch System Build 2 3 days 113 days
Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 95
Customer Build Out of Remaining Data 10 days 116 days
Configuration Phase 444.25 days 0 days
OnCall Dispatch Fundamentals for Core Team 10 days 131 days COTS Interface Product Installation and Configuration 131.63 days 0 days CommSys ConnectCIC Installation 5.25 days 131.63 days
OnCall Dispatch Configuration Consulting 1 18.25 days 146 days OnCall Dispatch Configuration Consulting 3 days 151.25 days Customer configures OnCall Dispatch 7 days 157.25 days
OnCall Dispatch Configuration Consulting 2 15.75 days 169.25 days OnCall Dispatch Configuration Consulting 3 days 172 days Customer configures OnCall Dispatch 7 days 178 days
OnCall Dispatch | Customer Rules Engine Configuration
Services 12 days 185 days
OnCall Dispatch Configuration Consulting 3 18 days 314 days OnCall Dispatch Configuration Consulting 3 days 319 days Customer configures OnCall Dispatch 7 days 325 days
OnCall Dispatch | Mobile Unit Configuration Consulting
Session - Law/Fire 15 days 337 days
OnCall Dispatch | Mobile Unit Law/Fire Configuration Session 3 days 339 days Customer configures OnCall Dispatch | Mobile Unit 10 days 342 days OnCall Dispatch | Mobile Responder Configuration - Law 2 days 342 days OnCall Dispatch | Mobile Responder Configuration - Fire 2 days 332 days OnCall Dispatch Archive Database Staging 0.25 days 419 days OnCall Analytics - Dispatch Configuration 7 days 419.25 days OnCall Analytics Custom Reports Creation 417.25 days 27 days Custom Interface Product Installation and Configuration 43 days 164.25 days Standard Interface Product Installation and Configuration 210.37 days 131.63 days Testing Phase 278 days 141 days
Test Plan and Test Cases Development - OnCall Dispatch 0 days 141 days Customer Functional Testing - OnCall Dispatch 45 days 373.75 days Customer Functional Testing 10 days 373.75 days
Customer Provides Blocker Error Report 5 days 383.75 days Customer Executes Test Plan Post Blocker Error Resolution 5 days 413.75 days Training Phase 489 days 0 days
Hexagon-Led Training 37 days 419 days
HxGN OnCall Dispatch System Administrator Training 9.5 days 419 days HxGN OnCall Dispatch Train-the-Trainer (TTT) 18.5 days 428.5 days OnCall Dispatch TTT #1 4 days 430 days
OnCall Dispatch TTT #2 4 days 440 days
OnCall Dispatch | Mobile Unit Train-the-Trainer 9 days 447 days OnCall Dispatch | Mobile Responder Train-the-Trainer 5 days 448 days OnCall Analytics - Admin and User Training 10.75 days 419.25 days Customer-Led End User Training (45 calendar days) 33 days 441.5 days Test and Training Environment Creation 7 days 0 days
Cutover Phase 46.13 days 489 days
Cutover Plan 11.63 days 489 days
Hexagon Delivers Draft Cutover Plan 0.13 days 490 days
Customer Reviews and Approves Cutover Plan 10 days 490.13 days Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 96
System Readiness Review 1 day 500.63 days
Cutover to Production Use 6 days 507 days
Post Cutover Support Week 1 5 days 513 days
Post Cutover Support Week 2 5 days 518 days
Post Cutover Support Week 3 5 days 523 days
Post Cutover Support Week 4 5 days 528 days

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 97
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
 City of Sunnyvale 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

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 98
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 City of Sunnyvale 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
 City of Sunnyvale 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

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 99
HxGN OnCall Dispatch | Mobile Unit Train-the-Trainer (Qty: 1)

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 City of Sunnyvale 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
 City of Sunnyvale 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  City of Sunnyvale 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

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 100
HxGN OnCall Dispatch | Mobile Responder Train-the-Trainer (Qty: 1) 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 City of Sunnyvale 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 City of Sunnyvale needs Student Capacity 12

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 101
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)

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 102
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)

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 103
Attachment E – OnCall Dispatch Specifications

[following this page]

Attachment 1

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

Attachment 1

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 Sub ject 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 th e 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 purposes.

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 registered 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 such changes.

Contact Us
Contact us https://hexagon.com/company/contact-us with any questions regarding these terms.

Attachment 1

HxGN OnCall® Dispatch Suite

3 Attachment 1

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

Attachment 1

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.

Attachment 1

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.

Attachment 1

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

Attachment 1

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.

Attachment 1

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.

Attachment 1

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.

Attachment 1

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.

Attachment 1

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 high 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.

Attachment 1

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.

Attachment 1

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.

Attachment 1

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.

Attachment 1

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.

Attachment 1

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)
Attachment 1

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 the 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
Attachment 1

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

Attachment 1

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.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 104
Attachment F – System Configuration Diagram

[following this page]

Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
1 System Overview

TABLE OF CONTENTS
System Overview Page 1 Hardware Specifications Page 2 Client Hardware Specifications Page 3 CAD Architecture Diagram Page 4
OnCall Mapping & Management Environments Page 5 OnCall Dispatch Production Environment Page 6
OnCall Dispatch Disaster Recovery Environment Page 7
OnCall Dispatch Test & Training Environments Page 8
Notes Page 9
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
System Management Server #1
vCenter Server #1
Kemp Load Balancing Appliance
MAPPING PRODUCTION ENVIRONMENT:

Mapping Server #1, 2, 3 (Production)
Mapping Staging Server
CAD PRODUCTION ENVIRONMENT:

Database Server #1,2 (CAD SQL AlwaysOn Cluster)
Reporting Database Server (Read Only DB Copy)
Archive Database Server #1a
OnCall Message Queue Server #1a, 2a, 3a
Web Server, #1, 2
Application Server #1a, 2a
Smart Advisor Web Application Server #1, 2, 3
Communications/Interface Server #1a
Communications/Interface Server #2a
OnCall Analytics Reporting Server (with Data Warehouse)

CAD TEST ENVIRONMENT:

Test Database Server #1, 2 (CAD SQL AlwaysOn Cluster)
Test OnCall Message Queue Server #1, 2, 3
Test Web Server #1, 2
Test Application Server #1, 2
Test Communications/Interface Server #1
Test Communications/Interface Server #2
CAD TRAINING ENVIRONMENT:

Training Database Server
Training OnCall Message Queue Server
Training Web Application Server

MANAGEMENT DR ENVIRONMENT:

Domain Controller/DNS Server #3
System Management Server #2
vCenter Server #2
Kemp Load Balancing Appliance
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
Application Server #1b, 2b
Communications/Interface Server #1c (Cold Backup)
Communications/Interface Server #2c

Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
2 Hardware Specifications
Hexagon recommends Data at Rest Encryption per CJIS Security Policy sect 5.10.1.2.2 Mobile device VPN bandwidth minimum of 215 Mbps is required *Kemp Load Balancers are required as part of the base solution; exceptions are not allowed.

Provisioned Required Provisioned Required Provisioned Required 196 78 912 1,094 14 20 38,560
Production
Memory
Site 1 Totals
vCPUs (3:1) Disk (TB) IOPS
Provisioned Required Provisioned Required Provisioned Required 96 38 442 530 3 5 8,600
IOPS
Disaster Recovery
Memory
Site 2 Totals
vCPUs (3:1) Disk (TB)
Quantity Make
3 * Kemp
2 HPE
2 Microsoft
2 Microsoft
2 Microsoft
4 Microsoft
2 Microsoft
2 VMware
Archive (No AAG) / Training Database
Test Database
SQL 2022 Standard Edition W/SA
SQL 2022 Developer Edition
SQL 2022 Enterprise Edition w/ SA
SQL 2022 Enterprise Edition w/ SA AAG Database
SQL 2022 Enterprise Edition w/ SA Operational Reports Optional Server vCenter | 6 CPU vSphere ESXi LicensevSphere Enterprise Plus Acceleration Kit On Call Analytics
Model
VLM-3000 (Enterprise Plus License)
DHCI Config 2
Description
Load Balancers
HPE DHCI 3 Hosts 768GB memory, 23TB (24TB Usable) with Windows Datacenter Bill of Material
Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
3 Client Hardware Specifications
OnCall Dispatch Advantage
Workstations - Windows
Recommended Specifications:

Windows 10/11 Professional
Modern Web Browser (Chrome, Firefox, Edge, etc.)
CPU:

Quad core (or more) Intel i5, i7 or i9 - 8th
Generation or later
Quad core (or more) AMD Ryzen 5, 7 or 9 - 2000
series or later
No ARM CPU architecture
Memory: 16GB min (32GB recommended)
Storage: 500GB (SSD recommended)
Display: Dual 21" 1920 x 1080 or larger
Graphics card: NVIDIA
Networking: 1GbE
OnCall Mobile Unit Mobile Data
Computers
Recommended Specifications:

Windows 10/11 Professional
Modern Web Browser (Chrome, Firefox, Edge, etc.)
CPU:

Quad core (or more) Intel i5, i7 or i9 - 8th
Generation or later
Quad core (or more) AMD Ryzen 5, 7 or 9 - 2000
series or later
No ARM CPU architecture
Memory: 16GB min (32GB recommended)
Storage: 500GB (SSD recommended)
Display: 1024 x 768 or higher, touchscreen
recommended
Wired networking: 1GbE
Wireless networking: WiFi, built in or USB 4G LTE
or 5G for cellular connectivity
Mobile Responder Smartphones/Tablets
Recommended Specifications:
iOS
or greater
Google® Inc. Android
devices with OS versions

9.0 or greater
OnCall Dispatch Advantage
Workstations - Apple
Recommended Specifications:

MacOS
Modern Web Browser (Chrome, Firefox, Edge, etc.)
CPU:

Quad core (or more) Intel i5, i7 or i9 or Apple Silicon M1, M2, M3
Memory: 16GB min (32GB recommended)
Storage: 500GB (SSD recommended)
Display: Dual 21" 1920 x 1080 or larger
Graphics card: AMD (if Intel architecture); N/A if
Apple Silicon
Networking: 1GbE
Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
4 Disaster Recovery ESX Cluster
Intranet
Internet
Production ESX Cluster (All VMs are running Windows Server) Rabbit MQ Cluster
X3 VMs
Interface Server
Rest API
load balancer)

DNS GSLB
Decision point
load balancer
HTTPS
Web Servers SQL Server
Primary
SQL Server
Backup
Synchronous
AlwaysOn
SQL Server
Data Warehouse
ETL
SQL Server
Archive
OnCall Backup
Always On Failover Group
HTTPS
Map Service
Web Server
HTTPS
Dispatch
Application Servers
Microsoft Active
Directory
Domain Controllers
Power BI
Server
CallTaker
Dispatcher
Viewer
Federated Rabbit MQRabbit MQ Cluster
X3 VMs
Dispatch
Application Servers
Microsoft Active
Directory
Domain Controllers
HTTPS
OnCall Dispatch Architectural Diagram
Many Virtual
Servers
Live traffic Standby traffic
Many Standby
Virtual Server
VNET
Legend
Raster tile
Reverse geocode
Routing
Raster tile
Reverse geocode
Routing
Map Service
Interface Server
Rest API
Virtual
Server
Standby
Virtual Server
Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
5 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
Esri Software
Mapping Server #1, 2, 3 (Production)
Windows Server
Esri Software
Qty: 3
Mapping Server #1, 2, 3 (DR)
Windows Server
Esri Software
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 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
Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
6 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 / CLETS
- Query to Tiburon RMS
- Query to CJIC (County jail system)
- Query to Alameda Warrant System (AWS)
HxGN OnCall Dispatch | Notifications (Qty: 1)
HxGN OnCall Dispatch | CAD Link (Qty: 1)
- Tiburon RMS
HxGN OnCall Dispatch | Fire Link (Qty: 1)
- ImageTrend FRMS and ePCR
HxGN OnCall Dispatch | Call-Taker Interface (Qty: 1)
- RapidSOS
HxGN OnCall Dispatch | PTT (Qty: 1)
- Motorola MCC7500 radios
HxGN OnCall Dispatch | Fire Station Printing (Qty: 1)
- Rip-n-Run
Standard Interfaces:

Body Worn Camera OnCall Interface (Qty: 1)
- Axon
CAD to CAD OnCall Dispatch Interface (Qty: 1)
- I/CAD 9.4 (Santa Clara County)
RapidSOS OnCall Call-Taker Interface (Qty: 1)
Fire Station Alerting OnCall Dispatch Interface (Qty: 1) - Zetron
Custom Interfaces:

CryWolf Bidirectional
California AB953 / RIPA
Query to Tiburon RMS
Query to CJIC (County jail system)
Query to Alameda Warrant System (AWS)
Custom Fields/Forms:

Tow
Supervised Release Form (SRF)
Rap Sheet
SVS (stolen vehicles)
Third Party Product:

CommSys ConnectCIC (for NCIC/CLETS)

Application Server #1a, 2a
Windows Server
ISM Services included with OnCall Dispatch
HxGN OnCall Dispatch | Customer Rules Engine Server (Qty: 2) Qty: 2
CAD MS SQL AlwaysOn Cluster
Archive Database Server #1a
Windows Server
Microsoft SQL Server 2022 SE with SA
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.

Web Server #1, 2
Windows Server
IIS (included with Windows Server)
HxGN OnCall Dispatch | Advantage CCU* (Qty: 7)
HxGN OnCall Dispatch | Essentials CCU* (Qty: 1)
- for animal control
HxGN OnCall Dispatch | Viewer CCU (Qty: 4)
HxGN OnCall Dispatch | Dashboard CCU (Qty: 3)
HxGN OnCall Dispatch | Advanced Mapping CCU *** (Qty: 7) HxGN OnCall Dispatch | Esri Map Control CCU (Qty: 7)
HxGN OnCall Dispatch | Resource Management CCU (Qty: 7) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 7)
HxGN OnCall Dispatch | Customer Rules Engine Adv Client (Qty: 7) HxGN OnCall Dispatch | Customer Rules Engine Editor (Qty: 1) HxGN OnCall Dispatch | Mobile Unit CCU** (Qty: 65)
HxGN OnCall Mobile Server (Qty: 2)
HxGN OnCall Dispatch | Mobile Responder CCU** (Qty: 20) * Includes ANI/ALI functionality
** Includes AVL functionality
*** Includes PLT functionality

Qty: 2

Database Server #1, 2
Windows Server
Microsoft SQL Server 2022 EE with SA
Intergraph Licensing Server
Qty: 2
Smart Advisor Web Application Server #1, 2, 3
Windows Server
Mongo Database
OnCall Dispatch | Smart Advisor CCU (Qty: 12)
OnCall Dispatch | Smart Advisor Mobile CCU (Qty: 65)
OnCall Dispatch | Smart Advisor Unit Agents (Qty: 1)
Qty: 3
OnCall Analytics Reporting Server
(with Data Warehouse)
Windows Server
IIS (included with Windows Server)
Microsoft SQL Server 2022 EE with SA
Power BI Report Server (included with SQL EE
with SA)
SQL Server Data Tools (download)
Visual Studio 2019
HxGN OnCall Analytics | Dispatch Advantage

Reporting Database Server
(Read Only DB Copy)
Windows Server
Microsoft SQL Server 2022 EE with SA

Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
7 OnCall Dispatch Disaster Recovery Environment
Communications/Interface Server #1c
(Cold Backup)
Windows Server
HxGN OnCall Dispatch | RestAPI
Xalt Runtime Engine
COTS Interfaces:

ANI/ALI Interface (included with OnCall Dispatch)
HxGN OnCall Dispatch | Informer (Qty: 1)
HxGN OnCall Dispatch | Notifications (Qty: 1)
HxGN OnCall Dispatch | CAD Link (Qty: 1)
HxGN OnCall Dispatch | Fire Link (Qty: 1)
HxGN OnCall Dispatch | Call-Taker Interface (Qty: 1)
HxGN OnCall Dispatch | PTT (Qty: 1)
HxGN OnCall Dispatch | Fire Station Printing (Qty: 1)
Standard Interfaces:

Body Worn Camera OnCall Interface (Qty: 1)
CAD to CAD OnCall Dispatch Interface (Qty: 1)
RapidSOS OnCall Call-Taker Interface (Qty: 1)
Fire Station Alerting OnCall Dispatch Interface (Qty: 1) Third Party Product:

CommSys ConnectCIC (for NCIC/CLETS)

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
Windows Server
ISM Services included with OnCall Dispatch
HxGN OnCall Dispatch | Customer Rules Engine Server (Qty: 2) Qty: 2
Communications/Interface Server #2c
Windows Server
HxGN OnCall Dispatch | RestAPI
ANI/ALI Interface (included with OnCall Dispatch)
Web Server DR #1, 2
Windows Server
IIS (included with Windows Server)
HxGN OnCall Dispatch | Advantage CCU* (Qty: 7)
HxGN OnCall Dispatch | Essentials CCU* (Qty: 1)
- for animal control
HxGN OnCall Dispatch | Viewer CCU (Qty: 4)
HxGN OnCall Dispatch | Dashboard CCU (Qty: 3)
HxGN OnCall Dispatch | Advanced Mapping CCU *** (Qty: 7) HxGN OnCall Dispatch | Esri Map Control CCU (Qty: 7)
HxGN OnCall Dispatch | Resource Management CCU (Qty: 7) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 7)
HxGN OnCall Dispatch | Customer Rules Engine Adv Client (Qty: 7) HxGN OnCall Dispatch | Customer Rules Engine Editor (Qty: 1) HxGN OnCall Dispatch | Mobile Unit CCU** (Qty: 65)

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

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
CAD MS SQL AlwaysOn Cluster
Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
8 CAD Test & Training Environments
Test Application Server #1, 2
Windows Server
ISM Services included with OnCall Dispatch
HxGN OnCall Dispatch | Customer Rules Engine Server (Qty: 2) 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
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
Intergraph Licensing Server
OnCall Dispatch Training Environment
Training Web Application Server
Windows Server
HxGN OnCall Dispatch | RestAPI
HxGN OnCall Dispatch | Advantage CCU (Qty: 2)
HxGN OnCall Dispatch | Resource Management CCU (Qty: 2) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 2)
HxGN OnCall Dispatch | Customer Rules Engine Adv Client (Qty: 2) HxGN OnCall Dispatch | Customer Rules Engine Server
HxGN OnCall Dispatch | Mobile Unit CCU** (Qty: 5)

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)
Test Web Server #1, 2
Windows Server
IIS (included with Windows Server)
HxGN OnCall Dispatch | Advantage CCU* (Qty: 7)
HxGN OnCall Dispatch | Essentials CCU* (Qty: 1)
- for animal control
HxGN OnCall Dispatch | Viewer CCU (Qty: 4)
HxGN OnCall Dispatch | Dashboard CCU (Qty: 3)
HxGN OnCall Dispatch | Advanced Mapping CCU *** (Qty: 7) HxGN OnCall Dispatch | Esri Map Control CCU (Qty: 7)
HxGN OnCall Dispatch | Resource Management CCU (Qty: 7) HxGN OnCall Dispatch | ProQA Interface CCU (Qty: 7)
HxGN OnCall Dispatch | Customer Rules Engine Adv Client (Qty: 7) HxGN OnCall Dispatch | Customer Rules Engine Editor (Qty: 1) HxGN OnCall Dispatch | Mobile Unit CCU** (Qty: 65)
HxGN OnCall Mobile Server (Qty: 2)
HxGN OnCall Dispatch | Mobile Responder CCU** (Qty: 20)

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
Attachment 1

Color Legend
Black – Base products
Red – Optioned products
Green – Customer-furnished products
Sunnyvale, CA Phase 2
OnCall Dispatch
Hardware & Software Configuration

April 2024
9 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 separate 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 specifications 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 physical 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 utilization. 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 capability 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 cluster 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 environment, 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 Microsoft policy.

13. Hexagon assumes that the Customer will provide a rack with sufficient space, power, and cooling.

15. The Operational Reports component of OnCall Dispatch is normally configured to point to the archive server which is normally 5-15 minutes behind production on information. For those customers that find this acceptable the read-only reporting replica is not required. For those that feel the need to have the data pulled directly from live or those that plan to create additional customized operational reports, the read-only replica is recommended to prevent performance impacts from malformed reports.

Attachment 1

City of Sunnyvale, CA
On-Premise OnCall Dispatch Implementation
Statement of Work 105
Attachment G – CAD/Mobile Functional Specifications
Identified in Phase 1 Fit & Gap

[following this page]

Attachment 1

CITY OF SUNNYVALE

FIT AND GAP ANALYSIS
JULY 2023
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 1 Attachment 1

Fit and Gap Analysis
Hexagon Safety & Infrastructure Page 1 of 10
© 2021 Intergraph Corporation. All rights reserved.

The content of this document is proprietary work of Intergraph Corporation, or relevant third parties, and is protected by copyright law and international treaty. Duplication of this document is permissible with employee identification of Intergraph Corporation. All rights in content or materials bearing copyright notice or other attribution of third-party rights are reserved to the relevant third party. United States Government license rights are limited to those mandatory rights identified in DFARS 252.227-7015(b).

Intergraph may make improvements and/or changes in the products and/or the programs described in this publication at any time without notice.

Any content or materials supplied hereunder are provided "as is," without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of merchantability, fitness for a particular purpose, or against infringement. In no event shall Intergraph be liable for any damages arising out of, or in connection with the downloading, viewing, use, duplication, distribution or disclosure of any content or material published by Intergraph, including but not limited to any direct, indirect, incidental, special, punitive or consequential damages, or loss or corruption of data.

Some jurisdictions do not allow the exclusions or limitations set forth above, so the above may not apply to you.

The exclusions or limitations shall apply in all jurisdictions to the maximum extent allowed by law.

Intergraph Corporation
P.O. Box 240000
288 Dunlop Blvd.

Huntsville, AL 35813
Phone: +1.256.730.2000
Toll Free USA: +1.800.345.4856
Fax: +256.730.2048.

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 2 Attachment 1

Fit and Gap Analysis

Version History
Date Author Comments
7/10/2023 Ginny Wilcox/Deirdre Irwin Initial document
7/21/2023 Amber Ahmed Content Review
7/24/2023 Donno Cole Content Review

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 3 Attachment 1

Fit and Gap Analysis
Hexagon Safety & Infrastructure Page 3 of 10

Contents
Introduction ................................ ................................ ................................ ............................... 4 Purpose ................................ ................................ ................................ ................................ . 4 Methodology................................ ................................ ................................ .............................. 5 Identified Gaps ................................ ................................ ................................ .......................... 6 OnCall Dispatch ................................ ................................ ................................ .................... 6 OnCall Mobile Unit/Mobile Responder ................................ ................................ ................... 7 Reporting ................................ ................................ ................................ .............................. 7 Interfaces ................................ ................................ ................................ .............................. 8 Recommendations ................................ ................................ ................................ .................... 9 Wrap-Up ................................ ................................ ................................ ................................ ... 10 GIS Implementation................................ ................................ ................................ ............. 10 Functionality Differences at a Glance ................................ ................................ .................. 10

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 4 Attachment 1

Introduction
The Fit and Gap Analysis, including the attachments hereto, provided by Intergraph Corporation by and through its Hexagon Safety, Infrastructure & Geospatial division (“Hexagon”) to the City of Sunnyvale (“Customer”) describes the findings provided by Hexagon based on the prioritized requirements traceability matrix (RTM).

Purpose
The purpose of this document is to identify the methodology utilized by the Hexagon team to discover gaps in the OnCall Suite as related to the prioritized technical requirements matrix (RTM). In addition, the items have been classified into respective methods of addressing any perceived gap(s).

The Hexagon team has also included a high-level difference between on-prem versus a hosted solution for the Sunnyvale deployment.

The focus for the Fit and Gap was to analyze the requirements for OnCall Dispatch, OnCall Mobile Unit, OnCall Mobile Responder and OnCall Analytics.

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 5 Attachment 1

Fit and Gap Analysis
Hexagon Safety & Infrastructure Page 5 of 10
Methodology
To optimize the analysis of the requirements, the Hexagon team used several approaches. These included the following:
• In-depth discussion and demonstration of the prioritized technical matrix items during on-site visits
• Guest speakers to discuss GIS, Hardware/Infrastructure, Informer, Analytics (SaaS solution) and Mobile Responder
• Lab access
The technical requirements matrix (RTM) was prioritized by the Sunnyvale team prior to the on-site visits.

Further review of the CAD requirements was conducted by the Sunnyvale team to identify topics which required further explanation.

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 6 Attachment 1

Fit and Gap Analysis

Identified Gaps
The technical requirements matrix has been added as an addendum to this report with further detailed explanation. The Hexagon team has highlighted items which were discovered during the on -site visits.

This section identifies noted gaps and organizes them in the following classifications:
• Roadmap – the requirement has been added to a future version of the software. • Additional Module – the functionality will require an additional module to be purchased/licensed • Product Change Request (PCR) - a request for additional functionality or modification to the purchased Cloud Application(s) or Covered Products.
• Out of Scope (OOS) – functionality not in scope for the OnCall Suite. • Infrastructure Dependent – dependent on how security is defined by the client • Configuration – can be configured with current software parameters

OnCall Dispatch
Functionality Classification
Support for command line Roadmap
Accelerator/Shortcut Keys PCR
Send message to all units on call Additional Module (“CRE”) Multi-line command line Roadmap – Intelligent command line Persistent command line PCR
Partial event numbers Roadmap
Maintain timestamps on reopen PCR
Need a method to deactivate an employee
gracefully
The license can be checked in via the
Administrator Portal which will log out the
individual immediately.

Preempt Unit – default to put call back into
pending automatically (no popups)
Configuration
Add supplemental data to a closed event PCR
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 7 Attachment 1

Fit and Gap Analysis
Hexagon Safety & Infrastructure Page 7 of 10

Functionality Classification
QIH (Query Incident History) – need synopsis
of event at top, i.e., units on call, timers,
callers
Roadmap
Need disposition code in Location History PCR
Search functionality needs to support free
text dates along with calendar
PCR
Ability to define custom date frames for
searches, i.e. 3 months
PCR

OnCall Mobile Unit/Mobile Responder
Functionality Classification
Mobile Device Manager (MDM) OOS – recommend contacting neighboring agencies like Santa Clara
Forwarding informer returns to another
mobile unit
Routing rules can be defined to allow
supervisor or covering dispatcher to receive if
authorized.

Reporting
Functionality Classification
SSRS OOS for hosted solution
OnCall Analytics - Scheduling OOS for hosted solution
OnCall Analytics – Paginated reports Available 1Q24 for hosted solution; Available now for on-premise
OnCall Analytics – initial event type not
stored
PCR
OCA – dispatch employee required PCR
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 8 Attachment 1

Fit and Gap Analysis

Functionality Classification
OCA – full complement up to 18 PCR – logic to support configurable full complement parameter (current hard-coded
max is 15)
Ability to search system history for events PCR - OnCall does not provide any mechanism to search changes in coverage
(dispatch group). "System" shutdowns or
restarts are only in the application logs files
on the servers involved in the system and is
n/a for cloud deployments. There is no way
to search the user history table from within
the product.

Interfaces
Functionality Classification
AniAli – confidence factor/probability circle Available. Configuration to make visible on caller card.

Zetron – model 6203 document provided
which identifies IP as an option
Additional Module (Fire Station Alerting);
serial connection not supported.

Zetron – notification of success or failure PCR
Fire Station Printing (Rip and Run) OOS for hosted solution; available for on- premise
Informer CLETS/CommSys Additional Module – tow and SRF
Crywolf – bi-directional traffic PCR for the pull of contact information from Crywolf data into OnCall
Mugshots/CalPhoto OOS per CalPhoto
Informer/CommSys – attach query return to
closed event.

PCR

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 9 Attachment 1

Fit and Gap Analysis
Hexagon Safety & Infrastructure Page 9 of 10

Recommendations
Based on discussions with the Sunnyvale team, Hexagon noted the following suggestions for Sunnyvale to aid in moving forward:

• GIS – Sunnyvale to open discussions with ESRI to discuss aliases, special addresses, commonplace names
• Review capabilities of FlowMSP for preplans
• Follow-up with IT and CLETS coordinator on Mobile Responder MDM requirements • Paging provider will need to be identified (PageGate) Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 10 Attachment 1

Fit and Gap Analysis

Wrap-Up
After spending several weeks with the Sunnyvale team, Hexagon identified these areas for further investigation internally at Sunnyvale to assist in decision making.

GIS Implementation
As ESRI is currently being utilized by the city for mapping, the OnCall suite would be an extension of the map work in progress today. Discussions highlighted areas which ESRI would assist with, i.e., base map, geo-locator, routing and any applicable layers.

In addition, Hexagon’s methodology for supporting the GIS effort is to provide consulting and follow-up support throughout the implementation process.

Functionality Differences at a Glance
Functionality On-Premise Hosted Solution
Scheduling of Reports

Available Not Available
Rip and Run Available Not Available
Hardware All hardware on-site Only an on-premise
interface server required
on-site
Database Access Authorized personnel have
full access
No direct access to
database
Maintenance Sunnyvale IT personnel
responsible for all hardware
Sunnyvale IT personnel
responsible for on-premise
interface server

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 11 Attachment 1

City of Sunnyvale
Fit & Gap Report
OnCall Dispatch 10.00.2303
Revision 1.0
© 2023 Intergraph Corporation. All rights reserved.

The content of this document is proprietary work of Intergraph Corporation, or relevant third parties, and is protected by copyright law and international treaty. Duplication of this document is permissible with employee identification of Intergraph Corporation. All rights in content or materials bearing copyright notice or other attribution of third party rights are reserved to the relevant third party. United States Government license rights are limited to those mandatory rights identified in DFARS 252.227-7015(b).

Intergraph may make improvements and/or changes in the products and/or the programs described in this publication at any time without notice.

Any content or materials supplied hereunder are provided "as is," without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of merchantability, fitness for a particular purpose, or against infringement. In no event shall Intergraph be liable for any damages arising out of, or in connection with the downloading, viewing, use, duplication, distribution or disclosure of any content or material published by Intergraph, including but not limited to any direct, indirect, incidental, special, punitive or consequential damages, or loss or corruption of data.

Some jurisdictions do not allow the exclusions or limitations set forth above, so the above may not apply to you. The exclusions or limitations shall apply in all jurisdictions to the maximum extent allowed by law.

Intergraph Corporation
P.O. Box 240000
288 Dunlop Blvd.

Huntsville, AL 35813
h
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 12 Attachment 1

Revision Date Author Comments

1.0 7/10/2023 Ginny Wilcox/
Deirdre Irwin
Initial Document Creation

1.1 7/24/2021 Donno Cole TD Reviewed for Delivery

1.2 7/25/2023 Amber Ahmed Reviewed for Delivery

Phone: +1.256.730.2000
Toll Free USA: +1.800.345.4856
Fax: +256.730.2048.

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 13 Attachment 1

Vendor Compliance Code Percent
Yes Y
Reporting R
Third Party T
Modification M
Not Available N
Functionality is provided through customization to the application, including creation of a new workflow or development of a custom interface, that may have an impact on future upgradability.

Functionality is not provided. Functionality may be provided through a future general availability (GA) release that is scheduled to occur within 1 year of the proposal response.

Confirm Priority, Availability, Definitions and Conditional Formatting:

Definition
Functionality is provided out of the box through the completion of a task associated with a routine configurable area that includes, but is not limited to, user-defined fields, delivered or configurable workflows, alerts or notifications, standard import/export, table driven setups and standard reports with no changes.

T
hese configuration areas will not be affected by a future upgrade. T he proposed services include
implementation and training on this functionality, unless specifically excluded in the Statement of Work, as part of the deployment of the solution.

Func
tionality is provided through reports generated using proposed Reporting Tools.

Func
tionality is provided by proposed third party functionality (i.e., third party is defined as a separate software vendor from the primary software vendor). T
he pricing of all third party products that provide this functionality MUST be included in the cost proposal.

Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 14 Attachment 1

Number CAD Functional Requirements Vendor
Compliance Comments DISPATCH

PRIORITY
DPS
Group NOTES
1 2
Two incident formats shall be provided for the entry of incident information, one for calls for service from the public, and the other suitable for officer initiated activity from the Mobile Data Terminals in vehicles.

Y H D/S
3 Validation shall take one second or less. N
This functionality is dependent on customer-
provided geocoder. Response time is directly
related to GIS performance.

H
4 The response priority shall be a function of the incident type but enterable by the call taker as well. Y M
5 The incident details shall allow at least 240 characters of text to be entered at one time and the ability to preview multiple lines of text prior to entering call for service.

Y Can add 8192 characters per remark,
unlimited remarks per incident. M
6 Vehicle information shall be recorded as data items, not just text.

Y Via Supplemental data in CAD Incident. L
7 The officer form shall allow the easy entry of unit,
location, and vehicle license information; this should pull from the officer’s login information.

Y Officer login process allow permissions set up
by Administrator to be used. L
8 After initial entry of information, the system shall verify the incident location against a geographical database (GIS
GEO file).

Y M
9 The system shall automatically search its database for previous incident history and shall retrieve and display summaries of the five most recent incidents at the
location.

Y
Not limited to 5; will have scrollable list if more
than displayable area. Listed in newest to
oldest.

H
10 The system shall automatically search its databases for reporting party information and shall retrieve and display summaries of the five most recent contacts with the
reporting party.

Y
Not limited to 5; will have scrollable list if more
than displayable area. Listed in newest to
oldest.

L
11 The system shall search its databases for vehicle history and shall retrieve and display (for traffic stops) summaries of the most recent five contacts with a vehicle whenever one is entered as part of an incident.

Y
Not limited to 5; will have scrollable list if more
than displayable area. Listed in newest to
oldest.

M
12 The system shall automatically search its databases for street information and shall retrieve any available
information about the street location from the
geographical databases.

Y L
13 The most important available information shall be
automatically displayed for dispatchers with indicators to alert the dispatcher to the availability of other pieces of information.

Y M
CAD General Requirements
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 15 Attachment 1

14 The system shall have the ability to cancel a hold placed on a pending event, AND if pending event placed on hold status, CAD shall have a feature where the call
automatically returns to pending status when the officer becomes available.

Y Via Hold Event and/or Dispatch Assign. M
15 The system shall have the ability to “stack” calls, and steal stacked calls from other users in an event the initial user becomes unavailable.

Y M
16 When the user commits the transaction, the system shall assign a system generated incident number to the
incident and record the date, time and dispatcher
handling the call.

Y M
17 Ability to handle multiple types of public safety agencies within the same jurisdiction:

C
18 Law Enforcement Y C
19 Fire Y C
20 Ability for CAD workstation to manage both call taking and dispatching functions.

Y C
21 Ability to maintain compliance with published NENA NG- 911 standards.

Y L
22 Ability to provide dedicated fields to capture all CAD transactions in an audit log.

Y M
23 Ability to support remote access to CAD. Y M
24 Ability to perform the following via remote access: M 25 Monitor Units Y M
26 Monitor Incidents Y M
27 Create Incidents Y M
28 Dispatch Incidents Y M
29 Run Queries Y M
30 Ability to access a browser-based CAD on a PDA (e.g., smartphone, tablet).

Y M
31 32 The system recognizes and provides for simultaneous handling of multiple transactions.

Y C
33 The system utilizes function keys for frequently used CAD transactions, e.g. incident initiation.

Y H
34 The system automatically checks reference data files during data processing.

Y H
35 The system shall not have pop-up windows that block a user from performing commands and effectively freeze
the system until the pop-up windows are clear
Y C
36 The system automatically validates entered data with automatic presentation of valid values when an invalid
value is entered.

Y Based on fields defined. There are also free
form text areas. M
37 Ability for users to customize window views, including, but not limited to:

H
38 Font size Y
39 Font color N
40 Font type N
41 Window background color Y Only night and day mode available CAD Application User Interface
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 16 Attachment 1

42 Window sizes Y
43 Window locations Y
44 Fields displayed Y
45 Order in which fields are displayed Y
46 Ability to have multiple windows open at the same time (e.g., multiple incident entry windows). Y H
47 Ability for the agency to determine which window
configuration options are configurable at the user level. Y User workspaces are defined in HxGN OnCall Administrator. H
48 Ability to save windows configurations based on user login, irrespective of workstation. Y H
49 Ability to maintain window configuration settings during upgrades. Y H
50 Ability to reset configuration to default settings. Y M 51 Ability to display system messages without affecting work in progress. Y M
52 Ability to tile or cascade multiple windows on screen. Y Based on the native OS Windows
management tools. HxGN OnCall Dispatch
does not manage this.

L
53 54
The command entries consist of a command identifier
and data parameters in conjunction with a function key (if necessary).

Y L
55 Menu selection is available for all functions that are performed by occasional, casual users of the system. Y L 56 Function keys are used for single key retrieval of blank incident forms. Y M
57 The system utilizes standard Windows shortcut keys (ctrl + z). Y L
58 The system Incident Histories and Unit Histories shall be easy to read and easy to retrieve. End users shall be able to pull up these histories by clicking on or typing minimal information. Thes
e histories should have incident
numbers and times included and show times for all
officers attached to the call. Times shall include: time call was received, time of entry, time of dispatch, time of en- route, time of on-scene and time of clear. Unit and time stamps shall be easily identifiable and back end system comments should not be included in the Incident Histories or Unit Histories. CLETS and NCIC inquires will be
attached to incident and unit histories.

Y C
59 The system supports execution and maintenance of
simultaneous events.

Y C
60 County Message Switch (to make CLETS queries from
within CAD & RMS) and return NCIC queries
T Via HxGN OnCall Dispatch Informer and third
party CommSys ConnectCIC
C **MIGHT NOT BE ABLE TO DEMONSTRATE WITH DOJ

CONNECTION
61 Ability to support data entry via: C
62 Mouse (point and click) Y C
63 Command line Y C
64 Preformatted masks Y C
65 Ability to execute any CAD function using the mouse (list exceptions).

Y H
CAD General Data Entry
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 17 Attachment 1

66 Ability to provide multiple command lines. Y C
67 Ability to support: H
68 Drop down menus Y H
69 Auto-completion Y H
70 Ability to execute any CAD function using the keyboard (list exceptions). Y With exception of some map features (Create Event Here, What's This functionality) L
71 Ability to create a new command line with a single
keystroke.

Y H
72 Ability to link a command line to a distinct incident. Y H

PURSUITS, ETC- MIGHT BE EASIER ON ENTRY
WINDOW - HxGN final comment: related to Persistent
Command line
73 Ability to enter commands in any order on the command line.

Y M FLEXIBLITY IN COMMAND STRING HxGN final comment:
related to configuration/redesign
74 Ability to enter more than one command on a single
command line.

Y M
75 Ability to send the same comments via one command to any unit associated with an event/incident.

Y M
76 Ability to click on the map and populate the address field with the corresponding location information.

Y H
77 Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to: M
78 Text wrap Y M
79 Paragraph formatting Y M
80 Bullets and numbering Y M
81 Copy and paste Y H
82 Grammar check N None outside of what the Operating System provides
L
83 Spell check N None outside of what the Operating Systems provides
L
84 85 Ability to automatically time stamp all system
transactions.

Y H
86 Ability to manually create a time stamp. Y M
87 Ability to manually override a time stamp. Y M
88 Ability to capture the time a time stamp was overridden. Y M 89 Ability for all overridden time stamps to be recorded as a manually entered, override time.

Y M
90 91
Ability to configure incident timers based on agency-
defined parameters (e.g., unit status updates, incident type, incident status) and times.

Y H
92 Ability to associate timers with: M
93 Unit status updates Y M
94 Incident type Y M
95 Priority type Y M
96 Incident status (e.g., remained in pending for 20 minutes) Y M CAD Timers
CAD Time Stamps
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 18 Attachment 1

97 Ability to alert user to the expiration of the timer via: H 98 Audible alert Y L
99 Visual alert Y M
100 Ability to configure the alerts to repeat at agency-defined intervals until the timer has been reset. N M
101 Ability to manually set timers. Y M
102 Ability to record acknowledgement of timer alert. Y M 103 Ability to provide the following options when a status timer expires: M
104 Modify to new time value Y M
105 Reset to default value Y M
106 Stop timer Y M
107
108
Ability, upon entering an address, to automatically present user any flags/alerts associated with the address,
including but not limited to:

C
109 Hazard information Y C
110 Premise history Y C
111 Ability for alerts to include: H
112 Audible alert Y L
113 Visual alert Y H
114 Ability to require dispatchers to acknowledge that they have viewed hazards. N M HxGN final comment: parameter setting can be set to write in comments that they have been viewed
115
Ability, when querying a name, for user to be notified of an associated alert (e.g., if the subject is flagged in the RMS, wanted via CLETS/NCIC).

Y H
116 Ability to drill down into flags to display additional information. Y L
117 Ability to display incident history of address when creating an incident. Y H
118 Ability for users to sort summary of past incidents by: H 119 Chronological order (most recent call shown first) Y H 120 Call type Y H
121 Ability for user to add a flag/alert. Y M
122 Ability to set an expiration for a flag/alert. Y M
123 Ability to add a temporary flag, comment or note to a location. Y M
124 Ability to notify agency-defined personnel of pending expiration of a temporary flag. N M
125 Ability to include flagged information with dispatches sent to responding units. Y H
126
** MOST

MIGHT NOT

BE AVAIL
DURING
PHASE 1
CAD Flag and Alerts
CAD Multiple Screen Functionality
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 19 Attachment 1

127
Ability to interface with jail booking photos from Santa Clara County TIPS System.

Requesting for interface to the Santa Clara Clara County Mugshot System
M
Hexagon has proposed an Informer query
interface to County Mugshot system. The
query is by Name/DOB, OLN or SSN. Please
see Attachment 2 for more detail.

HxGN Final comment: Discussed taking this interface out with the team
128
Document Imaging (transfers photos and associated
identifying information into RMS).

NG911 will specifically be enabling photos, video, and
multi-media texts that need to integrate with CAD
N
OnCall Dispatch does not have the ability to
transfer attachments such as photos to the
RMS.
129
Cogent AFIS (transfers AFIS ID number into RMS MNI
record and sends Live Scan mandated fields back to
AFIS; bi-directional). The City currently views this as an RMS function. However, we are looking for best overall value on the proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
130
Ability to interface with Santa Clara County EIS to support the collection of information from the RMS and populate it into the JMS pre-booking module.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
131
The system supports the ability to import data from field- data collectors such as handheld computers, smart
phones, etc.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
132
The system has the ability to produce an electronic file for submission to the California DOJ E-CARS system. N
Hexagon has proposed our OnCall Dispatch
CAD system. This interface would only be
available in an RMS.
133 The system has the ability to send files, photos and videos directly to the District Attorney N
Hexagon has proposed our OnCall Dispatch
CAD system. This interface would only be
available in an RMS.
134
The system provides / supports an interface with
electronic cite software.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This interface would only be
available in an RMS.
135
The system has the ability to interface with Tiburon for warrants and TIPS.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
M
Hexagon has proposed an optional Informer
query interface to Tiburon warrant and TIPS.

The query is by Name/DOB, OLN or SSN.

Please see Attachment 2 for more detail.
136
The system provides / supports an interface with I/Leads The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 20 Attachment 1

137
The system provides / supports an interface with
SmartJustice.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
138
The system provides / supports an interface with
Copperfire or other accident reporting feature.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
139 The system provides /supports integration with a body cam solution (WatchGuard,
Axon) Y
Hexagon has proposed an Axon Interface to
meet this requirement. Please see
Attachment 2 for more detail.
140 The system has the ability to update code table for municipal issues Y
Administrator in OnCall Dispatch Can update
event code and subtype tables for OnCall
Dispatch.

HxGN final comment: Assume code tables are related to
RMS
141
The system provides an interface capable of selectively sharing CAD and RMS data with other agencies either
using the same product or a competitive product.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
142
The system provides / supports an interface with citizen online reporting software.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
143
The system has the ability to integrate with our city
website (cop logic) for citizen reports
The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
144
System provides/supports an interface with Santa Clara
County ARIES.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
145 System provides/supports an interface with TabletPCR. Y Hexagon has proposed an optional HxGN
OnCall Dispatch | CAD Link interface to AMR
Tri-Tech.

Please see Attachment 2 for more detail.

C HxGN final Comment: ImageTrend is the ePCR system and is included in solution
146
System provides/support an interface for Crime Mapping.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
Y
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 21 Attachment 1

147
System provides/supports an interface with Zoll Fire RMS including ZMS (Zoll Message Switch).

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has not proposed this interface as
part of our solution, but can provide a CAD
interface to Zoll FireRMS upon request.

HxGN Final comment: ImageTrend ePCR and FRMS is
included and was advised Zoll
148 System provides/supports an interface with ProQA.

Please specify if interface is one or two way, Y
Hexagon has proposed OnCall Dispatch |
ProQA Interface to meet this requirement.

The interface is bi-directional.

Please see Attachment 2 for more detail.

C
149
System provides/supports an interface with Santa Clara
County Health Services Division’s PCR software.

This is referencing the same ePCR system as
represented in the interfaces section
Y
Hexagon has proposed OnCall Dispatch |
CAD Link Interface to meet this requirement.

Please see Attachment 2 for more detail.

HxGN comments - this is part of the ImageTrend system
150 System provides/supports an interface to be used with mobile app (Mobile PD).

Y OnCall Dispatch Mobile Responder (using
IOS and Android OS)
C
151
System provides/supports an interface to be used with
AMR Tri-Tech.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
Y
Hexagon has proposed an optional OnCall
Dispatch | CAD Link Interface to meet this
requirement. Please see Attachment 2 for
more detail.

HxGN comments - this is part of the ImageTrend system
152 System provides/supports an interface to be used for CAD Paging module or similar feature. Y
Hexagon has proposed HxGN OnCall
Dispatch | Notifications to meet this
requirement.

C
HxGN comments - OnCall Dispatch can be configured to
page but needs to connect to a paging system to send the page
153 System provides/supports an interface for Fire
Department current Rip-N-Run. Y
Hexagon has proposed HxGN OnCall
Dispatch | Fire Station Printing to meet this
requirement.

C HxGN comments - Gap identified for hosted solution
154 System provides/supports an interface for Zetron (Ring down for Fire Stations). Y
Hexagon has proposed HxGN OnCall
Dispatch | Fire Station Alerting to meet this
requirement.

C
155
System provides/supports an interface for Cogent Live
Scan. Please specify if this is a one way or two way
interface.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
156
157 Data entered into the system either directly or indirectly is propagated to all relevant databases.

Y L
158 Data entered into the system either directly or indirectly is available to all relevant system functions.

Y L
159 All modules of the system are completely integrated. Y H **NOT SURE HOW TO SEE AN EXAMPLE 160 Once entered, there is no requirement for re-entry of data to satisfy the needs of a different sub-system. Y
Hexagon clarifies that sub-systems would be
the OnCall Mobile Unit and OnCall Mobile
Responder.

L
161
162
The system supports a call taker taking the call, filling in the incident form, and routing the call to the appropriate dispatcher.

Y C
163 The system shall route the incident to the appropriate dispatch position.

Y L
CAD Single Point Data Entry
CAD Call Taker / Dispatcher Functionality
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 22 Attachment 1

164 The dispatcher receives an audible and/or visual
indication that a new incident has arrived for dispatch. Y H 165
The system shall be flexible enough to allow any position to be used for any system function, dispatching, call
taking, and records.

Y C
166 Changing a workstation’s function shall not require reconfiguration of the system. Y H
167 Data entered into the system either directly or indirectly is available to all relevant system functions. Y H
168 Once entered, there is no requirement for re-entry of data to satisfy the needs of a different sub-system. Y M
169
170
171 Ability to receive call data from: C
172 E9-1-1 phone system Y C
173 Non-emergency 10 digit phone numbers Y Yes, provided they are routed through ANI/ALI M 174 Private alarm companies Y M
HxGN comment- ASAP to PSAP is not available in the state - since this isn't high priority this wasn't discussed. We have included CryWolf
175
Ability to automatically create a call for service when a 9-1- 1 call comes in through the phone system (e.g., create a call and open a call entry mask):

C
176 Administrative hard wired phone line Y H
177 Hard wired 9-1-1 phone line Y H
178 Wireless 9-1-1 line Y H
179 Ability to transfer calls to another agency. Y
Hexagon clarifies (If event has not been
created) select a different agency than what
was originally selected.

OR (if event has been created) use the
Transfer Event command to transfer the event
to the other agency.

L
180 Ability to capture and track to which agency a call is transferred. Y
Hexagon clarifies (If event has not been
created) select a different agency than what
was originally selected.

OR (if event has been created) use the
Transfer Event command to transfer the event
to the other agency. Both workflows are
tracked and timestamped in system.

L
181
182 Ability to enter incidents using preformatted screens. Y H 183 Ability for the agency to determine what data elements are captured as part of the preformatted screen.

Y H
184 Ability to attach multimedia messages (MMS), including videos or pictures taken by citizens, to a call. Y
As long as the file types being attached have
been configured to be accepted by the system
administrator
H
185 Ability to provide dedicated fields to enter the following information:

C
186 Individual (caller, witness, suspect) Y C
187 Multiple individuals Y C
CAD Call Receipt
CAD Call Data Entry
CAD Call Taking
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 23 Attachment 1

188 Vehicle Y C
189 Location Y C
190 Ability for call taker to add comments to a call after it has been dispatched. Y C
191 Ability to alert dispatcher that the call taker has added information by: C
192 Audible alert Y C
193 Visible alert Y L
194
Ability to provide dedicated fields to capture all incoming call information from the E9-1-1 system, including, but not limited to:

H
195 Caller name Y H
196 Caller telephone number Y H
197 Caller address/location calling from Y H
198 Incident location Y H
199 Alternate telephone number Y H
200 Cellular phone service provider Y Yes Administrative configuration M 201 Phase I or Phase II indication Y M
202 X/Y coordinates Y Yes Administrative configuration M 203 Text messages (assuming phone system is NG911
capable) Y
Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

Please see Attachment 2 for more detail.

L **OTT SYSTEM CURRENTLY HxGN Final Comment: Per
Sunnyvale they were going to use RapidDeploy for texting 204 TTY conversation Y
Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

Please see Attachment 2 for more detail.

L
205 Any other information captured by the E9-1-1 system Y 206
Ability to automatically populate CAD screen with
information from E9-1-1 application, without manual
intervention.

Y H
207
Ability to populate CAD screen with information from E9-1- 1 application via manual intervention (e.g., function key, mouse click).

Y H
208 Ability to generate an incident from a previous incident. Y M REOPENING INCIDENTS 209
210 Ability to receive geographic coordinates from a cellular telephone carrier.

Y M
211 Ability to relate X/Y coordinates to an actual address. Y M 212 Ability to transform X/Y coordinates to a map for display. Y H 213 Ability to capture incident location separately from caller location.

Y H
214 Ability to enter a location for an event by the following methods:

H
215 Street address Y H
216 Block number or address range Y H
217 Commonplace name Y H
218 Landmark Y H
CAD Location Capture
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 24 Attachment 1

219 Intersecting street names Y H
220 X/Y coordinates Y Long/Lat M
221 Point and click on a map Y H
222 Ability to suggest locations based on type-ahead
capabilities for: H
223 Street addresses Y Based on map data H
224 Intersections Y Based on map data H
225 Commonplace names Y Based on map data H
226 Ability to type in either street first when entering intersections. Y Based on map data M
227
Ability to save intersections as identical address points regardless of order of streets entered (e.g., 1st/Main
same as Main/1st).

Y Based on map data M
228 Ability for system to automatically parse address data into address data fields including:
229 Street number Y Processed by customer geocoding provider, stored as JSON H
230 Street name Y Processed by customer geocoding provider, stored as JSON H
231 Street prefix Y Processed by customer geocoding provider, stored as JSON H
232 Street suffix (NW, SW, NE, SE) Y Processed by customer geocoding provider, stored as JSON H
233 Street type (Av, Ln, Bd, "None") Y Processed by customer geocoding provider, stored as JSON H
234 Unit type Y Processed by customer geocoding provider, stored as JSON M
235 Unit number Y Processed by customer geocoding provider, stored as JSON M
236 City Y Processed by customer geocoding provider,
stored as JSON M
237 Ability to capture the following information upon receipt of a wireless 9-1-1 call:
238 X/Y coordinates Y if sent in packet from source M
239 Street address of tower Y if sent in packet from source M 240 Nearest cross street Y if sent in packet from source M 241
242 Ability to geoverify location of all entered addresses. Y H 243 Ability to override geoverified location. Y H
244 Ability to validate an entry upon: H
245 Operator request (e.g., press a button) Y H
246 Entry into location field Y H
247 Ability to offer a list of address options if multiple similar addresses/intersections/street names are found in geofile. Y H 248 Ability to display closest address matches based on: M 249 Block ranges Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
250 Building name Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
CAD Location Verification
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 25 Attachment 1

251 Business name Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
252 Common place names Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
253 Intersections Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
254 Phonetic spelling Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
255 Soundex Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
256 Street name Y Provided the data is available in Azure maps, or customer's chosen geocoder M HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
257 Ability to display an unlimited number of common place names during the address verification process. Y Not unlimited, but configurable amount of suggestions via MaxAutocomplete parameter M
258 Ability to log all locations that fail geofile validation. Y M 259 Ability to create a report of all overridden geoverified locations.

R Via OnCall Operational Reports or OnCall
Analytics
M
260 Ability to use the ALI reported location address for address verification.

Y M
261 Ability to support Phase I wireless location validation from cellular callers.

Y L
262 Ability to support Phase II wireless location validation from cellular callers.

Y L
263
Ability to notify dispatcher if multiple street
addresses/street names/intersections with the same
names are found in geofile.

Y Based on customer map data and Address
verification service(s) M
264 Ability to enter a valid street name and be presented with: H 265 Aliases Y
Provided the data is available in Azure maps,
or customer's chosen geocoder
H HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
266 Associated address ranges Y Provided the data is available in Azure maps, or customer's chosen geocoder H
HxGN final notes: Hexagon no longer uses Azure in the
SaaS solution - we now use the customers ESRI. This
feature would be based on what ESRI returns
267 List of cross streets Y Provided the data is available in Azure maps, or customer's chosen geocoder
H HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
268 Ability to translate call location to appropriate public safety geographical boundary (e.g. district, beat, sector). Y Provided the data is available in Azure maps, or customer's chosen geocoder H HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
269
Ability to translate alias names to actual street names or addresses.

Y Provided the data is available in Azure maps,
or customer's chosen geocoder
H HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
270
Ability to display, on a map the incident location in relation to other active incidents on the map during the incident entry process.

Y Provided the data is available in Azure maps,
or customer's chosen geocoder H HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
271
Ability to manually verify an address without creating an event.

Y H
272
273 Ability to display a drop down list containing incident types.

Y H
274 Ability to support unique Police and Fire call types. Y H CAD Call Classification and Prioritization
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 26 Attachment 1

275 Ability to override incident priority. Y H
276 Ability for an authorized user to assign a priority to a location for a agency-defined period of time. Y Via Special Situation / Special Address in HxGN OnCall Administrator M
277 Ability to allow the authorized user to manually upgrade or downgrade the system-assigned priority. Y H
278 Ability for dispatcher to change call type without impacting active call data. Y C
279
280 Ability to initiate an incident from the input of location and type code. Y H
281 Ability to input all call and narrative information on one screen. Y H
282
Ability to display a blank form for entering new incidents with a single keystroke, mouse click or function key upon initiation of a CAD incident.

Y H
283 Ability to copy an existing incident to create a new incident at the same location. Y H
284 Ability to enter incidents using:
285 Standard call entry screen form Y H
286 CAD command on a command line Y M
287 Map by clicking on a location Y H
288
289 Ability to enter incidents scheduled for dispatching at a later time, maintaining the original time of entry. Y H 290 Ability to modify incidents scheduled for dispatching at a later time, maintaining the original time of entry. Y H 291
Ability to generate a call for service at specified intervals (e.g., directed patrol 5 hours after the last directed patrol left).

N
OnCall Dispatch can create a schedule for a
specific time, but not based on criteria such
as all units having left seen after five hours.

L **CAN HOLD CALLS
292 Ability for scheduled incident to automatically enter the pending queue. Y H
293 Ability for officers to self-dispatch to scheduled incidents. Y M **NEED ABILITY TO SET PARAMETERS BASED ON UNIT ID
294
295 Ability to automatically identify potential duplicate calls based on: M
296 Incident/call type Y M
297 Proximity to current incident Y M
298 Time parameter Y L
299 Specific incident address/event location Y H
300 Phone number Y L
301 Ability to display proximity calls on a map (e.g., to assist dispatchers in identifying possible duplicate calls). Y H 302
Ability for the agency to configure the duplicate call
identification algorithm (e.g., defined proximity, definition of "recently closed").

Y Via OnCall Administrator H
303 Ability to include the following in the potential duplicate call identification process: M
304 Recently closed calls Y M
305 Pending calls Y M
CAD Incident Initiation
CAD Incident Scheduling
CAD Duplicate Call Management
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 27 Attachment 1

306 Self initiated calls Y M
307 Active calls Y M
308 Ability to manually identify a duplicate call and transfer the duplicate call information into the primary call. Y H
309 Ability to provide the dispatcher with the following information about possible duplicate incidents: H
310 Incident details Y H
311 Caller phone number Y H
312 Incident status Y H
313 Incident type Y H
314 Time the incident was initiated Y H
315 Units assigned Y H
316 Original dispatcher Y M
317 Ability for the dispatcher to do any of the following if a CAD incident is determined to be a duplicate call: H
318
Add to the original incident record a second complainant with complete complainant information and additional
incident comments
Y H
319 Close a duplicate incident and cross-reference it to the original CAD incident Y H
320 Create an entirely new incident using existing address data Y H
321 Ability to filter duplicate calls out of reports. R Via OnCall Operational Reports or OnCall Analytics L
322
323
Ability to automatically initiate, upon address verification, an address inquiry to search for associated premise
information in CAD.

Y H
324 Ability for premise information searches to query for flagged information in the RMS. N L
325 Ability to search for premise information on locations not associated with incidents. Y H
326 Ability to automatically show premise history related to a current incident. Y H
327 Ability to indicate the number of past incidents at a location. Y H
328 Ability to record in the incident history that premise history has been viewed by the user. Y
OnCall Dispatch records when a user views
the incident record, not when they view
specific details, such as premise history or
supplemental information.

M HxGN Final note: OnCall does document this in the current release
329
Ability to recall any incident or premise history that has been viewed (e.g., does not allow for only one time view of premise history or incident).

Y H
330
Ability for premise information to be available to user but not prevent operator from continuing current work (e.g., window does not cover entire workstation screen).

Y C
331 Ability to search for premise information based on:
332 Address Y H
333 Sub-address (e.g., unit number, building floor, apartment number)
Y H
CAD Premise Information Retrieval
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 28 Attachment 1

334 Partial address information (e.g., all addresses with apartment 14) Y
Can use LOI radius to define area of concern
for a given event type, which can emulate a
sub address area
H
335 Block ranges Y
Can use LOI radius to define area of concern
for a given event type, which can emulate
block range
L
336 Current business name Y M
337 Historic business name (unlimited number) Y L
338 Common place names Y M
339 Intersections Y M
340
Ability to retrieve and attach to a CAD call any information associated with the premise (e.g., pre-plan information, previous calls for service).

Y C
341 Ability for map to display all known hazards within a user- defined radius.

Y H
342
343
344 Ability to alert a dispatcher to the arrival of a new incident via:
345 Audible alert Y L
346 Visual alert Y C
347 Ability to alert a dispatcher to the arrival of new incident information via:
348 Audible alert Y L
349 Visual alert Y C
350
Ability to retrieve a CAD incident and review all available information already entered up to the point of incident retrieval.

Y C
351 Ability to sort pending incidents by:
352 Priority Y H
353 Location Y L
354 Incident type Y M
355 Time in pending queue Y M
356 Ability to keep incidents in pending queue indefinitely. Y L 357
358
Response algorithms shall be based on incident location, incident type, and unit availability. System must have capability of allowing for recommendation of closest
available unit based GPS location using and Automatic
Vehicle Location System.

Y C
359
For police responses, the recommendation shall show the beat unit, if available or an unavailable unit from an
adjoining beat if the beat unit is not available.

Y C
360
The dispatcher shall be able to accept the recommended
dispatch with a single key or edit the recommendation as needed.

Y C
361
For officer initiated incidents, the unit will be the unit calling; the unit will be entered on the initial incident form and dispatch shall be automatic.

Y C
CAD Incident Retrieval
CAD Resource Recommendation
CAD Dispatching
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 29 Attachment 1

362
Ability for each agency using the CAD system (i.e., Police and Fire) to enable and disable agency-specific resource recommendations.

Y C
363
Ability to support numerous resource recommendation
algorithms based on agency defined parameters (e.g.,
priority 1 calls are dispatched according to closest,
available unit and all other calls are dispatch based on beat assignments).

Y C
364
Ability to prioritize unit response based on incident type so that appropriate units are automatically recommended
and/or dispatched in priority order.

Y C
365 Ability to re-recommend closest units when a new unit comes into service.

Y M
366
Ability for system to update the unit recommendation if user makes relevant incident information changes (e.g., type, location, alarm level).

Y C
367 Ability to record the unit recommendation as it was presented to the dispatcher.

Y L
368 Ability to automatically provide appropriate resource recommendations based on any combination of:
369 AVL location Y C
370 Beat/Station Location responsibility Y C
371 Closest unit taking into account:
372 Natural boundaries Y
Provided the data is available in Azure maps,
or customer's chosen geocoder and routing
service used
H HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
373 Obstacles Y
Provided the data is available in Azure maps,
or customer's chosen geocoder and routing
service used
L HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
374 Traffic Y
Provided the data is available in Azure maps,
or customer's chosen geocoder and routing
service used
L HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
375 Speed limits Y
Provided the data is available in Azure maps,
or customer's chosen geocoder and routing
service used
L HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
376 Street network Y
Provided the data is available in Azure maps,
or customer's chosen geocoder and routing
service used
L HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
377 Street direction Y
Provided the data is available in Azure maps,
or customer's chosen geocoder and routing
service used
L HxGN final notes: Hexagon no longer uses Azure in the SaaS solution - we now use the customers ESRI
378 District Y H
379 Equipment availability Y C
380 Incident location (e.g., unique response for specific location)
Y C
381 Incident type Y C
382 Incident priority Y C
383 Occupancy type (e.g. residential, office building) Y C 384 Pre-defined response plans (response area plan) Y C 385 Special conditions (e.g., heightened response) Y H
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 30 Attachment 1

386 Special equipment required Y H
387 Special skills units required Y H
388 Type of units required Y H
389 Number of units required Y H
390 Unit status Y H
391
392 Ability for the agency to develop response plans based on:
393 Geographic area (beat, sector, district, fire zone box etc.) Y C 394 Address Y C
395 Multiple response route configuration (e.g., divided highway). Y C
396 Time of day Y L
397 Fire alarm level Y C
398 Call type Y C
399 Fire pre-plan Y H
400 Resource availability Y C
401 Station coverage requirements Y C
402 Ability to assign a single response plan with multiple call types. Y C
403
Ability to accommodate unique response plans based on
fire district (e.g., District 1 requires an engine, District 2 requires an engine and a rig).

Y H
404 Ability to include multiple agencies in response plans. Y C 405 Ability to generate temporary response plans. Y C
406 Ability for user to override response plan
recommendation. Y C
407 Ability to load a new response plan without stopping or pausing application operations. Y C
408
Ability for a communications supervisor to update the
response plans (e.g., without assistance from technical support or vendor).

Y With correct Role permissions. C
409
410 Ability to bring up a list of special skills/equipment for:
411 All personnel logged on Y H
412 A selected person Y M
413 Apparatus/vehicle Y M
414 Ability to identify all personnel with a specific skill (e.g., language, training) by:
415 Logged on and available Y M
416 Logged on and not available (e.g., on another incident) Y M 417 Not logged on Y M
418 Ability to display potentially available resources based on unit status:
419 Assigned to a CAD call Y M
420 Assigned to a CAD call with a lower priority Y M
421 Unassigned Y M
422
CAD Response Plans
CAD Resource Determination
CAD Resource Dispatch
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 31 Attachment 1

423 Ability for dispatcher to select and assign/re-assign recommended units using any of the following methods:
424 Command line entry Y C
425 Function key Y H
426 Mouse (drag and drop onto map) Y H
427 Ability to dispatch units by:
428 Accepting the proposed application recommended units Y C 429 Selecting and dispatching units other than those
recommended by the application Y C
430 Selecting some, but not all, of the recommended units Y C 431 Ability to log recommendation overrides in the audit trail (e.g., recommended units and dispatched units). Y Separate log files per incidents. M 432 Ability for CAD to do the following upon dispatch:
433 Assign the recommended or requested units Y C
434 Remove the incident from the pending queue Y C
435 Send the incident to the assigned unit's mobile computer Y C 436 Start the status timers Y C
437 Update the status display Y C
438 Ability to dispatch more than one unit at a time to the same call. Y C
439 Ability to assign or add multiple units to an incident with a single command. Y C
440 Ability to assign a unit to an incident to which it was not originally recommended. Y C
441 Ability to provide sender notification that dispatches have been successfully delivered. Y C
442
Ability to automatically notify agency-defined personnel (e.g., Battalion Chiefs) of calls for service meeting agency- defined parameters.

Y Via HxGN OnCall Dispatch | Notifications C
443
444 The officer form shall be designed to facilitate entry of traffic stops. Y L
445 Ability for field personnel to initiate a call for service from the mobile computer (e.g., traffic stop). Y H ** OTHER OFCR INITIATED CALLS- NOT TRAFFIC STOP 446 Ability to add additional units to a self-initiated incident. Y H 447 Ability to capture AVL coordinates when field personnel initiate a call for service from the mobile computer. Y H 448 Ability to geovalidate addresses of self-initiated incidents. Y H 449 Ability to provide dedicated fields to record the following information when a unit is placed in a traffic stop status:
450 Location of the stop Y H
451 Number of occupants in the vehicle Y L
452 Vehicle license plate Y H
453 State of registration Y H
454 Vehicle identifier (make, model, color) Y L
455 Driver information Y H
456 Ability to limit field self-initiated calls to specific call types. Y Set by Agency administrators based on login privileges of officer. H
CAD Self-Initiated Calls for Service
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 32 Attachment 1

457
458 Ability to update unit status to associate the dispatched unit or units with the CAD incident. Y H
459 Ability to take a unit off a call and reassign the unit to a new call via:
460 Single command Y H
461 Drag and drop Y H
462
Ability to use one command to both dispatch and put "on scene" field personnel (e.g., if field personnel is "out with another unit").

Y H
463 Ability to hold an incident for a specific unit. Y H 464
Ability to automatically (without user intervention) notify the dispatcher of a held incident when the unit becomes available.

N L HxGN Final note: using DispatchNextQEonClear setting the unit can be assigned to the held incident automatically 465
466 Ability to pull a unit off an incident and reassign the unit to a new incident.

Y H
467 Ability to return CAD incident to the pending dispatch queue if all units are removed from an active incident.

Y H
468 Ability to visually indicate a preempted call (e.g., color code).

N L
469 Ability to support a swap feature to allow two units to swap incidents with a single command.

Y H
470
471 Ability to identify station coverage deficiencies based on minimum staffing levels by apparatus type. N
OnCall Dispatch interfaces with third party
Deccan to do this workflow. It is not currently
proposed but can be provided upon request.

L
472 Ability to recommend move-ups based on:
473 Fixed station order N
OnCall Dispatch interfaces with third party
Deccan to do this workflow. It is not currently
proposed but can be provided upon request.

C
474 Current vehicle location (e.g., AVL) N
OnCall Dispatch interfaces with third party
Deccan to do this workflow. It is not currently
proposed but can be provided upon request.

C
475 Alarm levels Y C
476 Ability to:
477 Accept move-up recommendations N
OnCall Dispatch interfaces with third party
Deccan to do this workflow. It is not currently
proposed but can be provided upon request.

C
478 Override move-up recommendations N
OnCall Dispatch interfaces with third party
Deccan to do this workflow. It is not currently
proposed but can be provided upon request.

C
479 Ability to reverse move-ups as apparatus clear calls. Y Standard functionality, manual via command line or mouse.

C
480 Ability to distinguish between assigned units and units in move-up or cover status.

Y Via Status in Unit Status Board. H
481
482 Automatic SMS text based on incident type is supported. Y Via HxGN OnCall Dispatch | Notifications H HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.

CAD Unit Assignment to CAD Incident
CAD Call Preemption
CAD Fire Move-Up Management
CAD Integrated Texting
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 33 Attachment 1

483 Manual SMS message is supported. Y Via HxGN OnCall Dispatch | Notifications C HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
484 Individuals can receive text messages. Y Via HxGN OnCall Dispatch | Notifications C HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
485 Groups can be defined and paged as a group. Y Via HxGN OnCall Dispatch | Notifications C HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
486 Automatic SMS messages include incident information already entered by the call taker. Y Via HxGN OnCall Dispatch | Notifications H HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
487
The software includes all screens necessary to maintain SMS text information for users, groups, and to define
paging required for particular types of incidents.

Y Via HxGN OnCall Dispatch | Notifications L
HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
488 Text messages shall be saved to a searchable file with a 3-year retention period. Y Messages are saved in related message tables. L
HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
489 Ability support sending text messages directly from CAD. Y Supports SMPP, SMTP, SNPP, WCTP C HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
490 Ability to support unlimited text characters (if limited in characters, please specify limit in comments). Y To the limits of the supported protocols:

SMPP, SMTP, SNPP, WCTP M
HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
491
Ability for dispatch of a unit to trigger a text to agency- defined personnel, based on a configurable algorithm
including:
492 Call type Y Via HxGN OnCall Dispatch | Notifications H HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
493 Alarm level Y Via HxGN OnCall Dispatch | Notifications H HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
494 Incident location Y Via HxGN OnCall Dispatch | Notifications M HxGN Final Comments: Alphanumeric messages can be
transmitted from the dispatch environment over the third- party paging terminal to the destination paging unit.
495 Time of day N L
496 Unit N L
497 Ability to include the following information in the text:
498 Call type Y Via HxGN OnCall Dispatch | Notifications H 499 Call location Y Via HxGN OnCall Dispatch | Notifications H 500 Time of day Y Via HxGN OnCall Dispatch | Notifications L 501 Date Y Via HxGN OnCall Dispatch | Notifications M
502 Initial comments N M
503 Ability deliver texts to additional numbers, in the event that the initial text is unsuccessful.

N L
504 Ability to reattempt to deliver unsuccessful texts for an agency-defined length of time.

N L
505 Ability to record delivery confirmation in the CAD audit trail.

N L
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 34 Attachment 1

506 Ability to record the time the text was read in the CAD audit trail. N L
507 Ability to manually initiate texts. Y Via messages in OnCall Dispatch H 508
509
510
The system must have the “Free a Unit” or "Preempt"
command to return a unit to a clear status but not close the incident the unit has been assigned.

Y C
511
The system must have the command “Reassign a Unit” to
reassign a unit from one incident to another, returning the first incident to a pending status rather than closing it if there are no other units assigned to the first incident.

Y Dispatch Assign functionality C
**DON'T WANT EXTRA POP UP BOXES ASKING IF IM
SURE TO DROP BACK TO PENDING - HxGN Final
comment: There is a setting now that you can set to prevent this
512
The system must have the command “Exchange Units” to
dispatch a unit to an incident while simultaneously
clearing a unit it is replacing.

Y H
513
The system shall have an easily entered “pursuit mode”
to facilitate entry of continuous narration of vehicle and foot pursuits. In pursuit mode, each time the dispatcher presses ENTER the current entry shall be recorded with a time stamp and a new entry line presented.

N H
**THROUGH HXG- MIGHT JUST BE CALL MASK
INSTEAD OF A LOCK COMMAND LINE…. HxGN Final
Comment: Persistent Command line PCR would be
required
514
The system must show unit locations that are changed
while already assigned to an event and should be easily visible to all units with an MDC i.e.: perimeter locations of multiple units on an event using AVL or a location entered by dispatch.

Y C
515
The dispatcher must be able to hold one or more pending incidents for a particular unit with an indication in the incident status display.

Y M
516 Ability to log one or more units on-duty/off-duty with a single command.

Y H
517 Ability to automatically assign a beat to a unit upon logon. Y H 518 Ability to assign a unit to multiple beats. Y
OnCall Dispatch can handle with deployment
definitions if it affects recommendation
(beat/backup beat)
L
519 Ability to modify a unit's assignment during a shift. Y H 520 Ability to define a roster (e.g. squad, company). Y Lineup H 521 Ability to place all units in a previously defined roster on or off-duty.

Y Lineup H
522 Ability to allow for a single unit exception when placing a roster on or off duty.

Y L
523 Ability to log a fire apparatus into service without tying individuals to the apparatus.

Y L
524 Ability to associate multiple individuals with a unit. Y H 525 Ability to identify fire units with special equipment. Y H 526 Ability to designate a unit available for only certain types of calls.

Y M
527 Ability for units to log themselves into or out of service. Y H CAD Unit Management
CAD Unit Handling Functions
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 35 Attachment 1

528 Ability to prevent units from logging themselves into and out of service Y
OnCall Dispatch can remove the ability to run
the into and out of service commands from
units. Capability is in HxGN OnCall Dispatch |
Administrator
L
529 Ability to indicate a unit does not have a mobile computer. Y H 530 Ability to place an apparatus back in service when it is within an agency-defined radius of its station.

Y H
531
532 Ability to recognize an apparatus for multiple purposes (e.g., apparatus serving as both truck and engine).

Y H
533 Ability to identify company personnel capable of staffing multiple resources.

Y H
534 Ability to assign company personnel to the appropriate apparatus depending on the nature of the emergency.

Y L
535 Ability to remove an apparatus from service if personnel are not available to staff the apparatus.

Y M
536 Ability to place an apparatus back in service when
personnel are available to staff the apparatus.

Y M
537
538 Ability to monitor an unlimited number of units. Y C 539 Ability to display the following unit information:
540 Beat Y C
541 Call type Y C
542 Company Y C
543 Current incident number Y C
544 Current location Y C
545 Current status Y C
546 Division Y C
547 Elapsed time in status Y M
548 Last known location Y M
549 Logged onto Mobile (Y/N) Y M
550 Original location Y Recorded in Unit History M
551 Radio ID Y L
552 Reporting district Y L
553 Special note or comments Y L
554 Special skills/training Y L
555 Station Y H
556 Unit ID/call sign Y H
557 Vehicle number Y M
558 Ability to automatically update and display unit status data.

Y H
559 Ability to sort displayed data by any unit information (e.g., station, shift, incident, unit, location, status).

Y H
560
Ability to filter the units to be displayed in a single status monitor (e.g., by response area, discipline, type, status, out of service (mechanical)).

Y H
561 Ability to visually differentiate, through color, text and/or symbols, unit status:

CAD Cross Staffing
CAD Unit Status Display
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 36 Attachment 1

562 On CAD unit status display Y By symbols and text not by color. H 563 On map display Y By symbols and text not by color. H 564
565 Ability to record all unit assignments. Y C
566 Ability to record all unit locations. Y C
567 Ability to record all unit status changes. Y C
568 Ability to review unit status history within the CAD application. Y C
569 Ability to update location and note mileage for multiple stops. Y M
570 Ability to record multiple arrival times, including:
571 Arrival at a staging area Y M
572 Arrival at the incident location (e.g., room within a building) Y M
573 Arrival at the scene (e.g., general location) Y C
574 Ability to record multiple units arriving:
575 At one time (all at once) Y H
576 At different times Y C
577 Ability to place "at the scene" units that were not originally dispatched to the call. Y H **ATTACH AND ONSCENE
578 Ability to assign (potentially multiple) units to a specific location which is different from the incident location. Y C 579 Ability for a dispatcher to change the location of a unit at any time while the unit is still assigned to an incident. Y C 580 Ability to update the location of a unit without altering the original incident location. Y C
581
582 Ability to initiate status changes via the following methods:
583 Data fields Y H
584 Function key Y H
585 Mouse click (e.g., screen icon) Y M
586
Ability to automatically notify users monitoring or
displaying the incident that information has changed via a visual alert.

Y C
587
588 Ability to clear one unit from a CAD incident while allowing the other assigned units to remain on the call. Y C
589 Ability to select any number of units to clear from CAD incident. Y C
590 Ability to clear all units simultaneously from a CAD incident. Y C
591 Ability to require a disposition to be entered prior to clearing the primary unit from a CAD incident. Y Not by primary unit but before clearing event a disposition can be Mandatory field. C
592
593
594 Ability to monitor an unlimited number of incidents. Y C CAD Status Monitoring
CAD Unit Clearance
CAD Incident Management
CAD Call Display
CAD Unit Activity Tracking
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 37 Attachment 1

595
Ability to dynamically display (e.g., automatically update) incident status data in a summary window (status
monitor).

Y C
596 Ability to review incident information in reverse
chronological order. Y H
597 Ability to display a window listing pending and holding incidents entered from any CAD workstation Y C
598 Ability to allow for an unlimited number of agency-defined incident statuses. Y C
599 Ability to view incident details of one or more incidents at a time. Y C
600 Ability to click on an active incident and highlight all assigned units in the unit monitoring window. Y L
601 Ability to show incidents on the CAD mapping display. Y C 602 Ability to accommodate multiple locations for one call. Y M **THIS SHOULD BE DONE W LOCATION UPDATES 603
604 Ability to add new or additional information to a CAD incident. Y C
605 Ability for multiple operators to simultaneously modify the same incident. Y C
606 Ability to automatically identify (e.g., ID stamp) the operator adding information to a call. Y C
607 Ability to display the following information when additional information is added to an incident:
608 Time information was added Y C
609 ID of person entering information Y C
610 Ability to display new information added to the incident without requiring the user to open the call. Y C
611 Ability to simultaneously notify dispatcher and dispatched units of updated information. Y C **MOBILE UNITS SHOULD ALSO BE ABLE TO TURN OFF

NOTIFICATION IF THEY WANT
612
613 Ability to reopen closed incidents. Y H
614 Ability to reopen a closed call without losing previously recorded date and timestamps. Y C
615 Ability to assign units to reopened calls. Y C
616
Ability for dispatchers to add comments to a CAD call
record after the call is closed without reopening the
incident.

Y C
617 Ability to add a case number to a closed incident. N Event must be open to assign a case number H **PREVIOUS HXG VERSIONS HAVE THIS ABILITY// DO

WE HAVE TO UPDATE CASE NUMBERING

CONVENTION
618
619 Ability to cross-reference two or more active incidents. Y H **PREVIOUS HXG VERSIONS COULD CROSS

RFERENCE PRIOR CALL AND ACTIVE CALL (CHECK

THAT COPYING A CALL DOESN'T CHANGE LOCATION

OF INCIDENT)
620 Ability to cross-reference active and closed incidents. Y H 621
622
623 Ability to cancel an incident with a single command. Y H CAD Reopening Incidents
CAD Cross-Referencing Calls
CAD Call Disposition
CAD Incident Cancellation
CAD Incident Updates
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 38 Attachment 1

624
Ability to mandate that the user enter a reason for
canceling an incident prior to the system executing the command to cancel.

Y H
625
Ability to automatically remove the incident from the
pending or active incidents queue and add the disposition (e.g., cancelled) upon execution of a command canceling an incident.

Y Can't cancel an assigned event H
626
Ability to automatically clear all dispatched units from the incident upon incident cancellation (e.g. upon invoking the cancel command).

N L
627
628 Ability for the agency to define disposition codes. Y C 629 Ability to filter disposition codes by agency (e.g., fire and law enforcement each have their own disposition codes). Y C 630 Ability to support an unlimited number of disposition types.

Y C
631 Ability to require a disposition code before an incident can be cleared.

Y C
632 Ability for either dispatchers or field personnel to enter the disposition code.

Y C
633 Ability to enter comments of an unlimited length with a disposition code. N Limit of 8192 character C
**CAN IT BE MADE IN COMMENTS VIA MDC? WILL

DISPATCH SEE THE COMMENTS FROM THE MOBILE
THAT'S ENTERED INTO THE CALL?
634
635 Ability to identify whether a report is required based on disposition code.

Y M
636 Ability to transfer call for service data to:
637 RMS Y Via OnCall Dispatch | CAD Link interface C
**EVEN IF INTERFACE CAN'T BE DONE DURING PHASE
1- COST/ PROCESS OF ENTERING PREVIOUS CAD
DATA
638 RMS Field Reporting application Y Via OnCall Dispatch | CAD Link interface C 639 Fire RMS/ePCR application Y Via OnCall Dispatch | CAD Link interface C 640 Ability to transfer call for service data:
641 Upon transfer to dispatcher Y H
642 Upon incident closure Y H
643 On demand (i.e., manual initiation of transfer) Y Can pull Case Number ad hoc H 644
645 Ability to close a call that does not require the dispatch of resources.

Y C
646
Ability to enter a closing disposition code at the time of call creation to avoid having the call appear in the
pending queue (e.g., call is created and closed prior to the dispatching of resources)
Y C
**CAN IT BE ACCOMPLISHED W/ A SPECIFIC TYPE
CODE AND NOT 'ADVISED'…HxGN final comment - yes
you can create an event type to automatically be an advised event
647 Ability to change an incident disposition after a call is closed, but maintain a history of the original disposition.

Y Must reopen the event to update disposition,
and history of original disposition is kept.

H
648
649
650 Ability for mapping functionality to be integrated into CAD application.

Y C
CAD Report Initiation
CAD Incident Closure
CAD Mapping
CAD Mapping General Requirements
CAD Disposition Recording
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 39 Attachment 1

651 Ability to select multiple map layers for display, limited only by the number of available map layers. Y C
652 Ability to display the following on the map:
653 Location of 9-1-1 caller Y C
654 Location of all pending and active 9-1-1 calls Y Assuming a call is associated with an event C 655 Incident location during address verification Y C
656 Units based on AVL or last known locations (regardless of status) Y C
657 Ability to select units to display on map by user-defined criteria including, but not limited to:

Filters can be defined to specify units to
display on the map.
658 Beat Y Filters based on sync with Event Board/Event Board Tab, Event List M
659 Incident number Y Filters based on sync with Event Board/Event Board Tab, Event List M
660 Incident type Y Filters based on sync with Event Board/Event Board Tab, Event List M
661 Reporting district Y Filters based on sync with Event Board/Event Board Tab, Event List M
662 Station Y Filters based on sync with Event Board/Event Board Tab, Event List M
663 Status Y Filters based on sync with Event Board/Event Board Tab, Event List M
664 Type Y Filters based on sync with Event Board/Event Board Tab, Event List M
665 Unit ID Y Filters based on sync with Event Board/Event Board Tab, Event List H
666 Ability to pull up a call for service and have it
automatically show up on the map. Y Assuming a call for service is associated with an event M *OPTION TO CONFIGURE
667 Ability to zoom in and center map display on:
668 Incident location during address verification Y M
669 CAD incident in active window Y M
670 Last known location of a selected unit (AVL or unit status) Y M 671 Vehicle activating emergency button Y L
672
Ability to prevent the zoom level from automatically
modifying during an active incident (e.g., not automatically zooming out when new units are added)
Y
Administrator function (parameter available to
not window/zoom to include units upon
selection)
H
673
Ability for operational user to close streets by clicking on a specific area (e.g., street, hundred block area) from the CAD map.

Y L
HxGN Final Comment: with ESRI now the base map in
SaaS this feature is available with ESRI Map Controller interface from CAD and/or Mobile users - if you want to use this feature
674 Ability for user to define an expected duration for street closures. Y L
HxGN Final Comment: with ESRI now the base map in
SaaS this feature is available with ESRI Map Controller interface from CAD and/or Mobile users - if you want to use this feature
675 Ability to alert user when the expected duration for a street closure has expired. Y L
HxGN Final Comment: with ESRI now the base map in
SaaS this feature is available with ESRI Map Controller interface from CAD and/or Mobile users - if you want to use this feature
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 40 Attachment 1

676 Ability to push closed street information to mobile computers. Y L
HxGN Final Comment: with ESRI now the base map in
SaaS this feature is available with ESRI Map Controller interface from CAD and/or Mobile users - if you want to use this feature
677 Ability to project anticipated response times between two points on a map.

Y C
678 Ability for dispatcher to view the quickest route (based on time) from dispatched unit location to incident.

Y H
679 Ability for dispatcher to view shortest route from
dispatched unit location to incident.

Y If configured to route by distance rather than
by time
H
680 Ability to view shortest route. Y If configured to route by distance rather than by time
H
681
682 Ability to create perimeter locations by drawing a
perimeter on the mapping display.

Y Geofence functionality H
683
Ability to create a perimeter by identifying the location and requisite perimeter size (e.g., 300 yards around incident location) and have the perimeter location automatically generated.

Y Geofence functionality H **USEFUL FOR 166A4
684
Ability to display the drawn perimeter on the map and
have it displayed for all responding units on their Mobile computers.

Y Geofence functionality H
685 Ability to dispatch units to perimeter locations. Y Units may be dispatched to any location C 686 Ability for units to place themselves on a designated perimeter location.

Y Units can place themselves wherever using
Change Location
C
687 Ability to annotate the map. Y Via Map Graphics L
688 Ability for a user's annotated map to be shared with other users.

Y Geofences created by other users can be
seen when activated by the user
L
689
690
691 The system allows the tracking of all units through GPS. Y Via OnCall Dispatch | Tracker (included with OnCall Mobile Unit and Mobile Responder)
C
692 The system allows the tracking of vehicles that enter a certain area (i.e. frequency, route, speeds).

Y Geofence functionality L
693 Ability to support the use of a continuous, real-time AVL system via a CAD interface.

Y Via OnCall Dispatch | Tracker C
694 Ability to automatically refresh current vehicle location at agency-defined intervals.

Y Via OnCall Dispatch | Tracker C
695 Ability to turn AVL on/off by:
696 Agency Y Via OnCall Dispatch | Tracker H
697 Unit Y Via OnCall Dispatch | Tracker H
698 Ability to default to agency-defined defaults for
dispatching when AVL is turned off.

Y C
699
Ability to automatically mark a unit on-scene when it
comes within a certain number of feet of the incident
location.

Y Via OnCall Dispatch | Tracker HALO C
700 Ability for the agency to define what constitutes on-scene. Y Via OnCall Dispatch | Tracker HALO H 701 Ability to prevent use of on-scene function if unit is not within an agency-defined radius of incident.

N L
CAD Automatic Vehicle Location
CAD Automatic Vehicle Location General Requirements
CAD Mapping Perimeters
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 41 Attachment 1

702 Ability to log the specific X/Y coordinate from where the unit was dispatched prior to responding to an incident. Y L 703
Ability to automatically mark fire apparatus status "en route" upon exiting the station when responding to a call for service.

Y C
704 Ability to provide an AVL playback utility. R Via OnCall Analytics | Dispatch Data Models and Reports L
705 Ability to generate reports from AVL data, including: R Via OnCall Analytics | Dispatch Data Models and Reports L
706 Vehicle route R Via OnCall Analytics | Dispatch Data Models and Reports L
707 Speeds along the route R Via OnCall Analytics | Dispatch Data Models and Reports L
708
709
710 The frequency of rotation shall be configurable, i.e., each call, daily, weekly, etc. Y M
*TRM/ TOW MONITOR IS CUMBERSOME ON PREVIOUS
HXG VERSION. IS IT CONNECTED TO A MASK/

INTERFACE FOR SVS SO VEHICLE DATA IS ALREADY
PREPOPULATED FOR SVS ENTRY?
711 The system shall be capable of allowing the manual
selection of “next up” on the tow list.

Y M
712 The selected tow company shall be recorded in the
incident record.

Y M
713 Ability to support an automated contractor rotation list. Y M 714 Ability for the application to recommend a contractor based on any combination of the following:

M
715 Equipment Required Y M
716 Type of tow Y M
717 Order in Rotation Y M
718 Incident Location Y M
719 Time of day (e.g., hours of operation) Y M
720 Agency Y M
721 Ability to automatically place a contractor at the end of the rotation list after selected for service.

Y M
722 Ability to record that a contractor was selected from the service rotation list.

Y M
723 Ability to recommend the next available contractor if the initial contractor is unavailable.

Y M
724 Ability to record reason why a contractor was not
selected.

Y M
725 Ability to record contractor response. Y M
726 Ability to place contractor at top of list if incident is cancelled.

Y M
727 Ability to override contractor recommendation. Y M
728 Ability to enter a contractor that is not part of the rotation. Y M HxGN Final Comment: if the vendor is defined then they can select out of rotation
729 Ability for all actions regarding the contractor rotation and selection to be associated with an incident record.

Y M
730
731 Ability to attach tow history to a call for service record. Y The tow history will record the event number H CAD Towed Vehicles
CAD Contractor Rotation List
CAD Towed Vehicle History
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 42 Attachment 1

732 Ability to document reason for the tow. Y H
733 Ability to associate multiple vehicles with a single tow incident. Y M
734 Ability to track the total number of vehicles towed per incident. Y L
735
736
737 Ability to create BOLs. Y C
738 Ability to provide an audit trail for BOLs. Y H
739 Ability for field personnel to create BOLs. Y H
**CLARIFY- INTERNAL BOLS (MESSAGES) OR ALL
POINT BULLETIN BOLS? HxGN Final Comment: BOL's
are done via broadcasts in OnCall - APB's can be done via a type of broadcast for internal and thru CLETS message
switch to notify agencies
740 Ability to associate a BOL with a case number. Y H
741 Ability to provide the following fields for a BOL record:
742 Date issued Y H
**CAN JUST BE OPEN SUMMARY/ TEXT LINE FOR ALL
THESE OPTIONS….HxGN final comments: the date is
editable and you don't have to use the calendar. There
should be an expired date assigned to any type of
broadcast. Minimal requirements are needed to create a
BOL such as type, expiration, and details..
743 BOL expiration date Y L
744 Nature of the BOL Y H
745 BOL priority Y L
746 Subject name Y H
747 Subject description: Y H
748 Height Y H
749 Weight Y H
750 Build Y H
751 Hair color Y H
752 Eye color Y H
753 Date of birth Y H
754 Known address or location Y H
755 Driver's license number Y H
756 Vehicle description Y H
757 Vehicle license plate Y H
758 Weapon (multiple) Y H
759 Known associates Y H
760 Last known location Y H
761 Direction of travel Y H
762 Contact Information Y H
763 Person issuing the BOL Y M
764 Agency issuing the BOL Y H
765 Additional information in free-form text field Y H
CAD BOLs
CAD BOLs General Requirements
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 43 Attachment 1

766 Ability to search for BOL based upon any of the data fields. N OnCall Dispatch can search BOLO on ID,
Type, Title, Event(s), Date/Time L
767 Ability to accommodate multiple subjects in a BOL. Y M 768 Ability to accommodate multiple vehicles in a BOL. Y M 769 Ability to accommodate multiple weapons in a BOL. Y M 770 Ability to attach a file to a BOL. Y H
771 Ability to embed a photo in a BOL. N OnCall Dispatch can add as attachment but not embed. L
772 Ability to update a BOL. Y H **UPDATE WITHOUT RETYPING THE WHOLE THING 773 Ability to set time limits for BOL retention. N
Dispatcher can close a broadcast (setting it
inactive); but not have it automatically expire
after a time
L
774 Ability to close a BOL. Y H
775 Ability to designate groups or individuals to whom BOLs should be sent. Y M
776 Ability to view history of recently created BOLs. Y L 777 Ability to archive expired BOL records. Y L
778 Ability to search expired BOL records. Y L
**SNY TENDS TO FORWARD CREATED CALLS AS

MESSAGES TO OFFICERS INSTEAD OF CREATING A
NEW BOL. …HxGN Final comment: BOL's are in a location where units can view at anytime and can also be resent
such as when a new shift starts.
779
840
900
901
902 Ability to support a messaging system that can transmit messages to and from mobile and desktop workstations. Y C 903 Ability to display the following identifiers within a message:
904 Sender name/ID Y C
905 Sender date Y C
906 Sender time Y C
907 Receiver name/ID Y L
908 Receiver date Y L
909 Receiver time Y L
910
Ability to send messages to a user who is not logged into CAD and cache that message for retrieval when the user
logs onto CAD.

Y L
911 Ability for message server to continuously attempt to deliver a message until received and confirmed.

Y L
912 Ability for user to retrieve cached messages upon logon. Y L 913 Ability to assign a priority to a message (e.g., routine, urgent, emergency).

Y M
914 Ability to store messages for later viewing. Y M
915 Ability for messages to be sorted by most recent or first received.

Y M
CAD Queries (moved to separate tab)
CAD Reporting and Query (moved to separate tab)
CAD Messaging
CAD Messaging General Requirements
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 44 Attachment 1

916
917 Ability to create and save message groups. Y H
918 Ability to send broadcast messages. Y M **DON'T USE BROADCAST- TEND TO MAKE CALL FOR

SERVICE AND FORWARD THE CALL TO UNITS
919
Ability for users to select any number of people as part of a message group with no limitation on the number of
people in a group.

Y H
920
Ability to enter unlimited narrative with wrap-around
feature (if characters are limited, indicate the maximum in the "comments" section).

Y Not unlimited; supports 10,000 characters C
921 Ability to automatically populate the "To" field on the message mask when selecting recipients. Y C **COMMAND LINE ABILITIY? 922 Ability to select recipient by:
923 Name Y L
924 Unit ID Y H
925 Badge Number Y L
926
Ability to select a recipient by a single command to create a message (e.g., double click on a logged on user and
message screen pops up).

Y H
927 Ability to attach files to messages. Y H
928 Ability to embed photos in messages. N L
929 Ability to set agency-defined file size limit. Y L
930 Ability to send a message to all units handling a specific incident. Y H
931
Ability to transmit a reply message to the originator of a currently displayed message without having to reenter the originator's address.

Y M
932
Ability to transmit a "reply all" message to multiple
recipients that were part of the originator's message
group.

Y H
933 Ability to forward a message. Y C
934 Ability to create messages that are retained in the system and sent at pre-specified times. Y M
935 Ability to provide a notification for delivery of messages to the device. N M
**MESSAGES TO MDC HAVE VISUAL OR AUDIO
ALERT….HxGN final note: visual indications and some
audio depending on type and settings
936
937 Ability to notify receiver via an audible and/or visual flag that a new message has arrived in mailbox. Y C
938 Ability to prevent incoming messages from interfering with current work. Y C
939 Ability to notify receiver of total number of unread messages. Y C
940 Ability for messages to be queued in an "inbox" for later viewing at the convenience of users. Y M
941 Ability to query message logs by agency-defined criteria (e.g., date/time range, sender, recipient, device). Y C 942 Ability to note time opened/read by receiver. Y L
943 Ability to clear a message from the queue. Y C
944 Ability to retain a message in the queue. Y M
CAD Sending Messages
CAD Receiving Messages
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 45 Attachment 1

945 Ability for supervisors to monitor messages. Y
Supervisors can monitor messages that they
receive and send, but not messages that they
are not included as a recipient on.

L **JUST NEED IT IN REPORTING….. HxGN final note: yes
this can be done in OnCall Analytics
946 Ability for supervisors to search messages by a text string (e.g., to identify inappropriate language use)
Y L
947 Ability to archive messages. Y C
948 Ability to save message logs for an agency-determined period of time. Y
This type of maintenance or manual archive
operation is not relevant in a managed service
environment.

L
**HOW LONG IS THE RETENTION? HxGN final
Response: How long do you require the information to be kept?
949 Ability to purge message logs for an agency-determined period of time. Y
This type of maintenance or manual archive
operation is not relevant in a managed service
environment.

L
950
951
952 Ability for CAD fields to default to agency-defined values. Y C 953 Ability to include, at a minimum, the following data tables:
954 Call source (e.g., officer-initiated, 9-1-1, 10-digit) Y C 955 Call types and priorities Y C
956 Commands Y C
957 Devices Y C
958 Dispositions Y C
959 Equipment Y C
960 Vehicle ID Y C
961 Event error logs (so vendor can identify and troubleshoot errors)
Y H
962 Patrol and command area definitions Y C
963 Personnel, including emergency contact information and current assignment
Y M
964 Timers Y H
965 Unit status types (i.e., assigned, unassigned, assigned but available)
Y H
966 Units Y C
967 Ability to accommodate agency-defined unit identifiers. Y C 968
969 Ability to configure commands (e.g., V = vehicle stop). Y C 970 Ability to create agency-defined data entry screens. Y C 971 Ability to configure the field entry sequence. Y C
972 Ability to configure status code colors. Y C
** EVEN WITHIN SAME DIVISION- PATROL CAN HAVE
BLUE OR RED CALLS TO INDICATE PRIORITY ….HxGN
final comments: unit colors are based on status
973 Ability to create conditional fields. Y C
974 Ability to create mandatory fields. Y C
975 Ability for agency to add data elements on any screen. Y M 976 Ability for agency to change data elements on any screen. Y M 977 Ability for agency to configure alerts:
978 Associated message displayed Y H
CAD Table Maintenance
CAD Configuration
CAD System Administration
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 46 Attachment 1

979 Audible indicator Y H
980 Visual indicator Y H
981 Ability to display strategic incident protocols (i.e. a task list) for agency-defined incident types. Y SOP functionality H 982 Ability for users to update progress as tasks listed in the strategic incident protocol are completed. Y L
983 Ability for the agency to create strategic incident protocols without vendor intervention. Y H
984 Ability for the agency to modify strategic incident protocols without vendor intervention. Y H
985
986 Ability to update/create CAD premise history files. Y C 987 Ability to automatically update premise history when an incident occurs. Y L
**SHOULD BE IN FILE MAINTENANCE- NOT IN LINE
USER ACCESS…HxGN final Comment: System will
automatically add history to a location.
988 Ability to capture the following information when creating premise history:
989 Date and time stamp Y H
990 Date of incident Y H
991 Disposition Y L
992 Type of incident Y H
993 Incident number Y L
994 Narrative text of unlimited length (if limited, indicate maximum in the "comments" field)
Y H
995 Ability to capture and maintain specific premise
information, including but not limited to the following:
996 Alarm/access information Y M
997 Emergency contact information Y M
998 Hazardous conditions (e.g., officer responder safety) Y M 999 Chemicals Y M
1000 Medical information Y M
1001 Agency defined premise information Y M
1002 Previous calls for service based on at least the following: Y M 1003 Address/Location Y M
1004 Contact information Y
1005 Date and time Y
1006 Incident number Y
1007 Incident type Y
1008
Ability to capture and maintain specific premise
information by groups of addresses (e.g., all apartments in an apartment complex, all houses in a subdivision).

Y
By using boundary definitions in Special
Situation functionality, or by using LOI radius
definition for event type
H
1009 Ability to store premise information for an agency-defined length of time.

Y H
1010
Ability to purge premise information from a location (e.g., if it is known that the tenant/owner generating the
incidents has moved).

Y H
1011 Ability to store premise information for a specific apartment unit/suite/building number.

Y H
CAD Premise File Maintenance
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 47 Attachment 1

1012
Ability to define valid date ranges for time limited premise information at a given location (e.g., information valid between <start date> and <end date>).

Y M
1013 Ability to archive expired premise file information. Y L 1014
Ability to include in a premise record the following
information when premise information is added or
changed:
1015 Expiration date Y H
1016 Unit ID of person entering information Y H
1017 Ability to attach files to a premise record (e.g., floor plans, building diagrams, special instructions). Y H
1018 Ability to access files attached to a premise record:
1019 In CAD environment Y H
1020 In Mobile environment Y H
1021
1022 Ability to enter hazards associated with:
1023 Persons Y M
1024 Specific locations Y H
1025 Address ranges Y M
1026 Vehicles Y M
1027 Ability to record with an entered hazard:
1028 Expiration date Y M
1029 Time and date stamp at time of entry Y M
1030 ID of person entering information Y M
1031 Ability to assign expiration dates to hazards. Y M 1032 Ability to create lists of hazards by category Y Via HxGN OnCall Dispatch | Administrator M 1033 Ability to print hazards and hazard lists R
Via HxGN OnCall Dispatch Operational
Reports or HxGN OnCall analytics Dispatch
Data Models and Reports
M
1034
1035
1036
Ability for a communications supervisor to monitor system configuration and current staffing (e.g., who is signed-on, at what position, and with what responsibilities).

Y
OnCall Dispatch has the ability to see who is
signed-on and what unit they are associated
with. However, not able to see what
responsibilities that they have.

C
1037
Ability for a CAD workstation to be configured as a
supervisor workstation upon logon of a user with a CAD
supervisor profile.

Y L
1038 Ability for a supervisor to choose logon type (supervisor vs. dispatcher) upon workstation logon.

Y L
1039 Ability for a communications supervisor to monitor activity on any user workstation.

Y Unit board and event board but not live map
interaction.

M
1040 Ability for supervisor to override actions taken by any other operator.

Y Can update; both actions will stay in history of
file.

L
1041 Ability to notify dispatcher of any changes made by supervisor.

Y L
1042 Ability to identify dispatch origin (e.g., dispatcher or dispatch supervisor) of modifications.

Y H
CAD Hazard File Maintenance
CAD Communications Supervisor Support
CAD Communications Supervisor Support General Requirements CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 48 Attachment 1

1043
1044
Ability to retain and display last-known unit and incident status in the event of a catastrophic system failure (e.g., at the workstation, remote external logging device or
similar solution).

N C
1045
Ability to load incidents from the backup environment into the production environment upon restarting system after a system failure.

Y C
1046 Ability to reset numbering after CAD system has been restarted.

Y C
1047 Ability to retain CAD numbering sequence after system has been restarted.

Y C
1048
Ability to add incidents retroactively independent of
incident number order or sequential time sequence (i.e., incident 15 may have occurred after incident 20) in the event that the CAD system is unavailable for a time.

Y
Events must be created with the next
available event number. Manual times may
be set for these new events. The manually
set times can occur before or after other
events entered into the system. The manual
times will be recorded to the event / unit
history
C
1049
Ability to process retroactive incidents and assign incident numbers in the same manner as new incidents; the
supervisor can override the times associated with the
incident.

Y M
1050
Ability to set aside a block of call for service numbers in the event of a catastrophic CAD failure to enable a
manual workflow and tracking.

Y M
1051 Ability to indicate in the audit trail that an incident was entered retroactively.

Y H
1052 Ability to perform CAD catch-ups after system downtime, without requiring users to log back in. N
A user must login if session has expired. If
the user session is still valid they will not need
to re-authenticate.

L
1053
1054
1055
The vendor shall provide all required data conversion
import into proposed system.

Data conversion scope will be determined after phase 1
discovery discussions
Y
Hexagon clarifies this includes static data only
as identified in section 6.6.8 of the proposal
response.
1056
The vendor shall provide existing (12 years) of data in our current AMS/RMS conversion
Data conversion scope will be determined after phase 1
discovery discussions
N
Hexagon has proposed migrating static data
only as identified in section 6.6.8 of the
proposal response.
1057
The vendor shall provide import 2 years of current CAD
records
Data conversion scope will be determined after phase 1
discovery discussions
N
Hexagon has proposed migrating static data
only as identified in section 6.6.8 of the
proposal response.
1058
The vendor shall import code tables
Data conversion scope will be determined after phase 1
discovery discussions
Y
Hexagon has proposed migrating static data
only as identified in section 6.6.8 of the
proposal response. Examples include Event
Type, Disposition Type, Out of Service and
Unit type codes.

CAD Recovery
Other
CAD Data Import
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 49 Attachment 1

1059
1060 Application must comply with AB953 law. Y
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required
to do racial profiling analysis in accordance
with AB953 and custom reports can be
generated from HxGN OnCall Analytics.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

C
** ALL PART OF REPORTING *** HxGN Final comment:

HxGN is building the AB953 product to the newest California requirements. This will be ready for January deadline
1061
Comply with mandates that Police agencies provide
reports on racial profiling (AB953). Does the system
contain tools or reports to assist with racial profiling analysis
Y
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required
to do racial profiling analysis in accordance
with AB953 and custom reports can be
generated from HxGN OnCall Analytics.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

C
System to contain tools or reports to assist with racial profiling analysis Y
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required
to do racial profiling analysis in accordance
with AB953 and custom reports can be
generated from HxGN OnCall Analytics.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

M
1062
Example of reports: how many times did individuals of a given race interact with the police, relative to the number of calls for service pertaining to individuals of that same race
R
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required
to do racial profiling analysis in accordance
with AB953 and custom reports can be
generated from HxGN OnCall Analytics.

OnCall Analytics includes models and reports
to support the anti-bias / profiling reports for
Dispatch. Includes 1 paginated reports and 2
PowerBI reports. Please note this only
includes data already captured by Dispatch.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

M
1063 Ability for system be updated as the State’s mandate on racial profiling evolves over time Y
Hexagon has committed to including the
functionality related to AB 953 as described in
this response. To the extent additional
functionality or capability is required that is not
otherwise already existing in Hexagon’s
software, Hexagon would welcome further
discussions about such functionality that may
included in a future Change Order or Order.

M
Law Compliance
CAD tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 50 Attachment 1

Number Global Functional Requirements Vendor
Compliance Comments IT Notes
1 2 The system proposed is Microsoft Windows based. Y Via Azure H 3 The system runs on a Microsoft Windows Server 2012 R2 or newer platform. Support for Microsoft Windows 7 and
Windows 10 for workstations.

Y
Yes for Windows Server for an on-premise
deployment. Hexagon has proposed a cloud-
based SaaS deployment in Microsoft Azure.

Please note Windows Server 2016 and
Windows 10 are the oldest supported versions
of Windows.

H
4 CAD and Records Management are one integrated
system, not two systems interfaced to each other. Y
RFP is for CAD solution with integration to
Sunnyvale RMS
Hexagon Response:

Via HxGN OnCall Dispatch| CAD Link COTS
interface. Please see Attachment 2 for more
detail.
5 System offers a browser based interface for public
information that is easily managed.

N
6 All proposed application software is from one vendor. N 7 Separately identify the software of other vendors if
present. N
Microsoft Azure and Commsys. Additionally
like many enterprise software solutions,
Hexagon software includes open source
software components, solutions which are not
separately listed.
8 The system architecture supports High Availability server clustering.

Y H
9 The system supports the ability to import data from field- data collectors such as handheld computers, smart
phones, etc.

Y H
10 The system has the ability to produce an electronic file for submission to the California DOJ E-CARS system.

The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This interface would only be
available in an RMS.

L
11 The system has the ability to send files, photos and videos directly to the District Attorney
The City currently views this as an RMS function.

However, we are looking for best overall value on the
proposed solution
N
Hexagon has proposed our OnCall Dispatch
CAD system. This interface would only be
available in an RMS.

L
12 System provides timely updates when CLETS and CJIS
changes Y
Please refer to the Master Terms and
Conditions for Software at this link:
https://www.hexagonsafetyinfrastructure.com/-
/media/Legal/Hexagon/SI/Sales/MT/USMT082
020.pdf
H
Global System Features
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 51 Attachment 1

13 Ability to migrate all existing CAD and RMS data.

Data conversion scope will be determined after phase 1
discovery discussions
Y
Hexagon clarifies this includes CAD static
data only as identified in section 6.6.8 of the
proposal response. RMS data conversion has
not been proposed.

H
14 The system database is supported on Microsoft SQL
Server 2012 or newer platform. Y
Not on Microsoft SQL Server 2012. OnCall
Dispatch works with newer Microsoft SQL
Server 2017 and Microsoft SQL Server 2019
(for an on-premise deployment. Hexagon has
proposed a cloud-based SaaS deployment in
Microsoft Azure.)
H
15 The system supports running in a VMware virtualized
environment.

Y Microsoft Azure H
16 Migration of all (two) existing New World database; one primary (2003 to present) database and a gap (July 2014 to November 2015) database.

Data conversion scope will be determined after phase 1
discovery discussions
Hexagon clarifies this includes CAD static
data only as identified in section 6.6.8 of the
proposal response. RMS data conversion has
not been proposed.
17 Vendor hosted RMS solution.
18 Capable of handling multi-jurisdiction ORI Y H
19 Vendor to provide all necessary third party licenses including those for servers, SQLs, mapping, etc. Y
Hexagon clarifies if purchased through
Hexagon. Please note Hexagon has proposed
a cloud-based SaaS solution, so servers,
SQL, etc. would not be required. Mapping is
provided by Azure maps.

H
20 Ability to provide the user with feedback as to the success or failure of a system task, including, but not limited to: H 21 Audible alert Y H
22 Visual alert Y H
23 Ability for system to automatically adjust number
sequencing for new calendar years.

Y H
24 Ability for system to automatically account for daylight savings time and any required parameter changes to
daylight savings.

Y H
25 Ability to date and time stamp all system transactions. Y H 26 Ability to have a single master time stamp for all
application components. Y
There is not a master time stamp included.

HxGN OnCall Dispatch syncs with the system
time, which can be synced with whatever time
source the customer desires.

H
27 Ability for all date and time stamps to be system
generated.

Y H
28 Ability for phone number to appear in 3/3/4 format (e.g., xxx-xxx-xxxx).

Y L
29 Global Code Table Administration
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 52 Attachment 1

30 Ability for the agency to define codes for drop down menus (e.g., BN for brown, BL for blue). Y H
31 Ability for the agency to maintain code tables, without contacting vendor. Y Yes, through HxGN OnCall Dispatch | Administrator H
32 Ability to make changes and additions to the code tables without modification to or recompilation of the application software.

Y H
33 Ability to share code tables among application
components. Y H
34 Ability for code table updates to propagate throughout the system (e.g. an update in a code table for one application component updates the same code table in other
application components).

Y H
35 Ability to designate code table values as obsolete and unavailable for current use, preventing further entry of that value, yet retain the value in the table for inquiries on historical data.

N L
36 Ability to create a new code and merge/link historical records to a new code.

N L
37 Ability to store the date a code table value becomes obsolete.

N L
38 Ability to store the date a code table value becomes effective.

N L
39 Ability to prevent display of obsolete code table values on drop down lists.

Y L
40 Ability to require users to enter values from a code table (e.g., prevent user from bypassing option).

Y H
41 A means shall be provided to update, add to, and
otherwise maintain most system databases, even those
that are not maintained in the normal course of everyday operation of the system.

Y Most tables can be maintained via HxGN
OnCall Dispatch | Administrator H
42 43
All system users are required to sign onto the system
before being given access to any system function
compliant to CJIS standards.

Y H
44 The sign on form includes fields for user ID and password.

FBI CJIS compatible passwords. Y H
45 The password is not displayed when entered. Y H
46 After the password is verified, the system automatically attaches the user to a security group that determines what system functions he or she may access.

Y Via Capability Lists H
47 Security granularity extends to individual control of access to view, modify, add and delete functions for each
application screen.

Y Through Capability and Access lists H
Global Security Considerations
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 53 Attachment 1

48 The passwords and security group assignments are
changeable by authorized personnel only at the highest
security level.

Y H
49 The security groups are configurable. Y H
50 The System Manager is able to create and modify security groups, defining system access down to the function level. Y H 51 The System allows the tracking and audit of user logins. Y H 52 The system allows the tracking of users that access, view, print, search, edit, delete, or modify a record or report. Y H 53 System will record a system history accessible and
searchable from any dispatch workstation, that contains system events by terminal ID including employee
Logon/Logoff, changes in dispatch group assignments,
system shutdowns and restarts, and free-text comments
entered by dispatchers on relevant system events.

Y Audit functions H
54 All system users and permissions are managed locally Y Local to the system; OnCall Dispatch is hosted in Azure
H
55 Ability to comply with CJIS software/ application security requirements.

Y H
56 Ability to encrypt data transmissions, per CLETS/NCIC requirements.

Y H
57 Ability to create multiple security groups. Y H
58 Ability to assign personnel to security groups. Y H
59 Ability to assign users to multiple security groups. Y H 60 Ability for agencies to define access permissions for each security group.

Y H
61 Ability to prevent users with expired CLETS/NCIC
certification from accessing CLETS/NCIC data.

Y H
62 Ability for agency defined personnel to allow users with expired CLETS/NCIC certification to access
CLETS/NCIC data.

N L
63 Ability for agency defined personnel to document reason for allowing users with expired CLETS/NCIC certification to access CLETS/NCIC data.

N L
64 Ability to view, add, maintain, modify and delete user profiles based on:
65 Agency Y H
66 Security group Y H
67 User ID Y H
68 User name Y H
69 Any combination of the above Y H
70 Ability to tie security to personnel module for automated security provisioning driven by work assignment.

Y H
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 54 Attachment 1

71 Ability to tie security to personnel module for automated security provisioning driven by certification status (e.g., CLETS/NCIC certification).

Y H
72 Ability to restrict user access or security group access to files and data fields for specified transactions:
73 Add/create Y H
74 Attach to email or send via other electronic method N L 75 Delete Y H
** is there tracking to what is deleted? HxGN final
comments: there is an audit trail in the admin portal
with documents what has been changed. This is for
administrator functions. There is limited delete
capabilities in OnCall as a user and most everything is documented.
76 Inquiry Y H
77 Modify Y H
78 Print N L
79 View Y H
80 Ability to separately secure add, modify, delete, and inquiry functions.

Y H
81 Ability to assign security access by physical device (e.g., PC, terminal, tablet).

N Can by User ID L
82 Ability to remotely log out a workstation (mobile or desktop).

Y H
83 Ability to lock out a user who is deemed a security risk while that user is on-line (e.g., logged into the system). Y H HxGN Final Comments: In admin portal we were able
to "check-in" the user's licenses and this will log the user out immediately. This coupled with Active
Directory (if you are using this feature) would log out as well
84 Ability to provide security at the following levels:
85 Application Y H
86 Database Y
Azure is utilized for managed solutions.

Access Control, Endpoint protection, Firewall,
Virtual Networks, Auditing (Log Analytics)
H
87 Field N H
HxGN Final Comments: these requests seem to
related to an RMS type system as fields and records
are associated to that type of system.
88 Record N H
HxGN Final Comments: these requests seem to
related to an RMS type system as fields and records
are associated to that type of system.
89 Screen/Transaction N H
HxGN Final Comments: these requests seem to
related to an RMS type system as fields and records
are associated to that type of system.

Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 55 Attachment 1

90 System Y
Azure is utilized for managed solutions.

Access Control, Endpoint protection, Firewall,
Virtual Networks, Auditing (Log Analytics)
H
91 Ability to create temporary security profiles. N L
92 Ability to tie security profiles to Active Directory user groups.

Y H
93 Ability for applications to work independently in the event Active Directory becomes unavailable.

Y H
94 Ability to support alternate authentication technologies (i.e., ID card, security token, biometrics, etc.).

Y Via OIDC H
95 Ability to flag a data element as confidential information for security purposes.

N M
96 Ability for users who are not authorized to access
confidential information to see that the information exists, but not view the actual information.

Y M
97 98
All system users are required to sign onto the system
before being given access to any system function
compliant to CJIS standards.

Y H
99 The sign on form includes fields for user ID and password.

FBI CJIS compatible passwords. Y H
100 The password is not displayed when entered. Y H
101
After the password is verified, the system automatically attaches the user to a security group that determines what system functions he or she may access.

Y Capability and Access lists H
102
Security granularity extends to individual control of access to view, modify, add and delete functions for each
application screen.

Y H
103
The passwords and security group assignments are
changeable by authorized personnel only at the highest
security level.

Y H
104 The security groups are configurable. Y H
105 The System Manager is able to create and modify security groups, defining system access down to the function level. Y H 106 The System allows the tracking and audit of user logins. Y H 107 The system allows the tracking of users that access, view, print, search, edit, delete, or modify a record or report. Y Audit Event, However, not delete. 108
System will record a system history accessible and
searchable from any dispatch workstation, that contains system events by terminal ID including employee
Logon/Logoff, changes in dispatch group assignments,
system shutdowns and restarts, and free-text comments
entered by dispatchers on relevant system events.

Y
By User ID, Event ID; Dispatch Audit provides
a user with detailed visibility to any new or
existing changes made while using OnCall
Dispatch. Users do not have the ability to
shutdown or restart the system (system
administrator function only)
H
Global Security Administration
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 56 Attachment 1

109 All system users and permissions are managed locally Y On Cloud Server H 110 Ability to comply with CJIS software/ application security requirements. Y H
111 Ability to encrypt data transmissions, per CLETS/NCIC requirements. Y H
112 Ability to create multiple security groups. Y H
113 Ability to assign personnel to security groups. Y H 114 Ability to assign users to multiple security groups. Y H 115 Ability for agencies to define access permissions for each security group. Y H
116 Ability to prevent users with expired CLETS/NCIC
certification from accessing CLETS/NCIC data. Y H
117
Ability for agency defined personnel to allow users with expired CLETS/NCIC certification to access
CLETS/NCIC data.

N L HxGN final Comments: we are not responsible for
CLETS certification
118
Ability for agency defined personnel to document reason for allowing users with expired CLETS/NCIC certification to access CLETS/NCIC data.

N L HxGN final Comments: we are not responsible for
CLETS certification
119
Ability to view, add, maintain, modify and delete user
profiles based on:
120 Agency Y H
121 Security group Y H
122 User ID Y H
123 User name Y H
124 Any combination of the above Y H
125 Ability to tie security to personnel module for automated security provisioning driven by work assignment.

N L
126
Ability to tie security to personnel module for automated security provisioning driven by certification status (e.g., CLETS/NCIC certification).

N L
127 Ability to restrict user access or security group access to files and data fields for specified transactions:
128 Add/create Y H
129 Attach to email or send via other electronic method N L 130 Delete Y H
131 Inquiry Y H
132 Modify Y H
133 Print Y H
134 View Y H
135 Ability to separately secure add, modify, delete, and inquiry functions. N
Ability to run commands may be restricted via
the Capability lists, but securing add, modify,
delete, and inquiry functions is not currently
done.
136 Ability to assign security access by physical device (e.g., PC, terminal, tablet).

N L why do we request this?
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 57 Attachment 1

137 Ability to remotely log out a workstation (mobile or desktop). Y H
138 Ability to lock out a user who is deemed a security risk while that user is on-line (e.g., logged into the system). N ?? 139 Ability to provide security at the following levels:
140 Application Y H
141 Database Y H
142 Field N M
HxGN Final Comments: these requests seem to
related to an RMS type system as fields and records
are associated to that type of system.
143 Record N M
HxGN Final Comments: these requests seem to
related to an RMS type system as fields and records
are associated to that type of system.
144 Screen/Transaction N M
HxGN Final Comments: these requests seem to
related to an RMS type system as fields and records
are associated to that type of system.
145 System Y
Azure is utilized for managed solutions.

Access Control, Endpoint protection, Firewall,
Virtual Networks, Auditing (Log Analytics)
H
146
Ability to create temporary security profiles. Y H
147 Ability to tie security profiles to Active Directory user groups.

Y H
148 Ability for applications to work independently in the event Active Directory becomes unavailable.

Y H
149 Ability to support alternate authentication technologies (i.e., ID card, security token, biometrics, etc.).

Y M
150 Ability to flag a data element as confidential information for security purposes.

N M
151
Ability for users who are not authorized to access
confidential information to see that the information exists, but not view the actual information.

Y
Only with CJIS/Informer data returns; non-
authorized users can see query made but not
return information
M
152
153
Ability to support a single user logon ID and password
across all proposed applications including, but not limited to:
154 Mobile and Field Reporting applications N Hexagon has not proposed RMS field reporting as part of this proposal. L **RMS
155 RMS and Field Reporting applications N Hexagon has not proposed RMS and RMS field reporting as part of this proposal. L
156 CAD and RMS applications Y
Yes OnCall Dispatch
Hexagon has not proposed RMS as part of
this proposal.
157 Ability for system administrator to change user IDs. Y H Global Logons and Logoffs
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 58 Attachment 1

158
Ability to be logged onto multiple workstations at the same time (e.g., logged into mobile computer in a vehicle and logged onto a station computer at the same time):

Y H
159 Different types of workstation (e.g., desktop and laptop) Y H 160 Same types of workstations (e.g., two desktops) Y H 161 Ability to track user logon/logoff times and locations for time reporting purposes.

Y H
162 Ability to support LDAP or Active Directory authentication. Y H 163 Ability to support two-factor logon. Y Via OIDC H
164 Ability to support third-party identification devices for logons.

Y Via OIDC H
165 Ability to automatically logoff a user after an agency defined predetermined period of inactivity, based on:
166 User type N A user can auto logoff based on time or activity
M
167 Location N A user can auto logoff based on time or activity
M
168 Ability to disable automatic logoff for secured
workstations.

Y However, not CJIS recommended L
169 Ability to save user's data prior to automatically logging off the user.

Y User workspace configuration is saved when
user logs off
H
170 Ability to save user's system preferences prior to user logoff.

Y H
171 Ability to display date and time of last session upon user logon.

Y H
172
Ability to provide system generated message to system
administrator or supervisor when an agency defined
number of unsuccessful sign-on attempts have occurred.

N M
173
Ability for the unsuccessful sign-on attempt message to include, at a minimum:
174 Date and time Y M
175 Number of attempts Y M
176 User ID Y M
177 Workstation ID N M
178 Ability to “lock out” a user and close applications after an agency defined number of attempted logons. Y H
179 Ability to disable "lock out" feature. N System will lock a users out after defined number of failed sign in attempts.

L
180
Ability to provide a secure lock-out with quick re-
authentication to restrict access to systems from an
unattended workstation.

N Outside of using OS provided security (Lock
Computer) L
181 Global User IDs and Passwords
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 59 Attachment 1

182 Ability for the agency to define password and user ID creation criteria. Y H
183 Ability to use Active Directory for password maintenance. Y Azure AD H 184
Ability for the agency to define which user-groups can
reset passwords on behalf of users (or create a security group that can reset passwords on behalf of users).

Y H
185 Ability to require the user to change their passwords at agency defined intervals. Y H
186 Ability for the agency to set a global maximum time for allowing a user to keep using a password. Y H
187 Ability to maintain a history of de-activated user IDs. Y H 188 Ability to disable password expiration feature. N L 189 Ability to require the user to enter a new password twice (e.g., to verify password). Y H
190 Ability to produce auto-notification of impending password expiration. Y H
191 Ability to enforce strong passwords per CJIS
requirements. Y H
192 Ability for user ID to be non-case-sensitive. Y H
193 Ability for individual system users to change their own passwords. Y H
194 Ability for system administrator to add and delete users. Y H 195 Ability for system administrator to disable an account. Y H 196 Ability to mask passwords when typed. Y H
197 Ability to encrypt passwords when stored and sent (i.e., no clear text passwords). Y H
198
199 Ability to create a security group defining who has audit trail access permissions. Y Auditor Role H
200 Ability to maintain an audit trail at the following levels:
201 Individual Y User ID H
202 Record Y Event ID H
203 Module Y Administrator Audit H
204 Application Y Administrator Audit H
205 Ability to view all audit trail records. Y Auditor Role H 206 Ability to log all actions including, but not limited to :
207 Changes Y H
208 Updates Y H
209 Errors Y H
210 Security violations Y Failed logon attempts H
211 Attempted breaches Y Failed logon attempts H
212 File maintenance transactions (e.g., create, read, add, update, delete transactions) Y H
Global Audit Trails
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 60 Attachment 1

213 Inquiries to all internal and external systems N
Hexagon requires more information to answer
this requirement. The Informer Tables support
NCIC/RMS type queries.

H
Hexagon requires more information to answer this
requirement. The Informer Tables support NCIC/RMS
type queries.
214 Transaction entries Y H
215 Print jobs N L
216 Override N L **OVERRIDE WHAT?
217 Successful sign-on Y H
218 Unsuccessful sign-on attempts Y H
219 Unauthorized attempts to access data N L
220 Ability for the agency to configure which transactions are recorded in the audit log. N L
221 Ability to store audit trail data including, but not limited to:
222 User ID Y H
223 User name Y H
224 Terminal ID N H HxGN final Comment: we are browser based not terminal
225 IP address Y H
226 Printer ID N L
227 Security level N M
228 Date and time stamp Y H
229 Transaction type Y H
230 Input, edit, deletion or inquiry Y H
231 Before and after values of modified data Y Values of modified data, not the before data. H 232 Type of data accessed during an inquiry Y H
233 Report number (if applicable) Y H
234 Ability to review all computer activity performed by a specified user during a period of time. Y H
235 Ability to log all vendor access to system (e.g., record a description of all vendor activity). Y All logins are recorded H 236 Ability to maintain historical data based on an agency defined length of time. Y H
237 Ability to maintain file history so that field value changes can be viewed both before and after change occurred. N H HxGN Final comment: this looks like it is related to a Records Management system
238 Ability to set audit log purge criteria. N H HxGN Final comment: we have audit tables 239 Ability to perform purge based on criteria. Y H
240 Ability to date, timestamp, view and audit all inquiries. N M 241 Ability of the system to assign a unique identifier to each record (i.e., log ID). Y M
242 Ability to comply with NCIC III logging requirements. Y Stored in the InformerResponse and InformerQuery tables H
243 Ability for all audit and logging functionality to be configurable. N M
244 Ability to view audit trails online. N L
245 Ability to pull up a record and see (e.g., via a function key): N
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 61 Attachment 1

246 Who made last change to record Y H
247 Time and date stamp of last change to record Y H
248 Modifications made to record (before and after values) Y Modified Values are recorded H 249 Ability to extract reports from the audit trail. Y H 250 Ability to secure audit log from user tampering. Y Must have auditor role H 251 Ability to archive audit trails based on transaction type and/or date. N
This type of maintenance or manual archive
operation is not relevant in a managed service
environment
L
252 Ability to manually archive information based upon user- specified parameters (time, file size, etc.). N
This type of maintenance or manual archive
operation is not relevant in a managed service
environment
L
253 Ability to automatically archive information based upon the following parameters:
254 Agency defined time period N L
255 Agency defined file size N L
256
326
361
362
The system shall provide database search capabilities
that will allow the user to freely specify search criteria and search any database or module in the system.

N
A dispatcher can run individual searches for
Who, Recall ANI/ALI, Event Search,
Equipment Search, Event Chronology, Unit
History, Supplemental Information Search
M- EVS
363 A list of matching entries shall be created that shall be able to be reviewed on screen or printed.

Y Based on the search dialog H
364
The system shall provide database search capabilities
that will allow the user to search by date ranges, beats, and officers
Y Based on the search dialog H
365
The search capability shall not rely on any knowledge of databases or database structures. Describe how this is
accomplished in a separate attachment to your proposal.

Y
As part of the project, Hexagon will provide
access to e-learning in addition to user guides
which educate users on baseline operations of
the System. General navigation in the
modules is covered as well as how to conduct
searches, such as Event Search, Unit History,
Event Chronology etc. Additionally, the OnCall
Analytics reporting tool allows an agency to
set up intuitive wizard driven reports to query
data based on agencies needs and specific to
user roles.

H
366
The system shall provide a method to search by date
range for assigned beat and vehicle by unit or employee ID.

Y H
Global Reports (moved to a separate tab)
Global Queries (moved to a separate tab)
Global Search Capabilities
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 62 Attachment 1

367
System shall provide the ability to search system history for events including user logon, logoff by terminal ID, changes in dispatch group assignments, system
shutdowns and restarts, and free text comments.

N H
OnCall does not provide any mechanism to search
changes in coverage (dispatch group). "System"
shutdowns or restarts are only in the application logs
files on the servers involved in the system and is n/a
for cloud deployments. There is no way to search the
user history table from within the product.
368
System shall provide a searchable file to store and
retrieve CLETS/NCIC messages sent and received with a
3-year retention period.

N
The system also does not provide a way to
search the CLETS returns, you'd need SQL
Server access to search those tables which is
not available in a SaaS environment.

HOW LONG ARE DOCUMENTS RETAINED? HxGN
Final Response: dependant upon how much or long
data you want in the system (On-Prem)
369
System shall provide a searchable file to store and
retrieve Terminal-to-Terminal messages sent and
received with a 3-year retention period.

N
This type of maintenance or manual archive
operation is not relevant in a managed service
environment.
370
System shall provide the ability to search system history for events including user logon, logoff by terminal ID, changes in dispatch group assignments, system
shutdowns and restarts, and free text comments.

R Via HxGN OnCall Dispatch | Operational
Reports H
371 Ability to search on multiple operational data fields. Y Event Search H
372 Ability to access multiple files and tables in a single search.

Y H
373 Ability to search narrative fields. Y H
374 Ability to exclude specified text when conducting narrative text searches.

N L
375 Ability to conduct searches based on:
376 Soundex Y M
377 "Wild cards" Y H
378 Exact match Y M
379 Partial information Y H
380 Boolean operators ("and," "or," and "not") N L
381 Date ranges Y H
382 Ability to narrow down searches (search within a search). Y M 383 Ability to select any result from a search and drill down for detailed information (e.g., hyperlink).

Y H
384 Ability to restrict searches that result in large volumes of data by:
385 Providing a warning of the size of records found N H HxGN final comment: we provide a data warehouse
to prevent issues with pulling large data from live
database
386 Requesting users to prompt the system to continue the search
N L
387 Requesting users to prompt the system to cancel the search
N L
388 Requesting users to modify the existing search criteria R Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 63 Attachment 1

389 Ability to limit the number of records viewed at one time. Y Via Query H 390 Ability to clearly indicate when additional information (e.g., more search results) is available. N L
391 Ability to save searches for later use. R Via OnCall Analytics | Dispatch Data Models and Reports H
392 Ability to export search results into standard formats, including:
393 Word R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
L
394 PDF R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
395 Access R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
396 Excel R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
397 Text files R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
L
398 Shapefiles N L
399 HTML N L
400 Ability to drill down into search returns. N M
401
402
The supplied system shall be customizable, without
additional programming, as much as possible to the
method of operation of the City. Examples of things that shall be customizable are unit status codes and incident dispositions, but should include all data items where the user picks from a list of acceptable values.

Y
Pick lists are customizable without additional
programming through HxGN OnCall
Administrator
H
403
Such customization shall be accomplished without
reprogramming. Describe to what extent and how this is
accomplished with the proposed system in Section 8 of
your proposal.

Y
HxGN was built with configuration in mind.

The command menus, dashboard cards,
dialog boxes, event icon, unit icons, event
board, unit board, context menus, map
polygons, polygon feature queries and many
other aspects of the system may be
configured without reprogramming via
configuration overrides.

H

DO WE NEED CRM TO OVERRIDE CERTAIN TEXT
BOXES …... HxGN Final Response: Is this CRE - if
so see email that provided example of what CRE can
be used for. Also note new configuration allows units
to preempt without a text box popping up so no CRE
needed for that functionality if that is what this is
related to.
404
The system shall support the ability to capture digital signatures for various forms. i.e. property release.

N L
405
406
Selected vendor will provide detailed user training plan including schedule, for each system function or module - CAD, MDC, RMS, ARS, Property and Evidence, etc.

Y
Yes for the proposed OnCall Dispatch
products. RMS and related modules are not
included as part of this proposal.

H
Global System Configuration
Global Training
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 64 Attachment 1

407
Selected vendor will provide detailed system
administration training plan including schedule for city IT and police support staff. Topics to include, but not limited to, all software installation processes, server software and hardware administration, backups, software patches and
upgrades, maintenance, and working with vendor
technical support.

Y
Hexagon has proposed system administrator
training as part of this proposal. However,
several of the processes mentioned as topics
would not be applicable as Hexagon has
proposed a cloud-hosted managed service
solution.

H
408
409
Selected vendor shall provide copies of all training
manuals or other written training materials in electronic format.

Y H
410
Selected vendor shall provide copies of all System
Administration manuals or other written reference
materials in electronic format.

Y System Administration documentation is
delivered electronically with the product. H
411
Selected vendor shall provide copies of all Database
codes, tables and fields on functionality document after system acceptance in electronic format.

N H
HxGN final comments: Database schema is provided
within the analytics application and help files. No final hard copy documentation is available
412
Selected vendor shall provide copies of an "as built"
System Functionality document after system acceptance
in electronic format.

N M
413
Selected vendor is expected provide copies of release
note of change documents if with any future system
software updates, feature changes, or upgrades.

Y Release Notes documentation is delivered
electronically with the product. H
414
The help system shall conform to all Windows standards
for on line help documents.

Y H
415 Ability to access an online help menu. Y H
416 Ability to provide help facility via function key or icon from any screen or field within any application.

Y H
417 Ability to use either a mouse or command line to access the online help menu.

Y H
418 Ability to provide context-sensitive help in the form of prompts and instructions.

N L
419 Ability to provide context-sensitive help only upon a user request.

Y H
420
Ability to provide help facility for an operation in progress via a function key from a screen or field within any
application.

Y H
421 Ability to provide training modules through help menu. Y A user can link to training documentation through help menu
M
422 Ability to search help files by keywords. Y H
423 Ability to edit text in help files to address agency specific topics.

N L
424 Ability to maintain online agency specific documentation and procedures, including:

Global Documentation
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 65 Attachment 1

425 Glossary of terms Y
Agencies may create their own documentation
and attach to events messages or use with
SOP functionality in OnCall Dispatch
Advantage
H
426 Glossary of error codes Y
Agencies may create their own documentation
and attach to events messages or use with
SOP functionality in OnCall Dispatch
Advantage
H
427
Ability to augment vendor-supplied online help tables with additional information (e.g., add notes to a topic that are viewable along with the vendor-supplied information).

N Not help file, but through SOP functionality
can display data. L
428
Ability for help file to automatically update at the time of all version/release updates.

Y H
429 Ability to prevent software updates from overriding agency- specific online documentation and help files.

N M
430 Ability for system administrator to create error messages. Y Via Localized Strings in OnCall Administrator M 431 Ability for system administrator to edit error messages. Y Via Localized Strings in OnCall Administrator M 432 Ability to track revisions to online documentation and help files, including:

N
433 User ID N L
434 Date and time N L
435 Ability to provide help files in a Windows help format. N Web based L 436 Ability to bookmark topics. Y Using customer browser H 437 Ability to search help file by:
438 Keywords Y H
439 Phrases Y H
440 Topics Y H
441 Similar topics Y M
442
443
444 Application must comply with AB 953 law. Y
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required to
do racial profiling analysis in accordance with
AB953 and custom reports can be generated
from HxGN OnCall Analytics.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

H
Global Law Compliance
AB 953
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 66 Attachment 1

445
Comply with mandates that Police agencies provide
reports on racial profiling (AB953). Does the system
contain tools or reports to assist with racial profiling analysis
Y
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required to
do racial profiling analysis in accordance with
AB953 and custom reports can be generated
from HxGN OnCall Analytics.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

H
446 System to contain tools or reports to assist with racial profiling analysis Y
The HxGN OnCall Dispatch suite has the
ability to capture the data elements required to
do racial profiling analysis in accordance with
AB953 and custom reports can be generated
from HxGN OnCall Analytics.

Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.

H
447
Example of reports: how many times did individuals of a given race interact with the police, relative to the number of calls for service pertaining to individuals of that same race
Y PCR 4833 Racial Profiling Mobile Responder
pending Approval
H
448 Ability for system be updated as the State’s mandate on racial profiling evolves over time Y
Hexagon has committed to including the
functionality related to AB 953 as described in
this response. To the extent additional
functionality or capability is required that is not
otherwise already existing in Hexagon’s
software, Hexagon would welcome further
discussions about such functionality that may
included in a future Change Order or Order.

H
Global tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 67 Attachment 1

Number CAD Functional Requirements Vendor
Compliance Comments DISPATCH

PRIORITY
DPS
Group NOTES
256
257 The system shall provide the following reports: ** FOR ALL REPORTS- IS ANALYTICS PART OF THE SYSTEM?
258 Uniform Crime Reports (UCR) DOJ eCARS N
Hexagon has proposed our OnCall Dispatch
CAD system. This interface would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
259 NIBRS N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
260 Single Incident Report R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
261 Shift Bulletin R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
262 24 Hour Incident Summary R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
263 Incident Summary by arbitrary date period R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
264 Incident Response Times by time of day and day of week and Incident Priority R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
265 Officer Activity Reports R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
266 Officer Activity Reports by user specified analytical criteria R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
267 Officer Activity Reports by squad R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
268 Monthly Arrest historical statistics N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.
269 Monthly Patrol Statistics R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
270 Unverified Locations R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
271 Crime Summary by Offense N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Global Reports
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 68 Attachment 1

272 Collision Reports – CHP 555 and related N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
273 Case Investigation Summary N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
274 Case Investigation Activity by Officer N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
275 Officer Log R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
276 Calls for Service information, type, location, etc. R Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
277 False Alarms R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
278 Citations by Violation, by Officer, Location, Date, reporting district, etc. N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
279 Vehicle Log by Officer R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
280 Vehicle Usage Log R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
281 Vehicle Mileage Summary R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
282 Communications Center Call Handling Times R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
283 Various call time statistics R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
284 Multiple disparate locations aggrade R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
285 Arrest/incident charge, types and potential values N Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
286 Arrest/incident profile by various information N
Hexagon has proposed our OnCall Dispatch
CAD system. This function would only be
available in an RMS.

Can be done in RMS. DPS pls confirm.
287 The system provides a press log feature N L
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 69 Attachment 1

288 The system has the ability to provide user specified statically data in graphic format R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
M
289 Reports must be viewable on screen before they are
printed. R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
M
290 Ability to provide a native reporting tool that can:
291 Create reports based on any operational data field in any system database R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
292 Create reports based on multiple operational data fields in any system database R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
293 Allow the end user to design report format R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
294 Access multiple files and tables R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
295 Print R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
296 Generate HTML reports R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
297 Ability for the report generating tool to handle:
298 Arithmetic operations, including fractiles and percentiles R Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
299 A full suite of statistical operations R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
300 Logic operations R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
301 Ability for the report generating tool to handle the manipulation of:
302 Data formats R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
303 Field sizes R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
304 Editing rules for a field R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 70 Attachment 1

305 Field headings R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
M
306 Data definitions R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
M
307 Formatting rules R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
308 Ability to maintain a general library of user-created reports. R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
309 Ability to preserve all user-created reports during updates and upgrades. R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
310 Ability for all authorized users to access the general library of user-created reports. R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
311 Ability for users to put their own reports in a "dashboard" for later use. R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
M
312 Ability to send reports to individuals or groups (via system or agency email). R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
313 Ability to generate reports on a pre-determined schedule. N Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H HxGN Final Comments: this is available on-premise
only
314 Ability to automatically send scheduled reports to
distribution groups. N
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H HxGN Final Comments: this is available on-premise
only
315
Ability to export reports results into standard formats, including:
316 Word R Via HxGN OnCall Dispatch | Operational
Reports
L
317 PDF R Via HxGN OnCall Dispatch | Operational
Reports
H
318 Access R Via HxGN OnCall Dispatch | Operational
Reports
H
319 Excel R Via HxGN OnCall Dispatch | Operational
Reports
H
320 Text files R Via HxGN OnCall Dispatch | Operational Reports
L
321 Shapefiles N
322 HTML R Via HxGN OnCall Dispatch | Operational
Reports
L
323 Ability to save reports for subsequent viewing and/or printing. R
Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 71 Attachment 1

324 Ability to delete reports after viewing and/or printing. R Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
M
325 Ability to view requested reports prior to printing. R Via OnCall Dispatch Operational Reports or
OnCall Analytics | Dispatch Data Models and
Reports
H
326
327 Ability to run a query on:
328 Report number Y Event Search H
329 Incident number Y Event Search H
330 Officer information, including:
331 Name Y Unit History H
332 Badge Number Y Unit History H
333 ID Y Unit History H
334 Unit number Y Unit History H
335 Name information, including:
336 Name Y Supplemental Search, Informer H
337 Identification number (driver's license, social security number, etc.). Y Supplemental Search, Informer H
338 Address information, including:
339 Exact address Y Supplemental Search, Informer H
340 Street Y Supplemental Search, Informer H
341 Intersection Y Supplemental Search, Informer H
342 Business name Y Supplemental Search, Informer H
343 Common name Y Supplemental Search, Informer H
344 Vehicle information, including:
345 Vehicle identification number Y Supplemental Search, Informer H 346 License plate number Y Supplemental Search, Informer H 347 Phone number Y Event Search H
348 Reporting District Y Event Search H
349 Boat Hull number Y Supplemental Search, Informer M
350 Serial number for weapons Y Supplemental Search, Informer H 351 Serial number for property Y Supplemental Search, Informer H 352 Personal File Number (PFN) Y Supplemental Search, Informer M **IS THIS ONLY THROUGH COMMENTS SINCE IT'S
NOT TIED INTO CJIC- OR CAN IT BE? …..HxGN
final Comments: We discussed Sunnyvale obtaining
the CJIC to the county. Hexagon does this for San
Jose and can do this for Sunnyvale but Sunnyvale
needs to communicate to the County to make sure all
is ok to work on this. This would be a scope
enhancement and needs to be requested if you want
this feature
353 Ability to search and query multiple databases with one query request.

Y H
354 Ability to for users to indicate which databases to query. Y H 355 Ability to set agency defined defaults for databases to query within each application.

N L
Global Queries
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 72 Attachment 1

356 Ability to consolidate query returns when multiple
databases are queried. Y Returns from each are returned to the same list, noting their source. H
357 Ability for query returns to indicate the information source (e.g., CLETS, RMS, CJIC). Y H
358 Ability to select any result from a query and drill down for detailed information (e.g., hyperlink). Y H
359 Ability to drill down on query results. Y Users can view the details of a response by clicking into a result, displaying it in the panel. H
360 Ability to save queries for later use. N H
779
780
781
Ability to provide a native reporting tool that can:
782 Create CAD reports based on any data field in the CAD database R
Via HxGN OnCall Dispatch | Operational
Reports. However, not "any field." Can report
on operational data within CAD.
783 Create CAD reports based on multiple operational data fields in the CAD database
R Via HxGN OnCall Dispatch | Operational
Reports
784 Ability to create, within the CAD application, standard reports consistent with NFPA 1221 benchmarks.

N All the required data is not captured in the
Dispatch source system
785 Ability to create, within the CAD application, standard reports consistent with NFPA 1710 benchmarks.

N All the required data is not captured in the
Dispatch source system
786 Ability to generate the following standard reports from within the CAD application:
** NEED TO KNOW IF WE WILL STILL HAVE

ACCESS TO A SQL SERVER THAT CAPTURES ALL

CAD DATA THAT WE CURRENTLY CAPTURE ON

SSRS AND HAVE THE ABILITY TO CREATE OUR
OWN REPORTS. JW
787 Incident analysis by day of week R Via OnCall Analytics | Dispatch Data Models and Reports
788 Incident analysis by geographic area R Via OnCall Analytics | Dispatch Data Models and Reports
789 Incident analysis by hour of day R Via OnCall Analytics | Dispatch Data Models and Reports
790 Incident analysis by shift R Via OnCall Analytics | Dispatch Data Models and Reports
791 Incident analysis by beat R Via OnCall Analytics | Dispatch Data Models and Reports
792 incident analysis by reporting district R Via OnCall Analytics | Dispatch Data Models and Reports
793 Incident analysis by call type R Via OnCall Analytics | Dispatch Data Models and Reports
794 Incident analysis by disposition R Via OnCall Analytics | Dispatch Data Models and Reports
795 Incident analysis by priority code R Via OnCall Analytics | Dispatch Data Models and Reports
796 Incident analysis by geographic area by hour of day R Via OnCall Analytics | Dispatch Data Models and Reports
797 Incident analysis by responding agency R Via OnCall Analytics | Dispatch Data Models and Reports
CAD Reporting and Query
CAD Reporting and Analysis
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 73 Attachment 1

798 Incident analysis by unit R Via OnCall Analytics | Dispatch Data Models and Reports
799 False alarm reports R Via HxGN OnCall Dispatch | Operational Reports
800 Fractile reports R Via OnCall Analytics | Dispatch Data Models and Reports
801 Fractile reports by unit R Via OnCall Analytics | Dispatch Data Models and Reports
802 Processing time by method of call receipt R Via OnCall Analytics | Dispatch Data Models and Reports
803 Response times by geographic area R Via OnCall Analytics | Dispatch Data Models and Reports
804 Response times by type of call/priority R Via OnCall Analytics | Dispatch Data Models and Reports
805 Response times by original call destination R Via OnCall Analytics | Dispatch Data Models and Reports
806 Response times by assigned unit R Via OnCall Analytics | Dispatch Data Models and Reports
807 Total and average time on call – by day of week R Via OnCall Analytics | Dispatch Data Models and Reports
808 Total and average time on call – by geographic area R Via OnCall Analytics | Dispatch Data Models and Reports
809 Total and average time on call – by hour of day R Via OnCall Analytics | Dispatch Data Models and Reports
810 Total calls for service by: R Via OnCall Analytics | Dispatch Data Models and Reports
811 Date or date range R Via OnCall Analytics | Dispatch Data Models and Reports
812 Disposition R Via OnCall Analytics | Dispatch Data Models and Reports
813 Time of day R Via OnCall Analytics | Dispatch Data Models and Reports
814 Total incidents by date by nature or disposition R Via OnCall Analytics | Dispatch Data Models and Reports
815 Ability to provide an analytical tool that reviews workload by, but not limited to:
816 Workstation N
Via OnCall Analytics | Dispatch Data Models
and Reports. However, not by workstation but
by User ID.
817 Call taker/dispatcher R Via OnCall Analytics | Dispatch Data Models and Reports
818 Ability to report on unavailability of field personnel resources. N Data not captured in source system
819 Ability to report on unavailability of equipment resources. N Data not captured in source system 820 Ability to account for unavailable resources in response time calculations. N Data not captured in source system Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 74 Attachment 1

821 Ability to capture a snap shot, based on day and time parameters, of:
822 A workstation N Not by workstation ID, but by user ID. 823 General CAD system N
Hexagon requires more specifics on the
intent of the report before providing a
response to this requirement.
824
Ability to generate, from within the CAD application, a daily listing of incidents and personnel assigned to the incidents including, but not limited to:
825 Actual dispatch location R
Via OnCall Analytics | Dispatch Data Models
and Reports
Hexagon clarifies this functionality will only be
available as part of Phase 2 of the Project.
826 Call taker/dispatcher ID R Via OnCall Analytics | Dispatch Data Models and Reports
827 Date/time received R Via OnCall Analytics | Dispatch Data Models and Reports
828 Disposition R Via OnCall Analytics | Dispatch Data Models and Reports
829 Field personnel name R Via OnCall Analytics | Dispatch Data Models and Reports
830 Field personnel ID R Via OnCall Analytics | Dispatch Data Models and Reports
831 Incident location R Via OnCall Analytics | Dispatch Data Models and Reports
832 Incident number R Via OnCall Analytics | Dispatch Data Models and Reports
833 Ability to print audit report of changes to incident records including:

R Via OnCall Analytics | Dispatch Data Models
and Reports
834 Transaction type (deletion, edit, etc.) R Via OnCall Analytics | Dispatch Data Models and Reports
835 Unit ID R Via OnCall Analytics | Dispatch Data Models and Reports
836 Workstation/terminal ID R Via OnCall Analytics | Dispatch Data Models and Reports
837 Before and after value R Via OnCall Analytics | Dispatch Data Models and Reports
838 Ability to generate a list of incidents to be shared with the public based on agency-specific business rules.

R Via OnCall Analytics | Dispatch Data Models
and Reports
839
Ability to generate a report containing a summary of
incidents for an agency-defined period of time for
distribution to the public.

R Via OnCall Analytics | Dispatch Data Models
and Reports
840
841
Upon entry of a vehicle license plate, the CAD system
shall immediately search its database (including CLETS
SVS and DMV) and retrieve make, model, year, and
color information directly into the form.

Y H
CAD Queries
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 75 Attachment 1

842
Upon entry of a vehicle license plate, the CAD system
shall look up the person associated with the vehicle and display pertinent information about the person including but not limited to recent contact history, officer safety notations, and arrest, warrants, and suspect information.

Y M
**HOW LONG IS THE INFO RETAINED? HxGN final
Comment: this will be discussed during
implementation and getting your requirement
843
Ability to automatically query the license plate against the RMS, DMV and CLETS databases when a unit is on a
vehicle stop.

Y C
844 Ability to automatically run a registered vehicle owner upon return of a license plate query. Y C
**ANY INTERNAL WAY TO RUN A DOUBLE LAST
NAME? SOME OTHER CADS HAVE THAT OPTION
WITH A (*) IN BETWEEN …HxGN final comment -
yes
845 Ability to attach query returns to incident records. Y C 846 Ability to query the following databases from within CAD:
847 RMS Y C
**IS THIS BASED ON PROPOSED INTERFACE-
CAD TO RMS….HxGN final comments: We have
included name and vehicle query capabilities from
Tiburon to CAD via Informer in our proposal
848 CLETS/NCIC Y C
**IS THIS BASED ON PROPOSED INTERFACE-
CAD TO RMS….HxGN final comments: We have
included name and vehicle query capabilities from
Tiburon to CAD via Informer in our proposal
849 CJIC Y C
HxGN final Response: this would be an additional
scope - and we need to add the requirement into the
SOW
850 DMV Y C
**IS THIS BASED ON PROPOSED INTERFACE-
CAD TO RMS….HxGN final comments: We have
included name and vehicle query capabilities from
Tiburon to CAD via Informer in our proposal
851 All four databases simultaneously Y C
852 Ability for subject query returns to include associated photos, if available in the following databases:
853 RMS Y M
**QUERY INTO THE SYSTEM OR A PHOTO
ATTACHMENT INTO CAD? HxGN final Response:

Yes if photo's are attainable
854 County Mugshots M
Hexagon has proposed an Informer query
interface to County Mugshot system. The
query is by Name/DOB, OLN or SSN. Please
see Attachment 2 for more detail.

M HxGN final response: discussion with the group
advised this was not available
855 DMV T
Via third party CommSys ConnectCIC
middleware in combination with HxGN OnCall
Dispatch | Informer
M
856 CALPhoto N
Hexagon did not propose interface to
CALPhoto and would require more
information on how this would be used in
conjunction with a CAD system.

M HxGN final response: discussion with the group
advised this was not available
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 76 Attachment 1

857 Ability to query call for service records based on:
858 Date range Y Event Search functionality C
859 Time range Y Event Search functionality C
860 Incident number Y Event Search functionality C
861 Unit ID Y Event Search functionality C
862 Officer name/ID Y Event Search functionality C
863 Location Y Event Search functionality C
864 Any location in an incident Y Event Search functionality C 865 Any combination of the above Y Event Search functionality C 866
Ability to populate the query mask with data in the
incident record without cutting and pasting (e.g., with a function key or one or two key strokes):
867 Person Information N L
868 Vehicle Information N L
869 Ability to automatically query the following databases upon entry of a name:
870 RMS (Master Indices) T
Via Supplemental Information using third
party CommSys ConnectCIC middleware in
combination with HxGN OnCall Dispatch |
Informer
H **CAN ADMIN SET IF ITS AUTOMATIC OR NOT?
HxGN final response: Yes
871 CLETS/NCIC T
Via Supplemental Information using third
party CommSys ConnectCIC middleware in
combination with HxGN OnCall Dispatch |
Informer
H
872 DMV T
Via Supplemental Information using third
party CommSys ConnectCIC middleware in
combination with HxGN OnCall Dispatch |
Informer
H
873 CJIC T
Via Supplemental Information using third
party CommSys ConnectCIC middleware in
combination with HxGN OnCall Dispatch |
Informer
H
874 Ability to query and view the following by any public safety boundary layer (beat, sector etc.):
875 Active calls Y Event Search functionality L
876 Assigned calls Y Event Search functionality L
877 Priority calls Y Event Search functionality L
878 Waiting (pending) calls Y Event Search functionality L 879 Ability to query unit history by any combination of:
880 Date and time range (e.g., start and end date and time parameters)
Y Unit History functionality H
881 Unit ID, field personnel ID, or employee number Y Unit History functionality H 882 Ability to query resource availability by:
883 Dispatch group Y M
884 Geographic area (e.g., fire zone box, beat, sector) Y M 885 Special skills Y M
886 Unit types (e.g., apparatus, patrol units, Hazmat) Y M Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 77 Attachment 1

887 Ability to query unit status by:
888 Date and time range Y H
889 Dispatch group Y L
890 Personnel ID Y H
891 Geographic area (e.g., fire zone box, beat, sector) Y L 892 Incident type Y M
893 Unit ID Y H
894 Unit types (e.g., apparatus, patrol units) Y M
895 Ability to sort query results by any criteria (e.g., most recent to oldest, by priority). Y Sortable by columns of the inquiry results M 896 Ability to limit query returns to an agency-defined number. N L
897 Ability to hyperlink query returns to incident records. Y C 898 Ability to print query returns. Y C
899 Ability to redact query returns prior to printing. N M **DIFFERENCE BETWEEN LINKING AND
REDACTING? HxGN final response: We need more
clarification on this question - redaction tends to be an RMS type function
Reporting tab
Attachment 1 - Functional Specifications from Phase 1 Fit & Gap Analysis 78 Attachment 1