Overview
Operating hours define when a location is considered open in Mobaro. When you link a calendar and time zone to a location, Mobaro uses those settings to determine when downtime and uptime count toward your operational metrics.
Without operating hours, downtime is counted across the full day (24 hours). By assigning a calendar and time zone, Mobaro limits downtime and uptime calculations to your defined open hours—ensuring after-hours or overnight closures don’t inflate downtime totals.
Note: The calendars used for operating hours are the same type as those managed under the Schedules section, but you can create separate ones if your operating hours differ from your operational scheduling calendars.
Open the location editor
From the Mobaro backend:
Go to Locations.
Select the location you want to update (e.g., Hurricane).
Click the edit icon to open the Editor panel.
Assigning a calendar and time zone
When configuring a location’s operating hours, you must:
Open Locations → Edit.
Under Opening hours, select a Calendar.
Choose the correct Time zone for that location.
Mobaro uses the selected time zone to interpret all open and closed hours for downtime calculations.
Warning: Assigning an incorrect time zone may result in inaccurate downtime totals, especially for parks operating across different regions.
How downtime is calculated
When downtime is logged for a location with an assigned calendar and time zone:
Downtime inside the operating hours window is counted toward totals.
Downtime outside those hours is ignored.
Uptime is calculated only from the defined open hours of the location.
Mobaro applies these calculations automatically across dashboards, reports, and downtime exports.
Important: Downtime calculations update when the downtime is closed, not immediately when created. Before closing, a downtime may appear longer since it temporarily includes periods outside operating hours. Once closed, Mobaro recalculates the actual in-hours duration.
How operating hours affect downtime tracking
Once a calendar is assigned to a location, Mobaro uses the defined operating hours to determine when a location is considered active versus closed. This directly influences how downtime and uptime are measured.
Downtime refers to periods where a location or asset is unavailable during hours it should be operating.
Uptime is the total available time the location is operational within its scheduled hours.
Key behaviors
Downtime and uptime are only calculated during active operating hours defined by the linked calendar.
Any downtime outside of these hours is excluded from downtime totals.
If a downtime begins before or extends past the defined operating hours, only the in-range portions count toward downtime.
When viewing metrics across reports, dashboards, or the downtime overview, these calculations automatically respect each location’s linked calendar.
Example:
If your operating hours are 10 AM–6 PM and a downtime begins at 4 PM, then ends at 8 PM, Mobaro will only count 2 hours of downtime (4–6 PM).
The period after 6 PM is excluded, since it falls outside the defined operating hours.
Tip: This ensures overnight closures or maintenance outside guest-facing hours don’t artificially inflate downtime statistics.
Multi-day downtimes
When a downtime spans multiple days:
Mobaro checks each calendar day’s operating window and counts only the hours that fall within those active periods.
The downtime is segmented internally per day to ensure accurate tracking.
Example:
If a ride is down from Friday at 4 PM through Sunday at 10 AM, and your operating hours are 10 AM–6 PM daily:
Friday downtime = 2 hours (4 PM–6 PM)
Saturday downtime = 8 hours (10 AM–6 PM)
Sunday downtime = 0 hours (since it was resolved before opening)
How this affects dashboards and reports
All downtime-related data in Mobaro—Downtime Overview, Reports, Dashboards, and Exports—automatically respects the calendar and time zone linked to each location.
This ensures that:
Downtime totals only include time within operating hours.
Uptime percentages are based on available operating hours, not full days.
Metrics across parks in different time zones remain accurate and comparable.
Recommendation: Always confirm each location’s assigned calendar and time zone before reviewing downtime or uptime metrics.
Frequently asked questions
Q: Can I assign multiple calendars to a location?
A: No. Each location can only have one calendar assigned for operating hours.
Q: What happens if I forget to set the time zone?
A: Mobaro cannot correctly calculate downtime or uptime. Always select the correct time zone when assigning a calendar.
Q: Why does downtime appear longer before closing?
A: Downtime duration updates when the event is closed. Before closing, the timer includes all elapsed time, even outside operating hours.
Q: Can I use the same calendar for both schedules and operating hours?
A: Yes, but if a schedule's available hours differ from guest-facing hours, it’s best to use separate calendars.
Q: What happens if a downtime overlaps opening or closing times?
A: Only the portion within defined operating hours counts. Time before or after those hours is ignored once the downtime is closed.