Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 107 <br />group is more than 10 minutes old, it will generate a new poll request to the controller. The poll <br />group with the largest polling interval defines the maximum polling cycle for the fleet. <br />The poll list mode is used to minimize the contention for radio frequency bandwidth. The location <br />server/controller sends out the location queries to each device in the polling list along with a time- <br />slot during which it expects to receive the corresponding location report. In this manner, the <br />controller seeks to guarantee that no two vehicles will attempt to transmit a location report <br />simultaneously. <br /> Poll mode requires the devices to be programmable by an external source. This programmability <br />allows the reporting behavior of the device to be by varying parameters, such as delta distance <br />and/or delta time that are transmitted directly to each device. In poll mode, all devices are divided <br />among a certain number of poll groups. OnCall Dispatch | Tracker assigns each unit or device to <br />one of these poll groups based on certain parameters of the unit. <br />OnCall Dispatch | Tracker actively changes these parameters by assigning new values based on <br />a unit’s type (agency/dispatch group), status (Available, On-Scene, and so forth) and an event <br />type. For systems that include velocity in the location report, the last reported velocity may also <br />be used to determine the location reporting behavior. <br />Assumptions: <br /> Licensing is by device <br /> OnCall Dispatch | Tracker is a zero-cost product when bidding Hexagon mobile clients (Mobile <br />Unit and Mobile Responder) <br /> Pricing is only required when connecting to non-Hexagon devices such as radios and third <br />party mobile clients <br /> OnCall Dispatch | Tracker must be installed and licensed to track any device even if there is no <br />cost to the Customer <br /> The OnCall Dispatch | Tracker interface establishes communications between a third-party AVL <br />controller/message switch and the OnCall Dispatch System. <br /> Hexagon assumes that communication with the AVL controller/message switch will be achieved <br />via TCP/IP or serial line (RS-232) communication protocol. <br /> The OnCall Dispatch | Tracker interface supports NMEA, OpenSky, BlueTree, Sierra Wireless <br />RNAP, and TAIP protocols and devices that support these protocols should be compatible with <br />OnCall Dispatch | Tracker. If the Customer is currently running AVL hardware that OnCall <br />Dispatch | Tracker does not support, additional services must be purchased to develop a custom <br />AVL interface. <br /> Hexagon recommends that the Customer purchase a device such as the Sierra Wireless, Trimble <br />TrimFleet, or Airlink modems that supports one of the above protocols. <br /> Hexagon assumes that the Customer uses one of the supported GPS Receiver/Systems. If the <br />Customer requires Hexagon to interface to a GPS Receiver/System that is not supported, <br />additional development services will need to be quoted. <br />Constraints: <br /> The Customer is responsible for providing Hexagon with a complete and accurate description of <br />the interface to the AVL controller/message switch. <br /> If the Customer has AVL hardware that OnCall Dispatch | Tracker currently does not support, <br />Hexagon reserves the right to bid additional services to develop a custom AVL interface. <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E