Overview
Opening hours tell Mobaro when a Location is meant to be open. You set them by picking a Calendar in the Location's Opening Hours field, together with the Location's Time zone.
Their main job is Downtime: when you close a Downtime, Mobaro suggests a duration that only counts time inside opening hours. RideOps and some Backend views use them too. This article covers what opening hours affect and how to set them up. For the Downtime calculation and worked examples, see How opening hours affect downtime tracking.
At a glance |
|
Who can do this | Super Users, the Location's creator, or a Role with Locations › Modify. Creating the Calendar needs Schedules › Create. |
Where | Locations › a Location › Edit › General Information › Time zone and Opening Hours |
Works on | Backend (web). Also used by RideOps. |
Availability | All organizations |
💡 Why this matters: Without opening hours, a Downtime that runs overnight or starts before opening suggests every elapsed minute as Downtime. With opening hours, the suggested duration covers only the time the ride was meant to be running.
Opening hours vs Schedules
Mobaro uses one kind of Calendar, but what a Calendar does depends on where you attach it:
Attached to | What it controls |
A Schedule of type Calendar | When a Checklist is available to complete |
A Location's Opening Hours | When the Location is meant to be open. It doesn't schedule Checklists. |
A Checklist's availability window and a ride's open-to-close hours are rarely the same, so create a dedicated Calendar for opening hours.
What opening hours affect
Downtime duration: the Estimated Downtime suggested when you close a Downtime, and the Use calculated downtime duration option when you edit a closed one.
RideOps: the day's opening and closing times on the tablet, and the closing reminder when Enable closing time reminder is on in the Location's RideOps settings.
Operational Log: the planned RideOps preopening and closing Checklists for each day.
Ride Operations Timeline widget: the Filter by Opening Hours option — see Ride Operations Timeline Widget.
Opening hours don't open or close a Location, don't change whether it's Ready for operation, and don't schedule or check Checklists. If the Calendar says a Location is open on a day it isn't, nothing is flagged; only the uses listed above are affected for that day.
Create the Calendar
Create the opening-hours Calendar under Schedules › Calendars before you attach it, with patterns for your opening days and hours. See Creating a master Calendar.
Add opening hours to a Location
1. Open the Location editor
In the Backend, go to Locations, select the Location and click Edit.
2. Pick the Calendar
In General Information, click the Opening Hours field (Add calendar) and select the Calendar. A Location can have one opening-hours Calendar.
3. Set the time zone
Choose the Time zone the Location's hours are in. It becomes required once you've picked a Calendar.
4. Save
Save the Location. Mobaro uses the Calendar and time zone from now on, including when you close Downtimes that started earlier.
🛑 Critical: A wrong time zone shifts the opening hours by the offset. Suggested Downtime durations then count out-of-hours time and drop in-hours time, and RideOps shows the wrong opening and closing times. Always check the time zone matches where the Location is.
How this affects Downtime
When you close a Downtime in the Backend, the Estimated Downtime counts only the time between start and resolve that falls inside opening hours. It's pre-filled as the Actual Downtime, and you can change it before you close. Without an opening-hours Calendar, the estimate is the full elapsed time.
⚠️ Heads-up: Opening hours are applied only through that suggestion. A Downtime added to a past period with Add downtime for this period stores Ends at minus Starts at, and a Downtime closed through the Public API stores the duration the integration sends. Neither is trimmed. See How opening hours affect downtime tracking.
Best practices
Create a dedicated Calendar for opening hours rather than reusing a Checklist scheduling Calendar.
Set the time zone every time you attach a Calendar.
Review the Calendar when park or seasonal hours change.
Use consistent opening hours across Locations so Downtime comparisons on Dashboards stay meaningful.
Frequently asked questions
What is the Location "Opening Hours" calendar used for?
Mainly for Downtime: when you close a Downtime, Mobaro suggests a duration that counts only time inside opening hours. RideOps also uses it for the day's opening and closing times and the closing reminder. It doesn't schedule Checklists.
Will a location open and close automatically if I set a calendar for it?
No. Opening hours never open or close a Location. Someone opens and closes it in the Mobaro app, RideOps or the Backend, or an integration does it through the Public API.
Our opening hours change during the season. When the pattern expires, do I edit it or make a new calendar?
Edit the same Calendar under Schedules › Calendars and add or extend patterns for the new dates. The Location keeps using that Calendar, so you don't need to attach it again.
Can I add opening hours to many locations at once?
No. Edit multiple locations only changes Operational Logging, language and radius. Set Opening Hours and Time zone in each Location's editor. Several Locations can share the same Calendar.