Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 109 <br /> Stations <br />Functionality includes three (3) basic functions: <br />1 Automatic Dispatch Pages ─ Automatic sending of dispatch messages or tone alerts to <br />appropriate pagers associated with units during a normal dispatch. Dispatch messages sent by <br />OnCall Dispatch workstations will be analyzed and processed for paging units equipped with <br />pagers. This is an automatic feature. Once a dispatch packet is received, the paging server will <br />use the unit ID in the packet to look up the pager ID from the OnCall Dispatch Database. <br />Therefore, only logged-on units can be sent dispatch pages automatically. This pager ID will be <br />used to match records in other page-related tables to locate the actual device specific code to be <br />sent to the proper paging controller. Additionally, dispatch related conditions can be placed <br />against these pages for conditional paging. <br /> Entering Messages through Send Message ─ Manually sending user-entered text or pre- <br />formatted text messages to alphanumeric pagers. Through the Send Message dialog box in <br />OnCall Dispatch, users may manually enter or use pre-entered, pre-formatted messages to be <br />sent to alphanumeric pagers. A pick list of pre-formatted messages can be configured. As these <br />messages are manually entered and not the result of a dispatch operation, these type pages do <br />not have conditional capabilities. For example, all pager IDs entered or resolved from a unit ID will <br />be paged. <br /> Manually Sending Dispatch or Event Info ─ Manually sending dispatch or event information to <br />alphanumeric pagers. The paging interface can also re-send dispatch type pages to alphanumeric <br />pagers via the Send Message dialog box in OnCall Dispatch. By selecting or entering an event <br />number, the software will build a dispatch page just as it does for the actual dispatch. This text <br />message can then be modified or amended prior to sending the message. Because this is a <br />manual page and not the result of a dispatch, no conditions capabilities can be evaluated for the <br />individual page IDs. <br />Assumptions: <br /> Hexagon assumes that the paging system uses one of the supported protocols. Each license of <br />OnCall Dispatch | Notifications allows any number of potential pagers. The connection of the <br />Paging Controller is assumed to be RS-232 or Network based (TCP/IP). Connection may be <br />made through a dedicated or dial up line. <br /> Hexagon assumes use of a single paging controller type. If additional controller types are used, <br />Hexagon’s bid must be re-evaluated. <br /> OnCall Dispatch | Notifications currently does not support voice paging; it only supports <br />alphanumeric text. <br /> Hexagon assumes the Customer is responsible for providing any phone lines, modems, internet <br />connections, etc. required to establish the connection with the paging terminal(s). <br />Constraints: <br /> Each distinct paging controller type requires a separate license of OnCall Dispatch | Notifications. <br />However, the Customer may implement multiple paging providers using the same protocol, and <br />these would be considered a single paging controller for licensing purposes. <br /> SMTP provides the ability to send email messages and is the link between the Microsoft® <br />Windows® Exchange server and the OnCall Dispatch | Notifications system. <br /> OnCall Dispatch | Notifications does not support bidirectional communications. <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9EDocusign Envelope ID: 295A5D15-51E9-4D4A-ABF7-42411BB309FA