Overview
The Location Jack Knife widget is a bubble chart with one bubble per Location: MTBF across, MTTR up, and bubble size for the number of Downtimes. It answers "which rides break down often and take long to fix?" On the dashboard its default title is Jack Knife showing (MTBF, MTTR, Downtime count).
It uses the same figures as the MTTR MTBF Details 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 › Location Jack Knife |
Works on | Backend (web) |
Availability | All organizations. Uptime and Downtimes are recorded for Locations with Enable Operational Logging. |
What it shows
Part of the chart | What it shows |
Horizontal axis | MTBF hour(s): uptime in the period divided by the number of Downtimes. The axis is reversed: high MTBF on the left, 0 on the right. |
Vertical axis | MTTR hour(s): total recorded Downtime duration divided by the number of Downtimes. |
Bubble size | The number of Downtimes that started in the period. |
Red bands | With thresholds set: MTBF below its threshold (right) and MTTR above its threshold (top). |
The least reliable Locations, which break down often and take long to fix, sit in the top-right corner, inside both red bands. Each bubble is labelled with the Location's name. Only Locations with at least one Downtime that started in the period and some ended uptime are plotted, because the others have no MTBF.
Downtimes count whatever their state; deleted ones don't. Uptime comes from uptime periods that have ended, cut to the period.
⚠️ 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 |
Chart Options (palette button) | Opens General Options and Chart Thresholds. Click Save to apply. | - |
Use logarithmic axes | In General Options, or with its own button on the widget. Spreads out Locations when values differ a lot. | Off |
MTBF hour(s) threshold | In Chart Thresholds: tick it and enter hours to shade MTBF below that value red. A value is required while ticked. | Off |
MTTR hour(s) threshold | In Chart Thresholds: tick it and enter hours to shade MTTR above that value red. A value is required while ticked. | Off |
Title | Click the widget's title to rename it; the cross resets it. | Jack Knife showing (MTBF, MTTR, Downtime count) |
Example: with an MTBF hour(s) threshold of 50 and an MTTR hour(s) threshold of 100, a coaster with a large bubble in the top-right corner breaks down often and takes long to fix, while a ride outside the red bands meets both standards.
Reading the widget
Hover over a bubble to see the Location, its MTBF and MTTR in hours and minutes, and its Downtime Count. Bubbles can't be clicked; for the numbers, use the MTTR MTBF Details widget. With linear axes, both start at 0. When no Location matches the filters, the widget shows No data is available for this widget. Please try changing your filtering.
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
Set thresholds that match your own standards, and review the Locations in the top-right corner first.
Treat large bubbles as recurring problems: many Downtimes in the period.
Turn on logarithmic axes when one ride's figures squash all the others into a corner.
Save the thresholds in a Personal or Organization filter so they stay.
Frequently asked questions
Why is a ride missing from the chart?
Only Locations with at least one Downtime that started in the period, and some uptime that has ended, are plotted. Also check the Locations and Category filters, and that you can see the Location.
Why does the MTBF axis run backwards?
It's reversed on purpose, so the worst Locations (low MTBF, high MTTR) end up together in the top-right corner.
How do I set the red zone?
Click Chart Options, tick MTBF hour(s) and MTTR hour(s) under Chart Thresholds, enter the hours and click Save. Save your dashboard filter to keep them.