Overview
The Operational History Details widget is a table with one row per Location: its Uptime, Downtime, number of Downtimes and Lagtime for the period you choose. On the dashboard its default title is Details of the operational history.
Use it to compare rides side by side and find the ones losing the most time. For totals across all Locations, use the Location Operational History widget. 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 History Details widget (category Operational in the widget list) |
Works on | Backend (web) |
Availability | All organizations. Locations need Enable Operational Logging. |
💡 Why this matters: Park-wide totals can hide the one ride that drags the numbers down. A per-Location table sorted by downtime shows which rides to look at first.
Read the table
Column | What it shows |
Location | The Location's name |
Uptime | Share of the Location's uptime + downtime + lag time that it was open, with the time underneath |
Downtime | Share lost to closed Downtimes, with their confirmed duration underneath |
Downtimes | Number of closed Downtimes that started in the period |
Lagtime | Share and time the Location stayed closed after a Downtime, beyond its duration, up to the threshold. Only shown while a Lagtime Threshold is set. |
A dash (-) means zero. Uptime comes from uptime periods that have ended, cut to the period; a Downtime counts with its full confirmed duration if it started in the period. Time a Location was simply closed counts as neither. For the definitions, see Uptime, downtime, and lag time explained.
Click a column header to sort, for example Downtime to put the worst ride first; click again to reverse. The table is sorted by Location name by default. Choose 10, 20, 30, 40 or 50 items per page at the bottom and use the arrows to page. The sort and page size are saved with the dashboard filter.
⚠️ Heads-up: Only closed Downtimes count, and uptime only counts once the uptime period has ended. A Downtime that's Open, Blocking or Resolved but not yet closed, or a ride that's open right now, isn't in the figures yet. Resolving a Downtime isn't enough: close it in the Backend to include it.
Filter the widget
Use the buttons at the top of the widget. Filters combine, and you can also give the widget a custom title.
Time range: the button at the top left shows the current period — Last 12 months by default. Choose Today, Yesterday, Last week, Current week, Current month, Last a number of Days, Weeks or Months, Specific month or Custom Time Range. There is no All Time option.
Category: one or more Downtime Categories; only shown if your organization has Downtime Categories. It narrows the Downtime count and duration only. Uptime and lag time aren't filtered by category, so the percentages change too.
Locations: Locations or Location Groups. With nothing selected, the widget covers every Location you can see.
Lagtime Threshold: enter Lagtime Threshold (in minutes) and click Apply Filter; 300 minutes by default. All lagtimes with a longer duration are excluded, such as a ride that stayed closed overnight after a Downtime. Clear the threshold with the bin icon to leave lag time out altogether.
Access and refresh
The table lists every Location with Operational Logging that you can see and that matches the Locations filter, even if nothing happened there in the period. Other Locations are listed only if they have Downtimes in the period. Super Users and Users with Locations › View see all Locations; other Users see the Locations they're a member of, directly or through a Location Group. Two people can therefore see different numbers on the same dashboard. See How access works in Mobaro.
Times are in the dashboard's time zone. The widget reloads with the dashboard every 10 minutes and whenever you change a filter. Bulk filtering can also change its time range and Locations, and the Location Switcher its Locations. See How to use the Dashboard.
Best practices
Sort by Downtime or Downtimes to find the rides that need attention first.
Keep a Lagtime Threshold set, so overnight closures after a Downtime don't swamp lag time.
Use a Custom Time Range to review a whole season in one table.
Close Downtimes promptly with an accurate duration; open Downtimes don't count.
Frequently asked questions
Can I see downtime per ride?
Yes. Each row is one Location, with its downtime percentage, time and number of Downtimes for the period. Filter Locations to the rides you want. To list the individual Downtimes, click Downtimes on the Location Operational History widget.
How do I sort the table alphabetically?
Click the Location column header; click it again to reverse the order. Alphabetical by Location is the default. Save the filter as a Personal filter to keep your sort — see Dashboard filters — Organization vs Personal.
Can I export the operating hours for each location?
No. The widget has no export. Set a Custom Time Range, such as a season, to see each Location's uptime for it. For a day-by-day export, pull uptime periods through the Public API — see Getting started with the Mobaro API.
Why is the Lagtime column missing?
It only shows while a Lagtime Threshold is set. Open the Lagtime Threshold filter, enter a number of minutes (300 is the default) and click Apply Filter.