Overview
The Location Operational History widget shows four totals for the Locations and period you choose: the number of Downtimes, and the hours of Uptime, Downtime and Lagtime. Click a total to see the Downtimes or the per-Location figures behind it.
Use it to review how reliably your rides ran over a week, a month or a season. 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 › Location Operational History widget (category Operational in the widget list) |
Works on | Backend (web) |
Availability | All organizations. Locations need Enable Operational Logging. |
💡 Why this matters: Downtime hours alone don't tell you whether a ride has a reliability problem or a slow restart. Seeing downtime and lag time side by side over a period shows which one to fix.
What the widget shows
Total | What it counts |
Downtimes | Closed Downtimes that started in the period |
Uptime | Time the Locations were open in the period, from uptime periods that have ended |
Downtime | The confirmed duration of those closed Downtimes |
Lagtime | Extra time Locations stayed closed after a Downtime, beyond its duration, before reopening; up to the Lagtime Threshold. Hidden when there is none. |
Totals show in hours. Click Show as Percentage (the % button) to show uptime, downtime and lag time as shares of uptime + downtime + lag time instead; N/A means there's no recorded time to compare. Time a Location was simply closed counts as neither. For the definitions, and why the mobile app's percentages differ, see Uptime, downtime, and lag time explained.
⚠️ 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.
See the details
Click Downtimes to list those Downtimes, one row each, with Location, State, Description, Created and Duration. Click a column header to sort.
Click Uptime, Downtime or Lagtime to open Uptime and Downtime Details: a table with the figures for each Location, the same as the Operational History Details widget.
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 widget counts every Location with Operational Logging that you can see, plus any other Location with 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
Keep a Lagtime Threshold set, so overnight closures after a Downtime don't swamp lag time.
Close Downtimes promptly with an accurate duration; open Downtimes don't count.
Pair it with the Downtime by Category widget to see why rides went down.
Save a Personal filter per area with that area's Location Group.
Frequently asked questions
How do I see yesterday's downtime for a ride?
Set the time range to Yesterday and Locations to the ride, then click the Downtimes number to list each closed Downtime with its description and duration. For every Downtime, including open ones, use the Downtime list in the Backend — see Using downtime in Mobaro.
How do I show downtime as a percentage?
Click Show as Percentage (the % button) at the top of the widget. Uptime, downtime and lag time then show as shares of uptime + downtime + lag time, not of opening hours. The widget has no bar chart; for each Location's figures, use Operational History Details.
Why don't I see recent downtime on the dashboard?
Only closed Downtimes that started in the widget's period count, and the default period is the last 12 months. Close open or resolved Downtimes in the Backend and check the period. Opening hours don't hide downtime; they only affect the duration Mobaro suggests when you close one.
What's lagtime?
The time a Location stayed closed after a Downtime before someone opened it again, minus the Downtime's duration. Only lag times up to the Lagtime Threshold count. See Uptime, downtime, and lag time explained.
Can I see how long it takes to fix a downtime?
Not here; the widget shows total downtime hours, not an average. For mean time to repair, use the Location MTTR MTBF widget — see MTTR and MTBF.