Overview
RideOps in Mobaro enables efficient and secure ride operations by tailoring settings for each location. This includes configuring Operators, Attendants, Checklists, dispatch settings, and enabling Operational Logging. Follow the steps below to fully set up RideOps for a specific Location.
Step 1: Enable Operational Logging
Navigate to Locations
In the Mobaro Backend, go to 
Locations and select the Location where you want to enable RideOps.
Enable Operational Logging
Click on 
Edit on the Location. Scroll down and turn on 
Operational Logging by clicking the Enable Operational Logging checkbox.
Save Settings
Ensure that changes are saved before proceeding with further RideOps setup.
Note: Operational Logging is required for RideOps to function properly.
Step 2: Enable RideOps
Once Operational Logging is enabled, the option for enabling RideOps will become active.
Enable RideOps
Scroll down to the 
RideOps section and turn on RideOps by clicking the Enable RideOps checkbox.
Step 3: Configure Operators and Attendants
Assign Operators and Attendants for the location:
Operators
Add individual Users or User Groups as Operators for this Location. optional Assign Required Competencies to ensure only certified Users can operate the ride.
Warning: Assigning User Groups will allow all members of the group to operate the Location, regardless of Location-specific membership.
Attendants optional
Add individual Users or User groups as Attendants for this Location. optional Assign Required Competencies to ensure only qualified Users can staff attendant positions.
Warning: Similar to Operators, assigning User Groups as Attendants overrides Location membership restrictions.
Step 4: Assign Checklists for RideOps optional
Assign Preopening Checklists: These must be completed before the Location can be opened for operation.
optionalConfigure the Preopening Checklist Validity to set the time frame within which the Checklist remains valid. After this time, RideOps will prompt the Operator to re-complete the Preopening Checklist.optionalEnable Require Approval to mandate Checklist validation before operation.
Assign Closing Checklists: These must be completed before the Location is officially closed.
Caution: Currently, RideOps does not support the following features in Checklists:
Assignment triggers
Note: For detailed information on Preopening and Closing Checklists, see Configuring Checklists for RideOps.
Step 5: Configure Queues and Dispatches
Queues optional
Set maximum queue time and update intervals.
Configure warnings for delays in queue updates.
Dispatches
Define the number of dispatchable units (e.g., trains or cars).
Set capacity per unit and time between dispatches.
Note: For detailed instructions, see Managing Queues and Dispatches in RideOps.
Step 6: Create a RideOps Key
A RideOps Key allows Operators to access the RideOps interface for a specific Location.
Navigate to
Configuration > RideOps in the Mobaro Backend.Click + Create and assign a name to the key.
optionalLimit the key to specific Locations or allow Operators to switch between assigned Locations.Save your changes.
Tip: Use separate RideOps Keys for categories of Locations to simplify access control. See Creating and Managing RideOps Keys for detailed steps.
Step 7: Test Your RideOps Setup
Before launching RideOps, test your setup:
Log in as an Operator and simulate operational tasks (e.g., completing Checklists, dispatching units).
Verify that queue updates and dispatch timings meet your configurations.
Review the
View Operational Log via the 
Locations page to ensure that logs are being recorded correctly.Check competency enforcement to ensure only authorized staff can access RideOps.
Next Steps
Once your basic RideOps setup is complete, you can further refine your configuration with advanced features like:
Assigning Positions to Operators and Attendants.
Customizing RideOps messages, statistics, and functionality.
Refer to our additional articles for step-by-step guidance.
Frequently Asked Questions
Q: What is the purpose of Operational Logging?
A: Operational Logging tracks key actions such as uptime, downtime, and lag time. This log provides an audit trail for performance analysis and compliance purposes.
Q: Can I disable Operational Logging after enabling it?
A: Operational Logging is required for RideOps to function. It is not possible to disable it once RideOps is in use.
Q: What happens if Operational Logging is not enabled?
A: Without Operational Logging, RideOps features like dispatch tracking, queue updates, and operational reporting will not function properly.
Q: How can I ensure only certified Users operate rides?
A: Use the Competencies section to assign required Certifications for Operators and Attendants. Only certified Users will be granted access.
Q: What happens if an Operator's RideOps Key is not configured correctly?
A: If a RideOps Key is not assigned or configured for the correct Locations, Operators will be unable to log in or access the RideOps interface. Ensure the key is properly linked to the Location(s) they need to operate.
Q: Can one RideOps Key be shared across multiple Locations?
A: Yes, you can assign a single RideOps Key to multiple Locations. You can also enable the Allow Operators to switch between Locations option to allow seamless transitions between assigned Locations.
Q: What is the purpose of limiting RideOps Keys to specific Locations?
A: Limiting keys to specific Locations ensures Operators can only access rides they are authorized to operate. This prevents accidental or unauthorized access to other Locations.
Q: What devices are compatible with RideOps?
A: RideOps Keys are compatible with any device running the Mobaro mobile app. For recommended device specifications, refer to our Recommended Devices Guide.