Browse
Search
2025-318-E-Emergency Svc-Hexagon Safety, Infrastructure, & Geospatial-CAD Replacement
OrangeCountyNC
>
Board of County Commissioners
>
Contracts and Agreements
>
General Contracts and Agreements
>
2020's
>
2025
>
2025-318-E-Emergency Svc-Hexagon Safety, Infrastructure, & Geospatial-CAD Replacement
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/12/2025 3:44:12 PM
Creation date
6/12/2025 3:42:58 PM
Metadata
Fields
Template:
Contract
Date
6/4/2025
Contract Starting Date
6/4/2025
Contract Ending Date
6/11/2025
Contract Document Type
Contract
Amount
$2,729,399.34
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
249
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 106 <br /> M7100, P7100, XG-100M, XG-75, XG-100P <br />Certain GPS devices also accept commands from external systems to control the frequency of location <br />reports. HxGN OnCall Dispatch | Tracker can be configured to send the appropriate commands to these <br />devices, setting the frequency of location reports based upon unit type, unit status, and the type of event <br />the unit is currently assigned to. <br />When OnCall Dispatch | Tracker is used with our mobile solution on MDCs, Mobile Unit uses the in- <br />vehicle map and high-speed access to the GPS receiver to match the vehicles route to the map to <br />determine the address of the vehicle. This approach is necessary because mapping information is seldom <br />as accurate as the GPS device. The map is often several hundred feet off from the true location. This <br />approach is more accurate than the more common method of using a server to attempt to place a point <br />on the map based on a single position report. The computed location is used to pre-populate forms <br />requiring a location such as on-view incidents and unit emergency. The officer can override the location if <br />required as a final check before submitting the command. <br />The selected GPS receivers may support commands to change their delta time and/or delta distance <br />reporting rates dynamically. AVL information may be used in the CAD system in the Recommend Unit <br />processing. <br />Depending on the existing AVL solution, the OnCall Dispatch | Tracker interface supports three different <br />modes of operation: passive, poll, and poll list: <br /> Passive mode interfaces to a radio system, data terminal system, or location server and directly <br />receives location reports from radio, MDT, or GPS devices. In the passive mode, OnCall Dispatch <br />| Tracker exerts no control over the behavior of the location reporting devices and only receives <br />these location reports, processes their contents, and forwards them to OnCall Dispatch when <br />needed. <br />This mode is useful when the devices are not capable of responding/honoring the poll rate <br />commands that are issued to them from OnCall Dispatch | Tracker. This mode is also used when <br />the GPS devices in service are capable of regulating their own polling. <br /> In poll list mode, OnCall Dispatch | Tracker may interface with a location server or controller; that <br />is, a software/hardware solution that performs the actual polling of vehicles and devices. The <br />location server/controller may also perform other functions, such as differential correction. This <br />could be some software application running on a different server (Windows, Linux, and so forth) <br />or some other type of hardware controller (a “black box”) that communicates with the devices <br />OnCall Dispatch | Tracker needs to set the poll rates for. In this mode, OnCall Dispatch | Tracker <br />does not communicate directly with these devices but instead goes through an intermediate <br />“solution” that communicates with the devices. Essentially, this is an indirect mode of <br />communication where OnCall Dispatch | Tracker must go through third-party “solution” to <br />communicate with the devices. <br />OnCall Dispatch | Tracker builds a list of devices internally that it packages up and sends to the <br />location server or controller (“solution”) when it sets poll rates in the “poll list” mode. All devices <br />are then divided among poll groups which are configured in the AVL Poll Group dialog. OnCall <br />Dispatch | Tracker assigns each unit to one of these poll groups based on specified parameters <br />of the unit. As in the poll mode, these may include a unit’s type (agency/dispatch group), unit <br />status, event type and/or last reported velocity. <br />Each poll group has an associated polling interval. For example, a poll group may be defined to <br />be all vehicles whose status is ‘ON SCENE’ and whose last reported velocity is less than 10 miles <br />per hour; the polling interval for this group could be set to 600 seconds (10 minutes). When <br />OnCall Dispatch | Tracker determines that the last location report for a vehicle in this polling <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9EDocusign Envelope ID: 295A5D15-51E9-4D4A-ABF7-42411BB309FA
The URL can be used to link to this page
Your browser does not support the video tag.