New at Mobaro

Hi there,

We're delighted to introduce a new feature that allows for the activation of reminders to currently logged-in users. This functionality is particularly beneficial for organizations that share devices.

Essentially, this feature displays the identity of the user currently utilizing the system. Subsequently, users have the choice to seamlessly continue their ongoing session or to perform a logout, followed by logging back in as themselves.

This feature's availability is contingent upon your organization's configuration settings. If you're interested in implementing this feature, we kindly request your involvement by clicking the provided link and providing the necessary information. Please be aware that feature activation requests must originate from a Super User or a designated Main Account contact.

Hi there! RideOps operator are now able to easily register Notes and Downtimes with the new template system.

The addition of these templates will allow administrators create ride- and organization-specific Notes and Downtime templates to allow for easier registration and creation of Notes and Downtimes within RideOps.

You can begin creating Downtime Templates by going to Configuration and clicking 'Downtime' and start creating Note Templates by going to Configuration and clicking 'RideOps'.

RideOps version 4524 introduces a vast amount of improvements and customizations organizations can add to their current setup.

Pop-out Modal for RideOps setup

To help get a better overview of each location's setup in RideOps, we have improved the setup flow of RideOps to have a pop out window which will allow you to overview all information at once.

Define a minimum time between dispatches

You are now able to add in a buffer time between dispatches that lock the dispatch grid for x-seconds to ensure operators are not duplicating or falsifying dispatch information.

Lock down RideOps settings centrally

You can now lock down specific settings per-location via the RideOps Settings modal. These settings include:

• Inputting (changing) throughput and dispatch information when closing a location
• Showing/hiding the queue time and dispatch widget
• Defining which version of the dispatch widget is shown (Grid vs. Spinner)
• Defining the maximum riders per dispatch (when using the Spinner dispatch widget)
• Defining the number direction for the dispatch grid (ascending vs. descending)

Customized 'Not ready for operation' text

You are now able to create a write custom messages shown to operators for locations that are not ready for operation per-location.

Define a User's ability to operate easily

Super Users can now directly define where a user can be an Operator from the User edit window.

The latest version of the Operational History Details and Location Operational History widgets include the ability to see and compare lag time with downtime turnovers.

This will allow users to be able to see the computed time between a downtime's resolution and the Open function from either the operational logging panel or the RideOps application. This in turn allows you to calculate time between a maintenance handover of the attraction and the operational lag time.

To ensure downtimes that span multiple days do not affect these metrics, these widgets require a Lag Time Threshold to be defined to ensure outliers or incorrect data is not logged.