Overview
The Operational Overview widget shows a card for each Location with Operational Logging: whether it's open or down right now, and today's uptime, downtime and number of Downtimes. For Locations with RideOps, the card also shows today's dispatches, riders, average queue time and who is operating the ride.
Use it during the operating day to spot rides that are down, unstaffed or running below capacity. To add the widget to a dashboard, see How to set up Dashboard Templates.
At a glance |
|
Who can do this | Anyone who can view the dashboard. To keep changed widget settings, save them in a Personal filter. |
Where | Dashboards › a dashboard › Operational Overview widget (category Operational in the widget list) |
Works on | Backend (web) |
Availability | All organizations. Locations need Enable Operational Logging; ride figures need RideOps on the Location. |
💡 Why this matters: One live view of every ride's status and today's numbers lets you react during busy hours — for example, moving staff to a ride whose queue is building or whose operator hasn't signed in.
Read a Location card
Each card is one Location. Locations that aren't ready for operation are listed first, then the rest, each in alphabetical order.
Title bar: red when the Location isn't ready for operation, green when it is. This is the same readiness as on the Location Overview widget, which explains what turns a Location red. Click a red Location's name to see what's holding it, if you're allowed to.
Status box: at the left of the title bar, gray (closed), green (open), yellow (non-blocking Downtime) or red (Blocking Downtime). Hover over it for a description, and click a yellow or red box to open the Location's active Downtimes. See Downtime on Dashboards.
Below the title, the card shows today's figures. The icons have no labels: hover over a figure to see its name and value.
Figure | What it shows |
Uptime | Share of today's uptime plus downtime that the Location was open. Hover for the time. |
Downtime | Share of today's uptime plus downtime lost to Downtimes. Hover for the time. |
Downtimes | Number of Downtimes today. |
Dispatches | Dispatches today, with dispatch Utilization in brackets. RideOps only. |
Riders | Riders today, with capacity Utilization in brackets. RideOps only. |
Average Queue Time | Today's average posted queue time, in minutes. RideOps only. |
Operator | The signed-in operator and the number of Attendants, or Operator has not signed in. RideOps only. |
How the figures are calculated
All figures cover today, from midnight in the dashboard's time zone. The Uptime and Downtime percentages compare the two with each other: uptime ÷ (uptime + downtime). Time a Location was simply closed counts as neither. A Downtime without a confirmed duration counts until it was resolved, or until now if it's still active.
This is the same calculation as the Operations tile in the mobile app. The Location Operational History widget calculates differently, so the two can show different percentages. See Uptime, downtime, and lag time explained.
Dispatches, riders and queue times are the ones recorded in RideOps. Ride data sent in by an integration isn't included here; use a RideOps widget with Source set to External for that.
Filter the Operational Overview
The widget has one filter, Locations: choose Locations or Location Groups. With nothing selected, it shows every Location with Operational Logging that you have access to — see How access works in Mobaro. You can also give the widget a custom title.
There's no time range, metric or refresh setting: the widget always shows today and the same figures. It reloads with the dashboard every 10 minutes and whenever you change the filter. See How to use the Dashboard.
Best practices
Give each area supervisor a filter with their own Location Group, so the widget only shows the rides they run.
Check the operator line at opening to catch rides nobody has signed in to.
Close resolved Downtimes promptly in the Backend so the downtime percentages reflect the confirmed durations.
Show the widget in full-screen mode on a control-room screen during peak hours.
Frequently asked questions
How often does the dashboard refresh?
Every 10 minutes, and whenever you change the filter. The Operational Overview has no real-time or refresh setting of its own. Reload the page to update sooner. See How to use the Dashboard.
How do I get a widget with uptime, downtime and lag time?
The Operational Overview shows today's uptime and downtime, but not lag time. For uptime, downtime and lag time over a period, use the Location Operational History widget. See Uptime, downtime, and lag time explained.
Why does the widget show a high downtime for a ride that's running?
The percentages cover the whole of today. A Downtime without a confirmed duration counts until it was resolved, or until now if it's still active. Resolve and close old Downtimes in the Backend, and check their durations.
Why is a location missing from the widget?
The widget only shows Locations with Enable Operational Logging that you have access to and that match its Locations filter. Ride figures only show for Locations with RideOps. See Utilizing Operational Logging.