Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 112 <br />Assumptions: <br /> Additional third-party licensing may be necessary; the Customer should consult with their radio <br />provider for additional information. <br /> The XML format required by the external systems must be provided to Hexagon. <br />Constraints: <br /> The Customer is responsible for providing complete and accurate description of the API needed to <br />interface, and for any software/hardware/data required to implement communications with the <br />external systems. <br />External Alarms OnCall Dispatch Interface <br />The APCO ASAP Standard is supported with this interface. It allows OnCall to interface with the APCO <br />International Automated Secure Alarm Protocol (ASAP) Alarm System (also called “ASAP to PSAP”). <br />The Automated Secure Alarm Protocol (ASAP) program is a computer-aided dispatch system designed <br />by the Central Station Alarm Association (CSAA) and the Association of Public Safety Communications <br />Officials (APCO Int'l). <br />Because ASAP Alarm system operates on the National Law Enforcement Teletype System (NLETS) <br />backbone – state specific development services may be required for each implementation to convert the <br />APCO standard NLETS message into the State CJIS Message Switch format. <br />This interface requires CommSys ConnectCIC with ASAP Option and consulting services from The <br />Monitoring Association (TMA) through CommSys. TMA requires a test connection license of ConnectCIC <br />to support post production testing and modifications from TMA's alarm (i.e. changes to alarm payload, <br />addition or removal of participating Alarm vendors or central monitoring stations) <br />Assumptions: <br /> Hexagon has also proposed consulting services for the Customer to coordinate deployment with <br />the Monitoring Association directly. <br /> <br />Custom Interfaces <br />Text to 911 <br />Hexagon will develop a custom interface to meet this requirement. <br />Assumptions: <br /> This interface requires OnCall Dispatch | Call-Taker Interface and Vesta i3 Event Viewer log <br />interface API/SDK. <br /> The Customer is responsible for obtaining licensing from Vesta/Motorola for API/SDK. The <br />Customer responsible for any costs associated licensing from Motorola/Vesta. <br /> Interface is limited to the capabilities identified in the Vesta i3 Event Viewer log interface API/SDK <br />for supporting ANI/ALI spill, plus SMS/MMS to 911. <br /> Video calls to 911 are not supported at this time. <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E