Operational Logging tracks the Uptime and Downtime of your Locations, giving you accurate operational hours to monitor performance, spot recurring issues, and prove availability. Enable it per Location, then log, correct, and review operation from the Mobaro Backend or the mobile app.
You'll need to be a Super User or have an Operations Role with Manage Downtime, Manage Queue Entries, and Manage Dispatch Entries to modify a Location's operational log.
How operational status works
Operational Logging surfaces two related things about a Location: whether it's allowed to open, and what state it's in right now.
Ready for operation vs. not ready
A Location enabled for Operational Logging always holds one of two readiness states, shown on the Locations page and in the Location Overview on both the backend and the mobile app:
Readiness | Meaning |
Ready for operation | Meets all criteria and can be opened. |
Not ready for operation | Doesn't meet the criteria and can't be opened. |
A Location becomes Ready for operation once all Critical for Operation items are satisfied, at minimum any Checklists marked Critical for Operation.
Note: Each Organization is configured for its own compliance standards. High Priority Assignments, Blocking Downtimes, Checklists awaiting validation, and other criteria can be set to affect readiness. For your Organization's exact setup, check with your main point of contact or contact Mobaro Support.
Operational status
While a Location is enabled, its live status is shown by color:
Status | Meaning |
In operation | Running normally, no open issues. |
Open downtime | A temporary interruption that can be resolved without a blocking Assignment. |
Blocking downtime | A downtime with an associated Assignment that must be resolved before operation continues. |
Not in operation | The Location is closed and not currently operating. |
Enable Operational Logging
By default, Locations aren't enabled for Downtime or operational-hours registration. To turn it on, go to Locations, select the relevant Locations, and click Edit. Set Operational logging of Locations to Enable, then click Update selected values.
Each enabled Location now shows the open/close toggle, so you can mark it in or out of operation and register Downtime.
Note: Toggling a Location open relies on its status being Ready for operation. A Location that is Not ready for operation can't be toggled open.
Note: Enabling Operational Logging gives every User with access to that Location visibility through the Operations tile in the mobile app.
Edit the operational log
Fix mistakes or backfill missing periods from a Location's Uptime Summary.
Correct a logging mistake
Go to Locations, select the Location, and click View Uptime Summary. Select the incorrect log, click Edit Period, apply your changes, and click Save.
Add a downtime to an existing uptime period
In View Uptime Summary, select the affected Uptime Period, then click Add downtime for this period. Add the details, optionally creating a related Assignment, and click Add.
Warning: Adding a downtime with an Assignment to a historical period opens a new High Priority Assignment that can change the Location's current status to Not ready for operation, depending on your Organization's setup.
Create an uptime period
In View Uptime Summary, click Create Period, set a start and end time, and click Save.
Note: Uptime periods can't overlap.
Where you'll see operational status
Operational status appears in two places.
Mobaro Backend — the Operational Status Box on each enabled Location in the Location Overview widget.
Mobile app — the Operations tile, for any User with access to the Location's operational log.
Integrating with the Mobaro API
Operational Logging data is available through the Mobaro API, so you can sync it with ERP, BI, and other systems. For current endpoints, authentication, and examples, see the Mobaro API reference.
Frequently asked questions
Who can manage a Location's operational log?
Super Users, or Users with an Operations Role that includes Manage Downtime, Manage Queue Entries, and Manage Dispatch Entries.
Why can't I toggle a Location open?
A Location can only open when it's Ready for operation. If it's Not ready, an unresolved Critical for Operation item is blocking it, most often a Checklist marked Critical for Operation, or a Blocking Downtime or High Priority Assignment, depending on your setup.
What's the difference between Open downtime and Blocking downtime?
An Open downtime is a temporary interruption you can resolve directly. A Blocking downtime has an associated Assignment that must be resolved before operation continues, and it can mark the Location Not ready for operation.
Can uptime periods overlap?
No. Each uptime period must sit in its own time range.
Does adding a historical downtime affect the current status?
It can. If the downtime creates an Assignment, that opens as a High Priority Assignment and may flip the Location to Not ready for operation, depending on your Organization's setup.