Overview
In RideOps, Queues track guest wait times, while Dispatch Settings determine how often ride units are dispatched and how many guests should be accommodated. Setting up these configurations properly ensures accurate data reporting and throughput expectations.
Configure Queue Settings
Queues help Operators manage guest wait time updates.
To configure queue settings:
Navigate to RideOps Settings
Open the
Mobaro Backend, go to 
Locations, and select the desired location and click on 
Edit.Scroll to the
RideOps section and click on RideOps Settings.
Set Maximum Queue Time
Scroll to the
Queues section.In the Maximum Queue Time field, enter the maximum allowable wait time in minutes (e.g., 120 minutes). The default is 60 minutes.
Set Queue Time Step Size
Adjust the Queue Time Step Size to define the increments for queue time updates (e.g., 5-minute steps).
Tip: Use smaller step sizes for rides with high guest volume to allow for more granular queue time adjustments.
Enable Queue Time Update Warnings
In the Queue Time Update Warning field, set the number of minutes after which a warning will appear if the queue time isn’t updated (e.g., 15 minutes).
Configure Dispatch Settings
Dispatch parameters control the expected frequency of ride unit dispatches and the max guest capacity per unit.
To configure dispatch settings:
Locate Dispatch Settings
In the same RideOps Settings screen, scroll to the Dispatches section.
Set the Number of Dispatchable Units
In the Number of Dispatchable Units field, enter the total number of units (e.g., trains or cars) that can be dispatched independently.
Define Capacity Per Unit
In the Capacity Per Dispatchable Unit field, enter the number of guests that each unit can accommodate.
Set Time Between Dispatches
Define the following in seconds:
Expected Dispatch Time: The average time between dispatches under normal conditions (e.g., 170 seconds).
Ideal Dispatch Time: The target time for efficient dispatching (e.g., 140 seconds).
Enable Dispatch Update Warnings
Configure the Dispatch Update Warning to alert Operators if the time between dispatches exceeds a certain threshold (e.g., 3 minutes).
Reminder: Adjust these settings based on your ride's capacity and throughput to prevent Operators from dispatching too frequently.
Understanding Dispatchable Units and Capacity Per Unit
To optimize ride operations in RideOps, it’s crucial to correctly configure the Number of Dispatchable Units and Capacity Per Dispatchable Unit (CPDU).
Number of Dispatchable Units
This represents the total number of operational units that can be dispatched independently for a specific ride or attraction.
Examples of Units: Trains, cars, boats, or any vehicle type used in the ride.
How it Works:
If your ride operates with 3 trains and all can be loaded and dispatched independently, you would set the Number of Dispatchable Units to 3.
If only 1 train can be on the track at a time, the setting should be 1.
Note: The value should reflect the maximum number of ride vehicles that can operate concurrently on the track or circuit.
Capacity Per Dispatchable Unit (CPDU)
This is the maximum number of guests that a single dispatchable unit can accommodate.
Examples of CPDU:
A roller coaster train with 16 seats would have a CPDU of 16.
A log flume boat with 8 seats would have a CPDU of 8.
How It Works:
For a ride operating with 2 trains, each with a seating capacity of 16 guests, the CPDU remains 16 (per unit).
The total ride capacity per dispatch will be calculated automatically based on the Number of Dispatchable Units x CPDU.
Tip: Capacity Per Dispatchable Unit always reflects the number of seats in a single unit, not the total capacity of all active units.
Common Misconceptions
Confusing Total Capacity with CPDU:
CPDU reflects the guest capacity per unit, not the total capacity of all units combined.
Example:
If a ride has 3 trains, each seating 20 guests:
Number of Dispatchable Units = 3
CPDU = 20
Total ride capacity = 60 guests per dispatch.
Incorrectly Counting All Units:
Ensure Number of Dispatchable Units matches the actual number of units operating simultaneously, not the total units available.
Best Practices for Configuration
Double-Check CPDU: Verify seating capacity for each unit daily to ensure accuracy.
Adjust for Downtime: If a unit is removed from operation (e.g., for maintenance), update the Number of Dispatchable Units accordingly.
Calibrate for Peak vs. Off-Peak Seasons: Adjust the dispatchable units during lower demand to match real-world conditions.
Warning: Misconfiguring CPDU or dispatchable units can lead to inaccurate throughput data and present misleading figures.
Frequently Asked Questions
Q: What’s the difference between expected and ideal dispatch times?
A: Expected dispatch time represents the average time needed between dispatches, while ideal dispatch time is the target for optimal performance. Both values help Operators balance efficiency with flexibility.
Q: Can I disable queue time or dispatch update warnings?
A: No, this is not currently possible.