Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 104 <br />exported output files. The profiles act as event filters, determining which OnCall events are to be exported <br />to which file system directories (inboxes). <br />Assumptions: <br /> Hexagon assumes this is for the transfer of CAD event and unit data only to the specified <br />systems. <br /> Additional services are required from the third-party vendor to consume and distribute the incident <br />information provided via CAD Link. <br /> The Customer will be responsible for any data mapping <br /> The Customer will provide a technical resource as well as any necessary subject matter experts <br /> The Customer will provide a test system for installation and testing <br /> Hexagon will configure CAD Link to output to a single location where the Customer is responsible <br />for consuming the data <br /> The Customer is responsible for ensuring that any third-party vendor technical resources are <br />available to support the testing of this interface. <br /> Hexagon assumes that the third-party vendor will be utilizing XML protocols for this interface. <br /> This is a one-way interface. CAD Link exports OnCall Dispatch incident-related data, but it does <br />not import data. Any import is the responsibility of Customer or of the third-party vendor. <br />Constraints: <br /> OnCall Dispatch events must be closed before they are candidates for export by CAD Link. <br /> CAD Link does not provide features for obtaining "next available case numbers," "location <br />verification," or any other OnCall Dispatch-related functionality or interface; it only provides export <br />of specified event data for closed OnCall Dispatch events. <br />HxGN OnCall Dispatch | Fire Link <br /> ESO <br /> FirstDue <br /> Firehouse <br /> Pagetrack <br />Hexagon’s Fire Link product interfaces to various Fire RMS applications facilitating the automatic transfer <br />of event and unit data from OnCall Dispatch generated during a Call for Service. The designated third- <br />party RMS vendor (or the Customer) is then responsible for importing the information into the relevant <br />fields/tables of the target database. <br />Fire Link automates data transfers to the external system at periodic intervals as follows: <br /> Event information is generated when the first unit’s status changes to that specified by the user. <br />Valid status changes include Dispatch, Enroute, OnScene, Transport, Transport Arrive and Clear. <br /> Unit information is generated for each unit whose status changes to that specified by the user. <br />More than one status can be specified for sending unit information. <br /> Event information that includes event closing data, is generated when the event is closed. <br />The Fire Link Interface is available in two options (if using more than one option, then a separate Fire Link <br />Interface is required for each option): <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E