This article is a guide about setting up your locations on Mobaro in order to get them ready to be utilized on the RideOps platform. RideOps is an add-on to your Mobaro system in order to track throughput, ride log notes, capacity utilization, wait times, downtimes, and more — learn more about it here.

RideOps gives you the ability to track multiple ride metrics and data through one easy to use app

Getting RideOps set up in Mobaro is an easy process as well as you will see below. There is some preliminary information you will need in order to have an accurate setup that allows you to gain extremely useful insights on the operational status of your locations:

  • Target dispatch times between units (i.e., average time between dispatches)
  • Maximum number of units
  • Available fillable seats per dispatchable unit (i.e., 24 seats per train, 30 seats per gondola, 4 seats per buggy, etc.)
  • The operators allowed to control this location
    • Optionally, you can include competencies required to operate the location as well that your operators must have in order to log into that location.


Setting up RideOps

Enable your location for Operational Logging

The first step to activate RideOps for your location is to Enable Operational Logging; this allows you to track metrics such as opening and closing times, downtimes, as well as more complex stats like MTBF and MTTR.


To enable this feature, click on the select box next to the location, click the edit Screenshot_2022-06-28_at_7.11.52_AM.png button, scroll to the Operations section and click Enable Operational Logging.

Enable RideOps for your location

Now that Operational Logging is enabled, we can move on to setting up RideOps. Click on the select box to Enable RideOps. This will open up a section to input dispatch information; fill out this section with per-ride information. It is important to ensure you are entering accurate data as the RideOps metrics will be compared against these inputs to generate metrics such as capacity utilization, dispatch target percentage, throughput goals, etc.

You will also need to enter the operators who are able to operate the attraction as well as optionally attach any competencies necessary to operate the location.

Creating your RideOps key

Once you have enabled RideOps for all of the locations to wish to track metrics on, it is now time to create your RideOps key; this key will be used to activate RideOps on your tablets.

  1. Navigate to the Configuration page on the Mobaro backend
  2. Click the RideOps tab
  3. Click the Screenshot_2022-06-29_at_8.20.06_AM.png to create your a new RideOps key
  4. Add a name for your key
  5. Enter the location(s) that should be included for this key.
    1. If a location is not properly set up for RideOps, you will receive a warning message about this. You will still be able to add these locations to the key, but will not be available in the RideOps app until they are correctly configured.

Tip: You can create different keys for the different areas in your park or create one key that holds all of your locations. Either way, the tablets will become location-specific once you enter your key. 

Setting up RideOps

Now that you have properly set up your locations and have created your RideOps key, you can now assign that key to the tablets you are designating to utilize.

Navigate to on the tablet browser.

Tip: It is recommended to utilize Chrome for Android devices and Safari for Apple devices in order to download the web app to the device. 

From the RideOps home screen, you will be asked to input your RideOps key, enter that key and select the location this tablet should be used for.

Tip: To change a location after you have entered the RideOps key and set up the tablet for a specific location, sign in to any operator's profile, click the RideOps logo Screenshot_2022-06-29_at_8.29.26_AM.png and click on Factory Reset. You will be required to enter in the RideOps key again. 

Setting up Operator Checklists for RideOps

You can also attach a pre-opening checklist that must be completed by the operator after all Critical for Operation maintenance checks have been completed, but before opening the location on RideOps. You can also attach closing checklists that must be completed upon closing the attraction for the day.

These checklists are built directly in the Mobaro backend application just like all other checklists, however, instead of being scheduled, they are attached directly to the location via the location editor window.


RideOps statuses

Not ready for operation

Not ready for operation screen will appear if there is any of the following:

  • Incomplete / awaiting validation (if enabled in configuration) Critical for Operation checklist
  • Active High Priority assignment (if enabled in configuration)
  • Missing Critical for Operation checklist


Ready for operation (with Pre-opening checklist prompt)

A Ready for operation (with Pre-opening checklist prompt) will appear if all Critical for Operation checklists have been satisfied and there are no (by configuration) elements keeping the location in a not ready to operate state. The operator will be able to complete their pre-opening checklist at this point.



Ready for operation

Ready for operation tag will appear either:

  • After the successful completion of the Operator pre-opening checklist, or
  • After the completion and approval of all Mobaro-related Critical for Operation activities

And ensuring no, by configuration, activities are keeping the location red.

If a pre-opening checklist is completed by the operator, this screen will also indicate when that checklist will "expire" (12 hours from the point of successful submission)



Downtime status will appear after a downtime event was triggered either:

  • By the operator in the RideOps application
  • By a user on the Mobaro backend application via the Downtimes page
  • By a user on the Mobaro mobile application via the Operations tile

Downtimes must be handled and closed in the backend prior to the operator receiving the Ready for operation status once again.

If configured, any high priority assignments related to the downtime must also be closed prior to a Ready for operation status to reappear.


RideOps Notes

With the introduction of the new Notes feature on RideOps, there are several new note types you can create within the configuration settings of RideOps. Below you will see the new types and what their end result will be.

The note types include:

  • No action
  • Require approval
  • Trigger assignment



To set up customized notes, go to the Mobaro backend and then go to the Configuration page, you will navigate to the RideOps section where you will see the ability to create custom notes. You can create as many note types as applicable to help communication between departments.

Operators will also see status indicators in the notes section to see the progress of any questions, requests, or work orders they have put in.






Please sign in to leave a comment.