Overview
The MTTR MTBF Details widget is a table with one row per Location: its uptime, downtime, number of Downtimes, MTTR and MTBF for the period you choose. It answers "which rides drive our MTTR and MTBF?" On the dashboard its default title is MTTR (Mean Time To Repair) MTBF (Mean Time Between Failure) Details.
For the combined figures, use the Location MTTR MTBF widget; for a chart, the Location Jack Knife widget. What the metrics mean: MTTR and MTBF — Mobaro's reliability metrics.
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 › MTTR MTBF Details |
Works on | Backend (web) |
Availability | All organizations. Uptime and Downtimes are recorded for Locations with Enable Operational Logging. |
What it shows
Column | What it shows |
Location | The Location's name |
Uptime | Time the Location was open in the period, from uptime periods that have ended, cut to the period |
Downtime | Total recorded duration of the Downtimes that started in the period |
Downtime Count | Number of Downtimes that started in the period, whatever their state |
MTTR | Downtime divided by Downtime Count |
MTBF | Uptime divided by Downtime Count |
Times show in hours and minutes, such as 2 hour(s), 15 minute(s). A dash (-) means zero, or that there's nothing to calculate because no Downtime started in the period. A Downtime's duration is the Actual Downtime confirmed when it's closed; deleted Downtimes don't count.
The table lists every Location you can see that has Operational Logging and matches the Locations filter, even if nothing happened there, plus any other Location with uptime or Downtimes in the period. The Category filter changes the figures, not which rows appear.
⚠️ Heads-up: Downtimes that aren't closed yet have no duration but still count, so they pull MTTR down. Uptime only counts once an uptime period has ended: a Location that's open right now adds none of its current opening to MTBF (known issue). Close Downtimes promptly, and report on periods that have ended.
Settings and filters
Setting | What it does | Default |
Time range (button at the top left) | The period. A Downtime counts in the period it started. Options: Today, Yesterday, Last week, Current week, Current month, Last a number of Days, Weeks or Months, Specific month or Custom Time Range. No All Time. | Last 12 months |
Category | Count only Downtimes with the selected Downtime Categories; only shown if your organization has them. Uptime isn't filtered, so MTBF becomes time between failures of that kind. Known issue: a Downtime with more than one of the selected categories is currently counted once for each. | None: all Downtimes |
Locations | Pick Locations or Location Groups and click Apply Filter. The bin icon clears the selection. | None: every Location you can see |
Sort | Click a column header to sort by it; click again to reverse. The sort is saved with the dashboard filter. | By Location, A to Z |
Title | Click the widget's title to rename it; the cross resets it. | MTTR (Mean Time To Repair) MTBF (Mean Time Between Failure) Details |
Reading the widget
All rows show in one table, with no paging, and rows can't be clicked. When no Location matches, the widget shows No data is available for this widget. Please try changing your filtering. The combined MTTR on the Location MTTR MTBF widget isn't the average of the rows' MTTR: it divides all the downtime by all the Downtimes.
Super Users and Users with Locations › View see every Location; other Users see the Locations they're a member of, directly or through a User Group or Location Group. Two people can therefore see different figures on the same dashboard. 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
Sort by MTTR or Downtime Count to find the rides to look at first.
Read Downtime Count next to MTTR: an average from one or two Downtimes is noisy.
Report on periods that have ended, so open Downtimes and open uptime periods don't skew the figures.
Save a Personal filter per area with that area's Location Group.
Frequently asked questions
Which ride has the longest repair times?
Click the MTTR column header, then click it again to put the highest first. Check Downtime Count too: one long Downtime can make a ride look worse than it is.
Why does a ride show a dash for MTTR and MTBF?
No Downtime started at that Location in the period, so there's nothing to divide by. Check the time range and the Category filter.
Why is a ride missing from the table?
It's outside the Locations filter, it's deleted, you can't see it, or it has no Operational Logging and no uptime or Downtimes in the period.
Can I export the table?
No. The widget has no export. For your own analysis, pull Downtimes and uptime periods through the Public API. See Getting started with the Mobaro API.