Overview
Downtime management in Mobaro is crucial for optimizing operational efficiency and accurately tracking lost operational hours. This guide covers the essentials of measuring Downtime, understanding the different states a Downtime can enter during a workflow, and editing existing and closed Downtime registrations. By mastering these processes, you can ensure minimal disruption and effective resolution of interruptions.
Users must be Super Users or have the following role to manage Downtime:
Operations: Manage Downtime
Locations: View or Modify
Measuring Downtime
Measuring Downtime means finding the total amount of lost operational hours a Downtime registration has incurred. This is done in the web app when closing a Downtime registration. Although it is a manual step, the system helps with easy registration.
Calculation of Downtime:
Nominal Operational Hours:
Registered Operational Hours + Registered Downtime = Nominal Operational Hours
Downtime Percentage:
(Registered Downtime / Nominal Operational Hours) * 100 = Downtime Percentage
Note: Only register the amount of time the Location was out of operation where it should have been operating.
Downtime Scenarios
Downtime can occur in different scenarios. Here’s how to handle each:
Short-lived Downtime Registrations
Short-lived Downtime Registrations
Expected Operational Hours: 06:00 - 20:00 (14 hours)
Downtime: Starts at 14:00 and ends at 15:00 (1 hour)
Steps:
When closing the Downtime registration in the web app, verify the amount of Downtime.
The system suggests the time between the Downtime start and the resolved state.
Edit the suggested time if needed.
Calculation:
Nominal Operational Hours: 13 + 1 = 14 hours
Downtime Percentage: 1/14 = 7.1%
Downtime Exceeding Normal Operational Hours
Downtime Exceeding Normal Operational Hours
Expected Operational Hours: 06:00 - 20:00 (14 hours)
Downtime: Starts at 14:00 and ends at 22:00 (8 hours)
Steps:
When closing the Downtime registration, ensure correct Downtime is logged.
Only log the hours the Location was expected to operate but was down.
Calculation:
Actual Lost Operational Hours: 14:00 - 20:00 = 6 hours
Downtime Percentage: 6/14 = 42%
Downtime Spanning Multiple Days
Downtime Spanning Multiple Days
Day One: Downtime starts at 14:00
Day Two: Downtime resolved at 22:00
Steps:
Verify the operational hours for each day.
Only log the hours the Location was expected to operate but was down.
Calculation:
Day One: 14:00 - 20:00 = 6 hours
Day Two: 08:00 - 22:00 = 14 hours
Total Downtime: 6 + 14 = 20 hours
Expected Operational Hours: 28 hours (over two days)
Downtime Percentage: 20/28 = 71%
Note: The system will not automatically disassociate hours that are meant to be closed, therefore it is recommended to ensure you are only tracking Downtime hours as they match to expected operational hours.
Editing Existing and Closed Downtime Registrations
You can manage existing and closed Downtime registrations through the web app by following these steps
Navigate to
DowntimeClick
State and ensure to include ClosedSelect the Downtime registration from the list and click
Edit.Make changes and click
Save.