Overview
Operational Logging records when each Location is open, closed and down. It gives you accurate uptime and Downtime figures to monitor performance, spot recurring issues and prove availability.
This article covers turning Operational Logging on, reading a Location's readiness and operational status, opening and closing Locations in the Backend, and correcting the record in the Uptime Summary. For setting up Downtime as a whole, see How to Get Started with Downtime in Mobaro.
At a glance |
|
Who can do this | Enable: Super Users, the Location's creator, or Locations › Modify. Open and close: anyone who can see the Location, unless limited to set User Groups. Correct the Uptime Summary: Operations › Manage Downtime or Super User. |
Where | Locations (Edit, Toggle Operational Status, View Uptime Summary) |
Works on | Backend (web), Mobile app, RideOps, Public API |
Availability | All organizations |
Enable Operational Logging
Locations don't record operation until you turn it on. For several Locations, open Locations, click Toggle Multiselect, select them and click Edit. Set operational logging of locations to Enable, click Update selected values, then Confirm. For one Location, tick Enable Operational Logging in the Operations panel of its editor.
Enabled Locations get a readiness label and an open/close toggle on the Locations list, and appear in the Operations tile of the Mobaro app for Users who can open and close them.
🛑 Critical: Turning Operational Logging off also turns RideOps off for that Location and closes the Location if it's open. Turn it off only for Locations you no longer want to track.
Readiness
Each enabled Location is either Ready for operation or Not ready for operation. It's Not ready while a Checklist that is critical for operation is outstanding, or while something your organization counts as critical is open. Administrators choose what counts under Configuration › Location Overview › Header Color:
Red if one or more checklists are missing
Red if one or more active high priority assignments exist
Red if one or more active overdue assignments exist
Red if a blocking downtime is active on the location
Color is only affected by approved results
See Configuring readiness colors on the Location Overview and Schedule criticality and Location operational status.
Operational status
Separately from readiness, each enabled Location has an operational status. On the Location Overview widget it shows as a coloured box:
Colour | Meaning |
Gray | Out of operation, without active downtimes |
Green | In operation, without active downtimes |
Yellow | Out of operation, with non-blocking downtime |
Red | Out of operation, with blocking downtime |
For how the two combine, see Downtime on Dashboards. In the Mobaro app, the same status shows in the Operations tile — see Managing Downtime and uptime from the mobile app.
Open and close Locations in the Backend
On the Locations list, use the Toggle Operational Status switch on a Location's row. The switch is disabled while the Location is Not ready for operation, has a Blocking Downtime, or you aren't allowed to change its state. Opening a Location resolves any Open Downtime.
To change several at once, select them and click Open Location(s) or Close Location(s). Bulk opening skips Locations that are Not ready, have a Blocking Downtime or have a RideOps preopening Checklist.
Correct the operational log
Fix mistakes and fill gaps in the Uptime Summary: go to Locations, select one Location and click View Uptime Summary. Edit, add a downtime to and delete work only on closed uptime periods.
1. Correct an uptime period
Select the period, click Edit Period, change the times and click Save. To remove a period recorded by mistake, click Delete Period.
2. Add a missed downtime
Select the closed uptime period during which the Location went down; it must not already have a Downtime. Click Add downtime for this period, set Starts at and Ends at, add a description, and click Add. Mobaro closes the uptime period at Starts at, starts a new one at Ends at, and saves the Downtime as closed. Its duration is Ends at minus Starts at, not trimmed to opening hours.
🛑 Critical: If you tick Create Assignment while adding a past Downtime, Mobaro creates a new high-priority Assignment now. If Red if one or more active high priority assignments exist is on, the Location becomes Not ready for operation until the Assignment is resolved.
3. Create a missing uptime period
Click Create Period, set the start and end, and click Save. If the period overlaps existing ones, they're listed under Overlapping uptimes and Save stays disabled until you fix the times.
For more on the Uptime Summary, see Reviewing downtime on the Locations page. To see and edit RideOps entries such as dispatches and queue times, use View Operational Log — see Log book on the web — the Operational Log dialog.
Use the Mobaro API
Downtimes, uptime periods and opening and closing Locations are available through the Mobaro Public API (your organization needs Public API access), so you can sync them with ERP, BI and other systems. See Getting started with the Mobaro API.
Best practices
Open and close Locations as they actually start and stop, so uptime is accurate without later correction.
Correct mistakes the same day in the Uptime Summary, while people still remember what happened.
Leave Create Assignment unticked when you backfill a Downtime that has already been fixed.
Frequently asked questions
Why can't I toggle a location open?
The switch is disabled while the Location is Not ready for operation, has a Blocking Downtime, or you're not in the User Groups in Limit location operational state management to (user groups). Downtime, queue and dispatch permissions don't affect it. See Troubleshooting red statuses in location overviews.
Can I add a downtime retroactively?
Yes, in the Uptime Summary with Add downtime for this period, on a closed uptime period that has no Downtime yet. If the Location was never opened that day, create the uptime period first with Create Period.
My location shows out of operation for 10 minutes when it was running. Can I fix that?
Yes. In the Uptime Summary, select the closed uptime period next to the gap, click Edit Period and correct its times. Use Delete Period to remove a period recorded by mistake. The period that's still open can't be edited until the Location is closed.
Is there a way to delete everything in the operational log at once?
No. In the Uptime Summary you delete uptime periods one at a time with Delete Period.
How can I see the operational hours for each location over a season?
Add the Operational History Details widget to a Dashboard and set its time range; it shows uptime and Downtime per Location. See Operational History Details Widget. You can also pull uptime periods through the Public API.