Overview
Operational Logging is crucial for tracking the Uptime and Downtime of Locations in Mobaro. It provides accurate data on operational hours, helping organizations monitor performance, identify issues, and improve efficiency.
Users must be Super Users or have the following Role to modify a Location's Operational Log:
Operations: Manage Downtime, Manage Dispatch Entries, and Manage Queue Entries
Enabling Operational Logging for Locations
By default, Locations are not enabled for the registration of Downtime or Operational Hours. Follow these steps to enable Operational Logging:
Navigate to Locations
Select all relevant Locations
Click Edit
Select Enable on the Operational logging of Locations option
Click Update selected values
Now the toggling tool is visible for each Location, allowing you to mark it as in or out of operation and register Downtime.
Note: Toggling a Location open relies on the Location's status to be Ready for operation. A Location that is Not ready for operation will be unable to be toggled open.
Note: Enabling Operational Logging on a Location grants all Users with access to that Location visibility through the Operations tile in the mobile app.
Correcting Logging Mistakes
If a Location is mistakenly marked as in or out of operation, you can edit the log:
Navigate to Locations
Select the relevant Location
Click View Uptime Summary
Select the erroneous log
Click Edit Period
Apply the necessary changes
Click Save
Adding a Downtime to an existing Uptime Period
If a Location is missing a Downtime during an existing Uptime Period, you can add the Downtime by following these steps:
Navigate to Locations
Select the relevant Location
Click View Uptime Summary
Select the affected Uptime Period
Click Add downtime for this period
Add the necessary details including optionally creating a related Assignment
Click Add
Warning: Adding in an Assignment for a historical Downtime will open a new, High Priority Assignment that could change the Location's current status to Not ready for operation depending on your Organization's setup.
Creating a new Uptime Period
If a Location is missing an Uptime Period you can add the period by following these steps:
Navigate to Locations
Select the relevant Location
Click View Uptime Summary
Click Create Period
Add a start and end time
Click Save
Note: Uptime periods cannot overlap.
Understanding the RFO View
The Ready for operation (RFO) status communicates the operational status of Locations, similar to the Location Overview widget via Dashboards. The RFO status is indicated by box indicators and toggle statuses:
Ready vs. Not Ready
Each Location enabled with Operational Logging will hold one of two statuses that are visible via the Locations page or via the Location Overview on both the backend and mobile app:
Ready for operation
Not ready for operation
Operational Status | Significance |
Ready for operation | Indicates that the Location meets all criteria and is functioning normally. |
Not ready for operation | Indicates that the Location does not meet necessary criteria and cannot operate. |
Ability to Open a Location
The ability to open a Location relies on a Location being Ready for operation. This status is achieved when all Critical for Operation items have been satisfied including, at minimum:
Checklists marked Critical for Operation
Note: Each Organization is unique and can be configured to meet its specific compliance standards. High Priority Assignments, Blocking Downtimes, Checklists Awaiting Validation, and other criteria can be set up in the backend to affect a Location's Ready for operation status. For detailed information on your Organization's setup, please consult your Organization's main point of contact or contact Mobaro Support.
Operational Status Indicators
Mobaro allows you to easily view the status of a Location based on its Operational Status Indicators on both the backend and the mobile app.
Operational Status Colors
Operational Status | Significance |
In Operation | Indicates that the Location is functioning normally without any issues. |
Open Downtime | Indicates that the Location is undergoing a temporary interruption but can be managed or resolved without additional steps. |
Blocking Downtime | Indicates a critical issue that prevents the Location from being operational with an associated Assignment. The Assignment must be resolved before continuing operation. |
Not in operation | Indicates that the Location is not currently operational. |
Via the backend
Via the Location Overview widget on the backend, you can easily see the Operational Status of a Location with the Operational Status Box on each Operational Logging-enabled Location.
In Operation:
Active Open Downtime:
Active Blocking Downtime:
Out of Operation:
Via the mobile app
Users who have access to the Operational Log can view Operational Status via the Operations tile on the mobile app.
In Operation:
Active Open Downtime:
Active Blocking Downtime:
Out of Operation:
Integrating with Other Systems
Operational Logging data can be integrated with various systems for enhanced functionality, including the use of Mobaro’s API.
Using the Mobaro API
The Mobaro API allows for programmatic access to operational data, enabling seamless integration with other systems. Here are some example API calls and their usage:
Example API Calls
Get Operational Status
Retrieves the operational state of a Location.
curl -X GET "https://app.mobaro.com/api/customers/locations/{locationId}"
-H "x-api-key: YOUR_API_KEY"
Get Downtime Logs
Fetches downtime logs for a specific Location.
curl -X GET "https://app.mobaro.com/api/customers/downtime"
-H "x-api-key: YOUR_API_KEY"
Update Operational Status
Updates the operational status of a Location to Open.
curl -X PUT "https://app.mobaro.com/api/customers/locations/Open"
-H "x-api-key: YOUR_API_KEY"
-H "Content-Type: application/json"
-d '{"locations": "{locationID}"}'
Standard Connections
ERP (Enterprise Resource Planning Systems): Synchronize operational data with financial and resource planning.
BI (Business Intelligence Tools): Analyze data for insights and strategic planning.
By leveraging the Mobaro API, organizations can automate data exports, integrate with existing workflows, and enhance their overall operational efficiency.