Integration with on-site systems
Integrate with on-site systems through APIs or by installing on-site hardware devices.
What types of systems can be integrated?
-
PA / Intercom Systems
-
Access Control Systems
-
Strobe / Alarm Systems
-
Visitor Management Systems
-
Shooter Detection Systems
- License Plate Reader Systems
Any on-site system can be successfully integrated, as long as there is some way for it to accept an activating signal and/or send a signal when it is activated.
Requirements:
In order to integrate between our cloud system and on-site hardware, the on-site system must either offer an Application Programming Interface (API) or support activation using hard-wired voltage signals.
Two-way integration is possible, which means that no matter where the activation originates, whether in Share911/Share999 or on-site, both systems will activate.
1. Integration from Share911 / Share999 => On-site
Goal:
When an alert is broadcast in Share911, a corresponding activation of the on-site system is also triggered.
Requirements:
A. On-site system can accept a digital communication from the internet (API), or
B. On-site system can activate using a hard-wired voltage signal
If the on-site system offers an API, we integrate either through our existing Webhooks feature or a custom software implementation.
Case B: Hard-wired input
2. Integration from On-site => Share911 / Share999
Goal:
Requirements:
A. On-site System triggers a digital communication over the internet (REST, MQTT, etc), or
B. On-site System triggers a hard-wired relay
Case A: Digital communication
The on-site system is configured to send a digital payload with the details of the activation to one of our cloud endpoints, such as our Broadcast REST API.
Case B: Hard-wired relay
A system integrator will physically connect the on-site system to a hardware device, such as the AXIS D3110 Mk II Connectivity Hub, which then sends the digital payload to our cloud endpoint.