Skip to main content

Ride Operations Timeline Widget

A RideOps Dashboard widget that plots each ride's operating periods as a row on a shared timeline and highlights long waits between dispatches, so you can see operating continuity at a glance.

Written by Logan Bowlby

Overview

The Ride Operations Timeline widget plots when your rides were operating, laying each Location out as its own row on a shared timeline. Operating periods, gaps, and unusually long waits between dispatches all line up side by side, so you can compare rides against each other across the same stretch of the day.

Heads-up: This is a RideOps widget and relies on RideOps operating data being captured. If RideOps isn't in use at a Location, that ride has nothing to plot.


Reading the timeline

Each row is a Location, drawn across the period the Dashboard is showing. Along each row you can see when the ride was operating and where the gaps fall, with waits longer than your lag-time threshold called out so they stand out from normal load-and-dispatch timing.


The widget's settings

Two settings belong to the widget itself:

  • Lag time threshold — a number of minutes. Waits between dispatches longer than this are highlighted on the timeline.

  • Filter by opening hours — limits the timeline to your operating window instead of the full day, so closed hours don't read as downtime.


What else shapes the timeline

The widget doesn't carry its own date range. The timeline covers the period the Dashboard is set to, and which rides appear follows the Locations and Location Groups in scope — so changing the Dashboard's period or location scope changes what the timeline draws.

Note: This is why a timeline can look empty even when the widget is configured correctly — the period being shown may simply fall outside your operating hours.


Frequently asked questions

Q: How do I change the time range the timeline covers?
A: Change the period on the Dashboard.

Q: Why is the timeline empty?
A: Either there's no RideOps operating data for those rides in the period shown, or the period doesn't overlap your operating hours. Check that RideOps is in use at the Locations in scope, then widen the Dashboard's period.

Q: What does the lag-time threshold actually do?
A: It sets the line between a normal wait and one worth noticing. Gaps between dispatches longer than the minutes you set are highlighted; shorter ones aren't.

Q: Should I turn on filter by opening hours?
A: Usually yes. Without it the timeline covers the whole day, so the hours you were closed appear as gaps in operation.

Did this answer your question?