Overview
Mobaro surfaces Location-level downtime two ways on Dashboards: a color-coded bottom bar on each Location card in the Location Overview Dashboard widget, and the Location MTTR/MTBF widget for reliability metrics over time. Together they let an operations team see at a glance whether each Location is currently operable, whether a downtime is open or resolved, and whether there's a longer-term reliability trend worth investigating.
The mental model: Each Location card has two indicators stacked. The header indicator uses the standard red/amber/green pattern from Checklist Result scoring. The bottom bar reflects downtime + operational state, which is a separate signal — they're independent and answer different questions.
The five color states on the Location Overview bottom bar
Each Location card in the Location Overview Dashboard widget has a colored bar at the bottom that combines two pieces of information: whether the Location is currently in operation or out of operation, and whether there are any downtime registrations attached. Five distinct states cover every combination.
Grey — out of operation, no downtimes
Location is marked out of operation and has no active downtime registrations. Typical for closed or off-season Locations. There are no planned activites (Checklists or Assignments) during the defined time period for the Location Overview widget. Can be marked back to operational at any time without action.
Green — in operation, no downtimes
Location is operating and has no active downtime registrations. The healthy default state for a running Location.
Green stripe with Grey box — out of operation, ready for operation but not open
Location is out of operation but is ready for operation and is ready to be opened. This is the signal: "the work is done, somebody just needs to open it."
Yellow — non-blocking downtime open
Location has an open downtime registration that doesn't block operation. Sometimes called a "non-blocking downtime" — the Location can be marked operational without resolving the downtime first. Useful for tracking minor issues that don't justify a related assignment such as weather conditions.
Red — out of operation, blocking downtime open
Location has a blocking downtime registration that needs to be resolved before operation resumes. Typically paired with a blocking Assignment created when the downtime was registered (either by the Location's automatic configuration or manually by administrative staff).
Note: The bottom-bar indicator is independent of the header red/amber/green that comes from Checklist Result scoring. A Location can have a green header (latest Checklist passed cleanly) and a red bottom bar (a blocking downtime is open) — they answer different questions.
The Location MTTR/MTBF widget
The Location MTTR MTBF widget turns downtime registrations into reliability metrics over a chosen time period. Both metrics depend on operational hours and downtime data being logged consistently — without that data, the widget has nothing to compute from.
MTTR — mean time to repair. The average elapsed time from when a downtime is registered to when the Location is back in operation. Measured in fractional hours on the widget (e.g., 0.75 = 45 minutes). Click into the widget for exact minute-level numbers per Location.
MTBF — mean time between failures. The average operational hours between downtime registrations. Higher is better — a Location with a high MTBF is going long stretches without breaking. Measured in operational hours, not wall-clock hours.
The widget supports filtering by all Locations, a Location Group, a single Location, time period, and Categories. For deeper coverage of how to read these metrics and what to do with them, see the MTTR and MTBF — Mobaro's reliability metrics companion article.
Worked examples
Example 1: Morning ride status check
Scenario: A Park Director glances at the Location Overview Dashboard at 9am to see which rides are ready for opening.
Setup: Location Overview Dashboard widget configured for the park's full ride list.
Result: At a glance: green = ready, grey = scheduled closed, red = blocked (needs attention before opening). Yellow rides are operating with a known minor issue logged. The Director can prioritize the morning huddle around the red Locations without scrolling through individual records.
Example 2: Afternoon downtime closeout
Scenario: After a maintenance team finishes work on a closed ride, the Operations Manager needs to know which downtimes are awaiting administrative closure.
Setup: Location Overview Dashboard, scoped to the relevant area.
Result: Locations with grey stripes are the queue — the Manager closes each downtime registration in turn and the Locations transition back to grey (out of operation, ready) or green (returned to operation).
See also
MTTR and MTBF — Mobaro's reliability metrics — deeper treatment of the reliability metrics, how to interpret them, and operational examples.
Downtime registration overview — for the lifecycle of a downtime from creation to closure (blocking vs non-blocking, who can register, who can resolve).
Dashboards overview — for general Dashboard widget configuration.
Frequently asked questions
Q: Why does my Location show green on the bottom bar but red on the header?
A: The two indicators are independent. The header reflects the latest Checklist Result scoring (red/amber/green from compliance scores). The bottom bar reflects operational state + downtime. A passing Checklist Result with no open downtimes gives you green/green; a passing Checklist with an open blocking downtime gives you green header + red bottom bar.
Q: Can I configure custom colors for the bottom bar?
A: No — the five states and their colors are fixed by Mobaro to keep the meaning consistent across organizations and Users. The intent is that any operator can read the indicator the same way regardless of which park they're at.
Q: What's the difference between blocking and non-blocking downtime?
A: Blocking downtime forces the Location out of operation until resolved (red); non-blocking downtime tracks an issue without forcing closure (yellow). Blocking is the right choice when an issue makes operation unsafe or out-of-spec; non-blocking is for tracking minor matters that need a record but not action.
Q: How is operational hours calculated for MTBF?
A: From the Location's operational state — the time the Location is marked "in operation." Closed periods don't count toward MTBF. This is intentional: MTBF measures reliability while running, not wall-clock time.
Q: I want a Dashboard for just the resolved-pending state. How?
A: The Location Overview widget shows all states together. To isolate "Locations needing administrative closeout," use a filter on downtime status or build a Dashboard from the downtime listing rather than the Location Overview.