Skip to main content

Ride Operations Timeline widget

Read the Ride Operations Timeline: each ride's day as In Operation, Downtime, Recovery Lag and Out of Operation, with its date, Location and lag filters.

Written by Logan Bowlby

Overview

The Ride Operations Timeline widget draws one row per Location for a single day, showing when it was in operation, down, recovering after a Downtime, or out of operation. It answers "how did each ride's day actually go?"

It's built from openings, closings and Downtimes recorded through Operational Logging. It doesn't use RideOps dispatches, so it works whether or not a Location uses RideOps. For the definitions, see Uptime, downtime, and lag time explained.

At a glance

Who can do this

Super Users, or a Role with Dashboard Templates › Manage, add it. Viewers see data only for Locations they can see.

Where

Dashboard Templates › a template › Add a widget › Operational › Ride Operations Timeline

Works on

Backend (web)

Availability

All organizations. Only Locations with Enable Operational Logging appear.

Ride Operations Timeline widget with a row per ride coloured by operating state through the day

What it shows

Segment

Colour

What it means

In Operation

Green

The Location was open (an uptime period). If it's still open, the bar runs to now.

Downtime

Red

A Downtime that started that day, from its start to its start plus its confirmed duration. Without a duration yet, it ends when it was resolved or closed, or at the end of the day (now, for Today).

Recovery Lag

Orange

The gap from the end of a Downtime to the next opening.

Out of Operation

Grey

Any other time the Location was closed, or the whole day if nothing was recorded.

The Time of Day axis always spans the whole day, in the dashboard's time zone. For Today, bars stop at the current time and the rest of the day stays blank. Recovery Lag is the timeline's view of lag time: the extra time a ride stayed closed after its Downtime ended.

⚠️ Heads-up: A Downtime that started before the day you're viewing isn't drawn. A ride that went down yesterday and is still down shows grey Out of Operation today, not red Downtime (known issue). Check the Downtime list for long Downtimes.


Settings and filters

Setting

What it does

Default

Date (button at the top left)

The day to show: Today, Yesterday or a Specific Date. There's no longer range.

Today

Locations

Pick Locations or Location Groups, with no maximum, and click Apply Filter. Required: the timeline stays empty until you choose.

None

Lagtime Threshold

Enter Lagtime Threshold (in minutes) and click Apply Filter. A Recovery Lag longer than this gets Exceeds lag time threshold in its tooltip. It doesn't change colours or hide anything. The bin icon clears it.

300 minutes

Filter by Opening Hours (calendar button)

Draws each row only from the Location's earliest opening time to its latest closing time that day. Locations without opening hours keep the whole day.

Off

Title

Click the widget's title to rename it; the cross resets it.

Ride Operations Timeline

Ride Operations Timeline widget settings

Reading the widget

Hover over a segment to see its type, its start and end time (HH:mm) and its duration. Downtime segments add their state, such as State: Closed. Segments can't be clicked. The legend lists each ride; click a name to hide or show that ride's bars. Each row is 32 pixels high; with more than about 18 rows, the widget scrolls.

Locations without Operational Logging are left out without a message, and you only see Locations you have access to. See How access works in Mobaro.

The widget reloads with the dashboard every 10 minutes (there's no setting to turn this off) and when you change a filter; times are in the dashboard's time zone. Bulk filtering and the Location Switcher can change its filters, and a Personal filter keeps your changes. See How to use the Dashboard.


Best practices

  • Turn on Filter by Opening Hours and keep each Location's opening hours up to date. See Add opening hours to a Location.

  • Keep a Lagtime Threshold that matches your target restart time, so slow recoveries are flagged.

  • Close Downtimes promptly with an accurate duration, so the red and orange segments are right.

  • Save a Personal filter per area with that area's Location Group.


Frequently asked questions

How do I make the timeline start at 09:00 instead of 00:00?

You can't set a start and end time: the axis always shows the whole day. Turn on Filter by Opening Hours to draw each ride only within its opening hours for that day.

Can I see when the first dispatch of the day was?

Not on this widget: it shows opening, closing and Downtimes, not dispatches. Open the Location's Operational Log and tick Dispatch. See Log book on the web — the Operational Log dialog.

Why is the timeline empty?

Choose Locations in the Locations filter; nothing shows until you do. Only Locations with Enable Operational Logging appear. A ride with nothing recorded that day shows as grey Out of Operation.

What does the lag time threshold do here?

It only flags long Recovery Lags with Exceeds lag time threshold in the tooltip. On the Location Operational History widget, the same setting leaves longer lag times out of the totals.

Did this answer your question?