Overview
RideOps is Mobaro's tablet app for ride Operators and Attendants. Setting it up for a Location means turning on Operational Logging and RideOps on the Location, filling in the RideOps Settings dialog, and creating a RideOps Key for the tablet.
This article walks through each column of the RideOps Settings dialog.
At a glance |
|
Who can do this | Super Users or a Role with Locations › Modify. RideOps Keys: Super Users only. |
Where | Locations › a Location › RideOps Settings; keys in Configuration › RideOps |
Works on | Backend (web) to configure; RideOps on the tablet |
Availability | All organizations |
💡 Why this matters: RideOps settings are per Location. What you set here applies only to the Location you're editing, so repeat the setup for every ride you bring into RideOps.
Turn on RideOps for a Location
1. Open the Location
In the Backend, go to Locations and open the Location you want to bring into RideOps.
2. Enable Operational Logging
In the Operations section, tick Enable Operational Logging. RideOps can't be turned on without it; see Utilizing Operational Logging.
3. Enable RideOps
In the RideOps section, tick Enable RideOps.
4. Fill in RideOps Settings and save
Click RideOps Settings, fill in the columns described below, and confirm the dialog. Then save the Location.
⚠️ Heads-up: If you close the dialog without Number of dispatchable units, Capacity per dispatchable unit and Time between dispatches, Enable RideOps is switched off again. Unticking Enable Operational Logging also switches RideOps off.
Operators
Operators are the Users who open, dispatch and close the ride in RideOps.
Operators: add Users or User Groups. Adding a User Group lets every member operate this Location, regardless of normal Location membership, so add individuals if only some should.
Required Competencies: only Operators with an active Certification for all the listed Competencies can operate the ride.
Each Operator also needs a PIN Code of exactly 4 digits, set on their user in the Backend. After 5 wrong attempts the PIN locks until someone clicks Unlock PIN Code on the user.
Checklists
Preopening Checklist: the Operator must complete it before the ride can be opened.
Preopening Checklist Validity (minutes): how long a completed Preopening Checklist stays valid. The default is 720 minutes (12 hours).
Require Approval for Preopening Checklist: the Preopening Checklist must be approved before the ride can be opened.
Closing Checklist: Operators are prompted to complete it when closing the ride.
Enable closing time reminder: reminds Operators to close the ride.
If a Checklist uses content RideOps doesn't support yet, the dialog warns you. See Configuring checklists for RideOps.
Queues
Maximum Queue Time: the longest queue time, in minutes, an Operator can post. Default 60.
Queue Time Step Size: the interval between selectable queue times, in minutes. Default 5.
Queue Time Update Warning Threshold: minutes expected between queue time updates before RideOps warns the Operator. Default 15.
Dispatches
Number of dispatchable units: the number of cars, trains or other units in the ride.
Capacity per dispatchable unit: how many people fit in each unit.
Seconds/Dispatch or Riders/Hour: choose the tab for how you describe the ride's pace. Seconds/Dispatch asks for Time between dispatches and Ideal time between dispatches; Riders/Hour asks for Riders per hour and Ideal Riders per hour.
Dispatch Update Warning: minutes expected between dispatch entries before RideOps warns the Operator. Default 15.
Minimum time between dispatches: seconds the dispatch button stays unavailable after each dispatch, to prevent accidental double taps.
Enable Delayed Dispatches: lets Operators record delayed dispatches with a reason. It appears only if your organization has the Delayed Dispatches feature.
For how Operators use these, see Managing queues and dispatches in RideOps.
RideOps Configuration
Message when the ride is not ready for operation and Message when the ride has no CFO checks: custom text Operators see when the ride can't be opened, or when no critical-for-operation Checklists are planned. Tell them who to contact.
Allow Operators to view Ride Statistics: shows Ride Utilization, Dispatches, Riders and similar statistics in RideOps.
Allow inputting dispatches when closing the location and Allow inputting total riders when closing the location: let the Operator correct the day's totals when closing.
Lock RideOps app configuration: uses these settings on the tablet and disables customization there. Widget settings can't be changed on the tablet, and Factory Reset is hidden.
Show queue time widget: lets the Operator update queue times.
Show rider dispatch widget: lets the Operator dispatch riders, with four settings. Rider dispatch input type is Grid or Spinner. Maximum riders per dispatch is the most riders per dispatch. Number direction is Ascending or Descending. Rider dispatch metric type sets whether the Operator counts Full seats or Empty seats.
Positions and Attendants
Positions are the roles around a ride, such as Front Load or Unload. Attendants are the Users who can staff them.
Add Position opens Configure Position for location. Give it a name and description, tick Mandatory if RideOps must not open the ride until an Attendant fills it, and add any Required Competencies.
Attendants: add Users or User Groups, plus any Required Competencies every Attendant needs. As with Operators, a User Group gives all its members access regardless of Location membership.
Create a RideOps Key
A RideOps Key connects a tablet to your organization's RideOps Locations. One key can cover one or many Locations. Only Super Users can create keys.
1. Open Configuration › RideOps
In the Backend, go to Configuration and open the RideOps tab.
2. Click Create
In Create RideOps Key, enter a Name (for example, Coaster Plaza Tablets). Optionally choose Limit to these locations (Leave blank for all locations) and tick Allow Operators to switch location.
3. Click Create again
Mobaro shows the key and a QR code to enter or scan on the tablet. You can show it again later from the key's row. The key itself can't be changed or regenerated; only its name, Locations and switching can be edited.
RideOps runs in the tablet's browser; see Setting up the RideOps app as a PWA on tablets and Creating and managing RideOps key.
ℹ️ Note: If Mobaro has enabled barcode sign-in for your organization, the RideOps settings panel on the same page has Enable barcode sign-in. It lets Operators find themselves by scanning a badge; they still enter their PIN. See Enable barcode sign-in for RideOps operators.
Test your setup
Sign in on the tablet as a test Operator and complete the Preopening Checklist.
Open the ride, dispatch a few times, update the queue time and assign an Attendant to a Position.
Close the ride and complete the Closing Checklist, plus the dispatch and rider totals if you enabled them.
Check the Operational Log records the opening, dispatches and closing with the right times.
Sign in as a User who lacks a Required Competency and check they can't operate the ride.
Next, you can add Downtime templates for RideOps and brief Operators with Operating a ride in RideOps.
Best practices
Use one RideOps Key per area of the park rather than one per ride.
Tie Required Competencies to Certification Processes so RideOps access follows training records.
Tick Mandatory only for safety-critical Positions, so openings aren't blocked unnecessarily.
Turn on Lock RideOps app configuration only after testing the settings with a real Operator.
In custom messages, name the team and extension to call rather than a person.
Frequently asked questions
Where do I find our RideOps key?
In the Backend under Configuration › RideOps, in the RideOps Keys table. Super Users can show a key again with its QR code, or create a new one. See Creating and managing RideOps key.
How do I get to RideOps on a tablet?
Open RideOps in the tablet's browser, add it to the home screen, and enter or scan your RideOps key. See Setting up the RideOps app as a PWA on tablets.
Why doesn't an operator show up in RideOps?
They must be listed under Operators for the Location, directly or through a User Group. They're shown greyed out if they have no PIN Code or are missing a Required Competency. Check their Certifications and PIN in the Backend.
How can I stop a ride opening until a checklist is done?
Set a Preopening Checklist in the Checklists column; RideOps won't open the ride until it's completed. Tick Require Approval for Preopening Checklist if a supervisor must also approve it.
How do I change how many guests can be counted per dispatch?
In RideOps Configuration, set Maximum riders per dispatch under Show rider dispatch widget. The ride's capacity is set by Number of dispatchable units and Capacity per dispatchable unit in Dispatches.
My PIN is locked in RideOps. How long does it last?
Until it's unlocked. A PIN locks after 5 wrong attempts, and it doesn't unlock by itself. Ask an administrator to open your user in the Backend and click Unlock PIN Code.