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.
What is Operational Logging?
Operational Logging captures all key ride operation activities in a detailed log. This includes timestamps for dispatches, queue updates, and downtime registrations. It provides an audit trail for compliance and performance tracking, helping operators and administrators monitor ride operations effectively.
Note: Operational Logging must be enabled for RideOps to function correctly.
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
Open the 
Settings for the location. Turn on Operational Logging by toggling the corresponding option.
Save Settings
Ensure that changes are saved before proceeding with further RideOps setup.
Step 2: Configure Operators and Attendants
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 3: Set Checklists for RideOps optional
Assign Preopening Checklists: These must be completed before the ride 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 ride is officially closed.
Caution: Currently, RideOps does not support the following features in checklists:
Assignment triggers
Step 4: Configure Queues and Dispatches
Queues optional
Maximum Queue Time: Set the maximum allowable time (in minutes) for the queue.
Queue Time Step Size: Define the interval (in minutes) for queue time adjustments.
Queue Time Update Warning: Set a threshold for the expected interval between queue time updates.
Dispatches
Dispatchable Units: Set the number of dispatchable units (e.g., trains, cars).
Capacity Per Dispatchable Unit: Specify the capacity for each unit.
optionalTime Between Dispatches: Configure the expected and ideal time (in seconds) between dispatches.optionalDispatch Update Warning: Set a minimum time (in minutes) between updates by operators
Step 5: Configure RideOps Messages and Options
RideOps Configuration optional
Add custom messages for Operators when:
The ride is not ready for operation.
CFO checks are missing or incomplete.
Enable Allow Operators to view Ride Statistics to grant access to utilization, throughput, and dispatch data.
Enable Lock RideOps app configuration to prevent Operators from changing specifical RideOps configurations.
Step 6: Assign Positions optional
Configure Position Details
Name: Enter a name for the position (e.g., Greeter, Loader).
Description: Optionally, provide a brief description of the position’s responsibilities.
Mandatory: Check this box if the position must be staffed for the location to be operational.
Reminder: Mandatory positions must have at least one attendant assigned before the location can open.
Assign Required Competencies
Use the Required Competencies field to add specific certifications or qualifications needed for this position. Only attendants with these competencies will be able to fill the position.
Note: Competencies ensure that only qualified staff are assigned to critical roles, maintaining operational safety and compliance.
Save the Position
Click 
Save to add the position to the list for the location. Repeat the process for additional positions as needed.
Step 7: Create a RideOps Key
A RideOps Key allows you to assign and control access to RideOps for specific locations. This step ensures that Operators can log in and operate rides seamlessly. Follow the steps below to create a RideOps Key:
Navigate to the Configuration Section
Open the Mobaro Backend and select 
Configuration. Click on the RideOps tab at the top of the Configuration page.
Create a New RideOps Key
Click the + Create button under the RideOps Keys section to open the RideOps Key editor.
Configure the RideOps Key
Name: Provide a name for the key (e.g., "Galaxy Coaster Key").
Limit to Locations: Assign the key to specific locations by adding them to the Limit to these locations field. Leave this blank to allow access to all locations.
optionalAllow Operators to Switch Between Locations:Check this box if Operators need to switch between the locations assigned to this key.
Leave it unchecked to restrict Operators to one location at a time.
Save the Key
Click Create to finalize the RideOps Key. It will now appear in the RideOps Keys list under Configuration.
Verify Key Assignment
Ensure that the RideOps Key is assigned to the correct locations and users have access to it.
Note: Operators using devices linked to a RideOps Key can only access the locations and functionalities specified during the key's configuration.
Step 8: Test Your RideOps Setup
Log in as an Operator or Attendant and verify access permissions and checklist functionality. Use simulated operations to confirm that dispatch and queue configurations meet requirements. Review the 
View Operational Log via the 
Locations page to ensure that logs are being recorded correctly.
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.