Overview
Use this guide when replacing, reassigning or rebuilding a RideOps tablet. Prepare the new device first, check the current ride configuration and preserve any work still held on the old tablet.
A replacement tablet needs its own setup. Settings held locally on the old tablet are not a device backup that automatically transfers to the new one.
At a glance |
|
Who can do this | Operators and the administrator responsible for the RideOps Key and Location settings. |
Where | RideOps on both tablets; Backend Configuration › RideOps and Locations |
Works on | Backend (web), RideOps |
Availability | All organizations |
💡 Why this matters: Preparing the key, ride and local settings before the change reduces disruption when the tablet is handed over.
Prepare the replacement
1. Confirm the ride and key
Identify the Location the tablet will operate and obtain the appropriate RideOps Key through your administrator. Check that the key includes that Location and that its switching policy fits how the tablet will be used. See RideOps Keys.
2. Record the current settings
Note the widgets, dispatch input method and closing-count options in use. Check whether Lock RideOps app configuration is enabled on the Location: locked settings come from the Backend, while unlocked local choices must be configured on the replacement. See tablet settings.
3. Install the tablet experience
Set up RideOps in the tablet’s browser and add it as a PWA using the tablet installation guide. Connect it to the intended network, enter the RideOps Key and select the correct Location.
Preserve the old tablet’s work
Before retiring the old tablet, review unfinished Checklists and let outstanding actions and file uploads synchronize. Confirm the important completed records in the Backend. If the device cannot synchronize, keep its data intact and contact Support before resetting it.
🛑 Critical: Factory Reset clears RideOps local stores, including queued actions, file uploads and Checklist progress. Do not reset or clear browser site data while work exists only on that tablet. Having the key ready does not protect unsynchronized work.
Coordinate the operational handover so staff know which tablet is in use. Avoid recording the same dispatch or other action on both devices as part of the changeover.
Verify the new tablet
The displayed Location is correct.
The intended Operator can sign in with their own PIN and required Competencies.
Attendant Positions and current ride information are visible.
Required widgets and dispatch inputs match the site’s setup.
Relevant manuals and Checklists can be opened.
The tablet can communicate with Mobaro.
Use an appropriate test arrangement for any submission or state change. Do not open a ride or invent a dispatch merely to test the replacement. See the Operator workflow for normal use.
Retire or reassign the old device
Once the records are confirmed and the replacement is ready, follow your device-retirement process. If resetting RideOps, have the intended key available for any later reuse; see resetting RideOps.
If you only need to use another Location already covered by the key, Change Location may be sufficient. It requires the key to allow switching and the Operator to be eligible at the destination. A reset is not necessary for every Location change.
Best practices
Keep a record of the intended tablet settings.
Confirm server records before removing local data.
Check whether a key is shared before changing or revoking it.
Frequently asked questions
How do I change the Location assigned to a tablet?
Use Change Location when the key allows it and covers the destination. Otherwise arrange the appropriate key and setup. See RideOps Keys.
Why is Factory Reset missing?
A locked RideOps app configuration hides it. Coordinate any temporary change with the Location administrator. See locked tablet settings.
Where can I find RideOps Keys?
Authorized administrators manage them under Configuration › RideOps. See creating and managing RideOps Keys.