Integration with e-Remiza and selective-alarm (DSP-50) systems
RespondGrid does not replace the dispatch system or the siren. It takes the alarm you already have (from e-Remiza or from a DSP system) and carries it to the phones of the whole unit at once: with the address, a one-tap “coming” answer and a view of who is coming and how soon.
Three ways for an alarm to reach RespondGrid
Pick the one that fits the system you have in the station. You can also combine two.
API integrationYou have e-Remiza
When: An integration through its API: you connect nothing to phones.
- The RespondGrid server polls e-Remiza with your unit's service account (about every 20 seconds). On a new call it sends the alert to all responders' phones at once.
- The type, address, description and scene come from e-Remiza without retyping. RespondGrid only reads and writes nothing into e-Remiza.
- Besides alerts: a roster import with qualifications (always with a preview before saving) and vehicle positions on the map.
What the unit does. Creates a separate service account in e-Remiza (read-only) and enters its details in the panel: Manage, Integrations and devices. The password is stored encrypted.
Trigger phoneYou have a DSP-50 system with a GSM terminal
When: If the GSM terminal rings the firefighters, add the trigger phone's number to the list.
- An old Android phone on a charger in the station works as the trigger. When someone calls its number, the server raises the alert on the phones of the whole unit.
- A call carries no address, so the alert arrives without details and the unit adds them. If the unit also has e-Remiza, the ring makes the server check e-Remiza at once.
- Every call to that number raises the alert, wrong numbers included, so the SIM card's number is given only to the alarm system or the dispatcher.
What the unit does. Creates a trigger account, signs it in on an Android phone, switches on “Alarm from a call” and adds the number of its SIM card to the list the system rings. The attempts log in the panel shows whether the phone works.
WebhookYou have a system that sends HTTP requests
When: A webhook: the unit's own token, the alert at once.
- The unit's administrator creates a token in the panel; it works for that unit only and can be revoked at any time.
- The outside system sends an HTTP request with the token. All fields are optional: category, address, description, a point on the map, a case number.
- A repeat with the same case number is the same alarm, so it will not ring twice.
What the unit does. Creates a token in the panel (Manage) and sets its own system to send the request. RespondGrid supplies nothing on the sending side.
Selective and simultaneous alerting: what DSP does and what RespondGrid does
DSP systems call units on their own side: selectively (chosen units or groups) or simultaneously (many recipients at once), over radio, sirens and a GSM terminal.
RespondGrid starts where the signal ends. The alert reaches the phones of all the unit's responders who accept it at the same moment, and adds what a signal cannot: the address and route, a one-tap “coming” answer, the travel time, a view of who is coming and the roster's availability.
RespondGrid does not split an alert into groups or functions. For an alert raised by hand you only choose which vehicles it goes to.
The three ways compared
| Way | When to choose it | What the alert carries | What the unit does |
|---|
| e-Remiza (API) | The unit has e-Remiza | Type, address, description, a point on the map | A separate service account, details in the panel |
|---|
| Trigger phone | A DSP system with a GSM terminal or a dispatcher rings a phone | The signal only, no details | A trigger account, an Android phone, the number on the list |
|---|
| Webhook | The system can send an HTTP request | Whatever the system sends | A token in the panel, setting up the request |
|---|
What RespondGrid does not do
- It does not replace the dispatch centre, the 112 number or the siren. Alerting complements dispatch systems and official notification procedures.
- It supplies no devices or software on the side of the system that sends the signal.
- “e-Remiza” and “DSP-50” are names of other companies' systems, used descriptively. RespondGrid is not their partner and is not endorsed by them.
Integrations belong to alerting. The unit panel is free, and alerting is free for the first 3 months.
Pricing · How it works
Questions about integrations
Does RespondGrid replace the dispatch system, the dispatch centre or the 112 number?
No. The dispatch system and the dispatch centre take the incident report; RespondGrid carries it to the responders' phones and collects their answers. The terms of service say outright that alerting complements, and does not replace, dispatch systems and official notification procedures.
Where does the alert come from?
Three ways. From e-Remiza: an API integration, the server polls e-Remiza itself and you connect nothing to phones. From a system that rings a phone (for example a DSP-50 with a GSM terminal): a trigger phone in the “alarm from a call” mode. From a system that sends HTTP requests: a webhook with the unit's token. An alert can also be raised by hand in the panel or in the app.
Does RespondGrid work with e-Remiza?
Yes, it is a ready API integration. The unit creates a separate service account in e-Remiza (read-only) and enters its details in the panel. The RespondGrid server polls e-Remiza about every 20 seconds and on a new call sends the alert to all responders' phones at once, with the address and the scene. The integration also imports the roster with qualifications (with a preview before saving) and shows vehicle positions on the map. RespondGrid only reads and writes nothing into e-Remiza.
Can a DSP-50 or another selective-alarm system be connected?
Yes, if the system has a GSM terminal that rings the firefighters. Add the number of the trigger phone (an old Android phone on a charger in the station, with the “alarm from a call” mode on) to that list, and the ring raises the alert on the phones of the whole unit. A call carries no address, so the alert arrives without details. Every call to that number raises the alert, so it is given only to the alarm system. A system that can send an HTTP request can be connected with a webhook. RespondGrid supplies no devices on the DSP system's side.
What is the difference between selective and simultaneous alerting?
These are the names used in DSP systems. Selective alerting calls chosen units or groups, simultaneous alerting many recipients at once, over radio, sirens and a GSM terminal. It happens on the DSP system's side. RespondGrid starts after the signal: it sends the alert to the phones of all the unit's responders at the same moment and adds the address, a one-tap “coming” answer, the travel time, a view of who is coming and availability. It does not split an alert into groups or functions; for an alert raised by hand you only choose vehicles.
What is needed to connect e-Remiza?
A separate service account in e-Remiza (not the one another system already works on, since e-Remiza invalidates a session when two programs sign in) with permission to view alarms, and an active alerting subscription (the first 3 months are free). The unit's administrator enters the login, password and unit identifier in the panel, under Manage. The “Fetch an alarm from e-Remiza” button checks the connection without waiting for a real call-out.
Do the integrations work on an iPhone?
An alert from any source reaches both Android phones and iPhones. The trigger phone that picks up a ring or a dispatch-system notification is meant for an Android phone.