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 105 <br /> Vendor-defined XML output to FIREHOUSE Software by ESO <br /> For the FIREHOUSE FireRMS interface, Fire Link will transfer event and resource data to <br />FIREHOUSE’s Custom Hexagon CAD Monitor, which in turn will populate the FIREHOUSE <br />RMS Database. This is an ASCII File Transfer. <br /> Standard XML output for all other FRMS vendors <br />Assumptions: <br /> The transmission protocol between Fire Link and the remote FireRMS is TCP/IP. <br /> Fire Link interfaces to a single database. <br /> Fire Link requires Xalt Integration as a prerequisite. <br />Constraints: <br /> The Customer is responsible for providing complete and accurate documentation on the systems <br />to be interfaced. <br /> The Customer is responsible for acquiring and installing a data import capability into their current <br />Fire RMS(s). <br /> For the interface to FIREHOUSE RMS, the Customer is responsible for providing the <br />FIREHOUSE RMS communications and associated equipment. The Customer is also responsible <br />for acquiring and installing the Custom Hexagon CAD Monitor data import capability into their <br />current Fire RMS. <br /> Hexagon cannot be held accountable for incompatibilities in its interface which are due to changes <br />in input/output formats or data requirements of the vendor’s product. <br />HxGN OnCall Dispatch | Tracker <br /> For radios <br />HxGN OnCall Dispatch | Tracker accepts incoming Global Positioning Satellite (GPS) data directly from a <br />GPS device, location servers or mobile data devices. HxGN OnCall Dispatch | Tracker functions as an <br />extension to the dispatch environment, periodically updating vehicle and personnel locations in OnCall <br />maps and monitors. <br />Supported GPS Devices: <br /> Devices running Mobile Unit or Mobile Responder <br /> Radios transmitting GPS data in the following message formats <br /> Trimble TAIP messages, UDP connection <br /> NMEA messages, UDP connection <br /> OpenSky messages, UDP connection <br /> Harris GPS Radio Types M-803, M5300, M7200, M7300, P5400, P5500, P7200 transmit <br />OpenSky GLR1/GLP1 messages over UDP <br /> OMA/MLP (web service) <br /> Non-Supported GPS Devices <br /> Smartphones not running Mobile Responder or Mobile Unit <br /> Harris radios that do not support OpenSky messages <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.