Overview
When a Location has opening hours, Mobaro uses them to suggest how much of a Downtime counts: only the time the Location was meant to be open. This article explains when that calculation happens, works through examples, and lists the cases it doesn't cover.
To attach opening hours to a Location, see Add opening hours to a Location.
At a glance |
|
Who can do this | Super Users or a Role with Operations › Manage Downtime, plus access to the Location |
Where | Downtime › Close Downtime (Estimated Downtime and Actual Downtime) |
Works on | Backend (web) |
Availability | All organizations. The Location needs an opening-hours Calendar and a time zone. |
💡 Why this matters: Downtime percentage and MTTR are only meaningful if Downtime is measured against the time a ride was meant to run. Without opening hours, a fault logged after closing counts as much as one at peak time, and uptime looks worse than it was.
How the calculation works
A Downtime has no duration until someone closes it in the Backend. When you click Close Downtime, Mobaro calculates the Estimated Downtime:
It takes the time from when the Downtime started to when it was resolved, or to now if it isn't resolved yet.
It keeps only the parts that fall inside the Location's opening hours, read in the Location's time zone, and rounds up to whole minutes.
Without an opening-hours Calendar, it keeps the full elapsed time.
The estimate is pre-filled as the Actual Downtime. You can accept it or change it. What you save when you close becomes the Downtime's duration, which Dashboards use for MTTR and Downtime totals.
Example: a single day
A Location's opening hours are 10 AM–6 PM. A ride goes down at 4 PM and the Downtime is resolved at 8 PM.
The Estimated Downtime is 2 hours (4 PM–6 PM). The 6 PM–8 PM period falls outside opening hours, so it isn't suggested.
Example: several days
When a Downtime spans several days, each day's opening hours are checked separately. With opening hours of 10 AM–6 PM every day and a ride down from Friday 4 PM until Sunday 10 AM:
Friday: 2 hours (4 PM–6 PM).
Saturday: 8 hours (the full opening hours).
Sunday: 0 hours (resolved at opening time).
The Estimated Downtime is 10 hours.
When opening hours aren't applied
Opening hours only shape the suggestion in the Close Downtime dialog and the recalculation described below. They don't trim:
a Downtime added to a past uptime period with Add downtime for this period: its duration is Ends at minus Starts at;
a Downtime closed through the Public API: it keeps the duration the integration sends, or none;
an Actual Downtime you typed yourself.
⚠️ Heads-up: Changing a Location's opening hours or time zone doesn't update Downtimes that are already closed. Recalculate them one by one, as described below.
Recalculate a closed Downtime
In the Downtime list, select the closed Downtime and click Edit Downtime. Click the pencil next to Duration to open Update downtime duration. If the stored duration differs from the opening-hours calculation, Mobaro shows the calculated value; click Use calculated downtime duration to apply it, or click Enable editing downtime duration to type your own. Click Save changes.
Best practices
Check the Estimated Downtime against what happened before you close each Downtime.
Set opening hours and the time zone before the season starts, so Downtimes are closed with the right suggestion from day one.
For formulas such as Nominal Operational Hours and Downtime percentage, see How Mobaro calculates Downtime registrations.
Frequently asked questions
My downtime shows 0 minutes after I closed it. Why?
The duration saved at close was 0. That happens when the whole Downtime fell outside the Location's opening hours, often because of a wrong Calendar or time zone. Missing opening hours don't cause it; then the full time is suggested. Fix it with Update downtime duration.
Why does a downtime show no duration before it's closed?
A Downtime only gets a duration when it's closed in the Backend. Until then, Dashboards treat it differently per widget. See Using downtime in Mobaro.
If we close a ride early in RideOps with Close ride, does that count as downtime?
No, not when you close it with Set status as closed: that only ends the uptime period. A Downtime is recorded only when the ride is set down (Set status as down) or a Downtime is started elsewhere.
Can I leave a downtime open for several days while the ride is closed?
Yes. When you close it, the Estimated Downtime counts only each day's opening hours, so nights and closed days aren't suggested. Check the value before you confirm it.