Overview
DMT RideGuard monitors rides with sensors and flags unusual behaviour, such as irregular movement, vibration or shocks. The integration lets RideGuard turn those findings into Mobaro Assignments on the right Location, for the User Group you choose, so your maintenance team follows up, documents and resolves them in Mobaro.
Detection, RideGuard’s own dashboard and its alerts stay at DMT. Mobaro connects your organization to RideGuard, tells RideGuard which Location and User Group belong to each monitored ride, and gives RideGuard an API key so it can create the Assignments.
At a glance |
|
Who can do this | Super Users, or a Role with Organization › Administrate |
Where | Configuration › Integrations › DMT RideGuard |
Works on | Backend (web) to set up. Assignments appear in the Backend and the app |
Availability | All organizations with a DMT RideGuard subscription and API key from DMT |
💡 Why this matters: A sensor alert only helps if someone acts on it. Routing RideGuard findings into Assignments gives each one an owner, a deadline and a record of what was checked.
How the integration works
When | What happens |
You save your DMT API Key | Mobaro creates an API key in your organization named DMT Rideguard Integration Key (Do Not Delete), with full (not read-only) access, and sends it to RideGuard |
You add or update a Location mapping | Mobaro sends RideGuard the DMT attraction ID, the Mobaro Location and the User Group to assign |
You delete a Location mapping | Mobaro tells RideGuard to remove that attraction’s mapping |
RideGuard detects an anomaly on a mapped ride | RideGuard creates an Assignment in Mobaro through the Mobaro API, using that key, on the Location and for the User Group |
Mobaro doesn’t fetch sensor data from RideGuard. The Assignment’s content, priority and due date come from RideGuard, not from settings in Mobaro. Once created, it works like any other Assignment: see Understanding the Assignments module.
🛑 Critical: Don’t delete or edit the DMT Rideguard Integration Key (Do Not Delete) API key. RideGuard uses it to create Assignments; without it, anomalies no longer reach your maintenance team in Mobaro, and nothing in Mobaro warns you.
Before you start
An active DMT RideGuard subscription, with sensors on the rides you want to monitor.
Your DMT RideGuard API Key, provided by DMT. Mobaro doesn’t generate it.
A Mobaro Location for each monitored ride, and a User Group for the team that should receive the Assignments. See Create and manage User Groups.
Connect your organization
1. Open DMT RideGuard
In the Backend, go to Configuration, open the Integrations tab and click the DMT RideGuard card. Cards show Enabled or Not enabled.
2. Enter the API key
Tick Enable integration to DMT RideGuard, paste the API Key from DMT and click Save. You’ll see DMT RideGuard settings saved successfully, and the Location Mappings table appears.
After saving, the API Key field is locked. To use a different DMT key, untick the box, click Save, then tick it again, enter the new key and save.
Map rides to RideGuard
1. Add a Location mapping
Under Location Mappings, click Add Location Mapping (the + button). The Map Location dialog opens.
2. Choose the Location, team and attraction
Pick the Location and the User Group that should receive the Assignments; both are required, one of each. Under External Locations, select the ride’s RideGuard attraction by Name and ID, which fills Remote ID. If the list is empty, type the attraction ID in Remote ID. Click Save.
The table lists each mapping’s Location, User Group and DMT RideGuard ID. Each Location can have one mapping.
3. Change or remove a mapping
Select a mapping and click Update Location Mapping to change its User Group or attraction; the Location can’t be changed. Click Delete Location Mapping and confirm to stop Assignments for that ride.
Turn the integration off
Delete the Location mappings first, so RideGuard stops creating Assignments; once the integration is off, the Location Mappings table is hidden and mappings can’t be changed. Then untick Enable integration to DMT RideGuard and click Save, which removes the saved DMT key. If the save fails, contact Mobaro Support. Unticking doesn’t delete the DMT Rideguard Integration Key (Do Not Delete) API key; if you have the API tab, delete it in Configuration › API › API Keys, or ask Mobaro Support.
⚠️ Heads-up: Each time the DMT key is saved, Mobaro creates another key with the same name and doesn’t remove the old one. If you see several, check the Created date and ask Mobaro Support before deleting any.
Best practices
Map only rides with RideGuard sensors installed.
Use a User Group owned by the maintenance team responsible for the ride, and keep its membership current.
Treat a RideGuard Assignment like any maintenance finding: record what was checked and whether the ride is safe to run.
Keep your DMT API key in a password manager.
Frequently asked questions
Is the integration two-way?
Yes, in a limited way. Mobaro sends RideGuard an API key and your Location and User Group mappings; RideGuard creates Assignments in Mobaro. Mobaro doesn’t fetch sensor data from RideGuard.
Where do the sensors and the API key come from?
From DMT. RideGuard is a separate product with its own hardware and subscription. Mobaro creates only its own key for RideGuard to use.
Why is there an API key called “DMT Rideguard Integration Key (Do Not Delete)”?
Mobaro created it when the DMT key was saved. RideGuard uses it to create Assignments. Leave it in place while the integration is in use.
Can I change which team receives the Assignments?
Yes. Select the mapping, click Update Location Mapping and pick another User Group. New anomalies go to that group; existing Assignments keep their assignees.
Do RideGuard Assignments make the ride Not ready for operation?
Only if your readiness colours treat it as critical, for example when RideGuard sends it as high priority and Red if one or more active high priority assignments exist is on. Mobaro doesn’t block the ride by itself. See Configuring readiness colors on the Location Overview.