Have Questions?
We have answers
Below you’ll find answers to the most common questions you may have about ASAP Service. Also, check out our LinkedIn page. If you still can’t find the answer, just contact us!
How does ASAP Service work?
ASAP is a bi-directional interface similar to a CAD-to-CAD interface. The difference is that one side of the interface is an alarm monitoring broker, rather than another CAD system. Data sent through the interface is standardized to ensure automatic incident creation and messaging between the operators of both systems. You can view a demo of it here.
How long does it take to implement ASAP Service?
CAD-integrated ASAP can be implemented in as little as three to four months. ASAP View, the secure, web-based solution, can be implemented as an interim solution in as little as two to four weeks.
As an ECC leader, do I need to coordinate alarm company participation?
No. With ASAP, you’re supported by a concierge team of implementation specialists who coordinate closely with alarm monitoring companies and ECCs, managing every detail to make integration effortless.
Does ASAP Service require a state message switch or an Nlets connection?
ASAP does not require an Nlets connection. CAD-integrated ASAP can be connected via Nlets or a direct API. It is also available as a secure, web-based solution. View the ASAP offerings here.
If my ECC is in a state without a current Nlets connection, can it still participate in ASAP?
Yes! You can connect to ASAP Service with a direct API or by implementing a secure, web-based version of ASAP.
My ECC’s CAD vendor does not have an active ASAP connection. Can I still participate in ASAP?
Yes! Implementation may take a bit longer for your CAD vendor to develop their part of the ASAP interface.
What happens if ASAP cannot deliver an alarm to the ECC?
If an alarm cannot be delivered to the ECC, the monitoring center will get a message that it could not be delivered and will then call the ECC.
Is the interface still called ASAP to PSAP?
The platform is now referred to as ASAP Service, although it was called ASAP to PSAP since 2011.