Overview
This guide is for the Operator running a ride from the RideOps app on a tablet. It walks through a full operating day: signing in, opening the ride, recording dispatches and queue times, handling Downtime, leaving handover notes, and closing.
For the admin setup behind these screens, see Setting up RideOps.
At a glance |
|
Who can do this | Users listed as Operators in the Location's RideOps Settings, with a PIN Code and an active Certification for every Required Competency |
Where | RideOps app on the tablet, signed in with a RideOps Key that covers the ride |
Works on | RideOps |
Availability | All organizations, once RideOps is set up for the Location |
💡 Why this matters: RideOps is the live record of how the ride ran today. Every dispatch, queue update and Downtime you log feeds throughput reporting, guest-facing wait times and the operational audit trail, so logging as you go keeps the data accurate without anyone reconstructing the day afterwards.
Sign in
Open the RideOps app on the tablet. If the RideOps Key covers more than one Location and allows switching, choose the ride you're operating.
On Operator Selection, tap your name and enter your 4-digit PIN, so the day's activity is recorded against you. Use Search to find your name. A greyed-out name means that Operator has no PIN Code or is missing a Required Competency; ask a supervisor to check.
If Mobaro has enabled barcode sign-in for your organization, you can tap Scan badge to sign in and scan your badge instead of finding your name, then enter your PIN as usual. See Enable barcode sign-in for RideOps operators.
After 5 wrong PIN attempts your PIN is locked until an administrator clicks Unlock PIN Code on your user in the Backend.
Open the ride
The status card on the RideOps dashboard tells you what has to happen before the ride can open.
Not ready for operation: RideOps lists what's outstanding, such as Checks that are required, Critical assignments, Handover notes requiring acknowledgement and Positions that require an attendant. Each has to be dealt with first.
Ready for preopening checklist: tap a Checklist under Available Preopening Checklists and complete it. If approval is required, it shows Awaiting checklist to be approved by supervisor until someone allowed to validate it approves it.
Ready for operation: the ride can be opened.
Sign Attendants in to the ride's Positions: tap a Position and choose who is staffing it. Positions marked Mandatory must have an Attendant before the ride can open.
Tap OPEN. The ride's status changes to open and, where the Attractions.io integration is configured, the live status and queue time start flowing to the guest app.
If no critical-for-operation Checklist has been completed for the ride today, RideOps shows a Critical Alert. When you tap OPEN, it asks you to confirm in No scheduled maintenance checklists: Disregard Warning opens the ride, Cancel Opening doesn't. If your admin has set a custom message for this case, RideOps shows that message instead and doesn't ask.
🛑 Critical: Disregard Warning opens the ride even though no maintenance check has been completed today. Only use it if your site's procedure allows it; otherwise tap Cancel Opening and contact a supervisor.
Run the ride
Recording dispatches: each time a unit leaves, record the dispatch with the number of riders and, if a unit is out of service, how many units were available. RideOps compares this with your dispatch targets to track throughput. If Delayed Dispatches are enabled, you can flag a dispatch as delayed and pick one of your organization's reasons. See Managing queues and dispatches in RideOps.
Updating the queue time: post the current wait time in the queue widget. RideOps warns you when the posted time hasn't been updated within the time your admin set, and when too long passes between dispatch entries. The queue time is what guests see if a guest-app integration is connected.
Logging downtime: if the ride stops unexpectedly, tap the lock button and then Start Downtime. Pick a Downtime Template if your park uses them, or type a Description, then tap Start downtime. See Creating downtime templates for use in RideOps.
What you can do next depends on the Downtime:
If your organization has turned on Allow RideOps operator to resolve non blocking downtime, the Downtime card shows Reopen ride (or Resolve downtime if the ride isn't ready yet).
If that setting is off, RideOps asks you to contact an administrator to resolve the Downtime.
A Blocking Downtime has an Assignment linked to it. The ride can't open until qualified staff resolve the Assignment, or the Downtime is closed in the Backend.
Use Downtime for unplanned stoppages and faults, and Close Ride for end-of-day or planned closures. See Using downtime in Mobaro.
Notes and handovers: use Notes to record anything the next person needs to know, such as an intermittent fault or a temporary workaround. If your organization uses handover notes that require acknowledgement, they must be acknowledged before the ride can open. See Acknowledging handover notes (for operators).
Switch Operator or ride
When another Operator takes over, open the Operators page and tap Switch next to your name, then have the new Operator sign in. Signing in as another Operator hands over control of the ride. Tap Sign out to sign out without handing over.
If the RideOps Key allows switching, use Change Location in the RideOps settings to move to another of the key's rides on the same tablet.
Close the ride
At the end of the operating day, tap the lock button and then Close Ride. If your ride is set up for it, Close Location asks you to confirm or correct the day's Cycles and Riders, which is useful when a manual count differs from what was logged. Tap close ride. If a Closing Checklist is configured, complete it. RideOps then asks whether you want to sign out.
Best practices
Log dispatches as they happen rather than in batches; the dispatch warning usually means one went unrecorded.
Keep the queue time current, especially when a guest-app integration shows it to guests.
Start a Downtime the moment the ride stops, with a clear description or the right template.
Close the ride at the end of every operating day, even a quiet one, so the next day starts from a clean state.
Frequently asked questions
Why can't I open the ride?
The status card lists what's outstanding: a required check, a critical Assignment, a handover note to acknowledge, an unstaffed mandatory Position, or a Preopening Checklist that isn't done or approved. A Blocking Downtime also stops it. Ask a supervisor if a missed check needs approving or rescheduling.
RideOps let us open the ride without the maintenance check. Why?
Only outstanding critical-for-operation Checklists block opening. If none is outstanding and none was completed today, RideOps warns you and lets the Operator choose Disregard Warning. Mark the maintenance check critical for operation on its Schedule if it must block opening. See Schedule criticality and Location operational status.
Why is my name greyed out in RideOps?
You have no PIN Code, or you're missing an active Certification for a Required Competency. If your name isn't listed at all, you aren't an Operator on the Location. Ask a supervisor; see Setting up RideOps.
How do I log out of RideOps so someone else can sign in?
Open the Operators page and tap Switch next to your name to hand over to the next Operator, or Sign out. Closing the ride also offers to sign you out.
How do I switch to another ride on the same tablet?
Use Change Location in the RideOps settings. It only works if the tablet's RideOps Key covers that ride and has Allow Operators to switch location ticked. See Creating and managing RideOps key.
Can I end a downtime from RideOps?
Yes, if your organization has turned on Allow RideOps operator to resolve non blocking downtime and the Downtime isn't Blocking: tap Reopen ride or Resolve downtime. Otherwise an administrator resolves it.