Overview
Dashboards show Location Downtime in two places. The Location Overview widget shows each Location's readiness and current operational state, including any active Downtime. The Location MTTR MTBF widget turns recorded Downtimes into reliability metrics over time.
Use them together to see at a glance which Locations can open, which are down right now, and whether a Location's reliability is trending the wrong way.
At a glance |
|
Who can do this | Anyone who can view the Dashboard |
Where | Dashboard › Location Overview and Location MTTR MTBF widgets |
Works on | Backend (web) |
Availability | All organizations. Operational state needs Enable Operational Logging on the Location. |
💡 Why this matters: Each Location card answers two separate questions. The title bar colour says whether the Location can open; the status box says what it's doing right now. Reading them separately stops a red title bar being mistaken for a breakdown, or a closed ride for a ready one.
Title bar colour: readiness
The colour of a Location's title bar shows its readiness. It isn't based on Checklist scores.
Red: Not ready. Critical-for-operation Checklists or critical Assignments are outstanding, as defined by your Header Color settings. A Blocking Downtime also turns it red if Red if a blocking downtime is active on the location is on.
Green: Ready, with Checklists in the widget's time range.
Gray: Ready, with no Checklists in the widget's time range.
There is no amber state. Super Users can click a red Location's name to see what's holding it; your organization can allow everyone to do this. See Configuring readiness colors on the Location Overview.
Operational status box
A small box at the left end of each Location's title bar shows whether the Location is operating and whether it has an active Downtime. Hover over it for a description. It appears only for Locations with Operational Logging. There are four states.
Gray: Out of operation, without active downtimes. The Location is closed, for example outside opening hours or off-season. It can be opened at any time.
Green: In operation, without active downtimes. The Location is open and running normally.
Yellow: Out of operation, with non-blocking downtime. An Open Downtime is active, so the Location is closed. Opening the Location resolves the Downtime; no Assignment has to be finished first.
Red: Out of operation, with blocking downtime. A Blocking Downtime is active. It has an Assignment created from the Downtime, either automatically when it started or by an administrator, and the Location can't be opened until that Assignment is resolved or the Downtime is closed in the Backend.
Click a yellow or red box to go to the Downtime list, filtered to that Location's Open and Blocking Downtimes. Resolved and closed Downtimes don't show in the box.
Reading the two together
A green title bar with a gray box means the Location is ready but not open: the work is done, and somebody just needs to open it.
A red title bar with a green box means the Location is operating while something critical is outstanding, for example a high-priority Assignment created after it opened. A green title bar with a red box is possible when your organization doesn't turn Locations red for Blocking Downtimes.
The Location MTTR MTBF widget
The Location MTTR MTBF widget calculates two reliability metrics for the selected period. You can filter it by time range, Downtime categories, and Locations or Location Groups. Click a value for the details per Location.
MTTR (Mean Time To Repair) is the average recorded duration of the Downtimes that started in the period: their total duration divided by their number. A Downtime's duration is recorded when it's closed in the Backend, where it can be confirmed or edited. The widget shows hours, so 0.75 means 45 minutes.
⚠️ Heads-up: Downtimes that haven't been closed yet have no duration, but they still count in the number of Downtimes. Until you close them, they pull MTTR down. Close resolved Downtimes promptly.
MTBF (Mean Time Between Failures) is the time the Locations were open in the period divided by the number of Downtimes that started in it. Closed time doesn't count, so MTBF measures reliability while running. Higher is better.
For how to interpret and act on these metrics, see MTTR and MTBF — Mobaro's reliability metrics.
Worked examples
Morning ride status check. At 9:00 AM a Park Director opens a Location Overview widget covering every ride. Green title bars with green boxes are running. Green title bars with gray boxes are ready and waiting to be opened. Red title bars are not ready; the Director clicks the names to see what's outstanding. Yellow and red boxes are down, and a click on the box opens their Downtimes.
Monthly reliability review. Before the review, the Operations Manager closes the month's resolved Downtimes in the Downtime list, confirming each duration. They then filter the Location MTTR MTBF widget to the Mechanical category for last month to compare rides.
Best practices
Read the title bar and the status box separately: one is readiness, the other is operational state.
Close resolved Downtimes promptly, and check their durations, so MTTR reflects reality.
Use Downtime categories consistently so the MTTR MTBF category filter is meaningful.
Record opening and closing reliably; MTBF depends on accurate uptime.
Frequently asked questions
Why does my location show gray on the Location Overview?
A gray title bar means the Location is ready but has no Checklists in the widget's time range. A gray status box means it's closed with no active Downtime. Neither is an error.
Why is my location still red when the downtime is resolved?
The title bar shows readiness, not Downtime. It stays red while critical Checklists or Assignments are outstanding. The status box shows the Downtime. Super Users can click the Location's name to see what's holding it red.
What does MTTR mean, and why isn't my downtime counted in it?
MTTR is Mean Time To Repair: the average recorded duration of Downtimes that started in the period. A Downtime only gets a duration when it's closed in the Backend, so close it to have it counted properly.
What's the difference between open, blocking, resolved and closed downtime?
Open and Blocking are active; Blocking has a related Assignment that must be resolved before the Location can open. Resolved means the Location was reopened or the Assignment resolved. Closed means an administrator finalised it and its duration in the Backend.
How can I see which rides are down right now?
Look for yellow and red status boxes in the Location Overview widget. Click one to open the Downtime list for that Location's active Downtimes.