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 instead of another CAD system. Data sent through the interface is standardized to ensure automatic incident creation and messaging between the operators of both systems.
Does ASAP Service require a state message switch or an Nlets connection?
Currently, ASAP requires an Nlets connection. Some states also require the connection to go through the state message switch; this requirement will be updated in the second half of 2025.
If my ECC is in a state without a current connection, can it still participate in ASAP?
Yes! Implementation may take a bit longer to develop a connection to the state switch.
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.
Since ASAP has existed since 2011, why are so few ECCs live with ASAP?
In the early years of ASAP, development to the state message switches were complicated, and standards were limited. Progress with the standards and technology have improved, and will continue to improve the implementation time, allowing for more ECCs to be onboarded each year.
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.
What is The Monitoring Association (TMA) doing to accelerate the ASAP implementation process?
TMA has partnered with Mission Critical Partners to support implementation – they have experience and employ modern technology to automate many steps of the ASAP onboarding process.