Overview
This article introduces the basic use of Downtime, including the different states a Downtime can enter during a workflow. It also covers the general terminology associated with Downtime. Understanding how to manage Downtime effectively can help you minimize operational disruptions and streamline the process of addressing and resolving interruptions.
Users must be Super Users or have the following role to manage Downtime:
Operations: Manage Downtime
Why Use Downtime?
Downtime allows you to register interruptions that result in Downtime at a Location and register Assignments related to a specific Downtime incident.
Downtime reporting can focus on three different areas:
Downtime Registration: Focuses on the events that lead to Downtime.
Operational Hours Impact: By registering Downtime and focusing on operational hours, you get an indication of lost operational hours due to Downtime.
Assignment Management: By adding Assignment management for Downtime events, you can track the corrective actions taken to resolve a Downtime incident.
Downtime States
Each Downtime registration has a state depending on its place in the workflow. The states are: Open, Blocking, Resolved, and Closed.
State | Description | Management |
Open | The initial state of a Downtime registration, regardless of whether it is created from the mobile or web app. | Mobile App: The User can mark the Location as operational again immediately.
Web App: An administrative User can mark the Downtime as ended, moving it to a resolved state.
Web App Assignment: If an Assignment is attached, it moves the Downtime to a blocking state. |
Blocking | The state of an active Downtime with an open Assignment attached to it. If your organization has enabled automatically creating Assignments in case of Downtime, this is the initial state. A Downtime will enter the blocking state if an Assignment is manually created on an open Downtime | Mobile App: The Location will be marked with the message “Not Ready,” and the ability to mark the Location as open will be disabled. Users must resolve the associated Assignment to move the Downtime to a resolved state.
Note: Administrative staff cannot force the Location back into an operational state from the web app. |
Resolved | The state of a Downtime that has been resolved, and the Location is back in operation or allowed to be marked as operational. This state change can happen automatically or manually. | Mobile App: Open Downtime registrations can be moved to the resolved state by marking the Location as in operation.
Blocking Downtime: Automatically moves to resolved when the associated Assignment is resolved.
Final Step: Administrative staff must close the Downtime registration and finalize the report on the actual Downtime duration. This is done in the web app by selecting the Downtime registration and pressing “Close Downtime”. |
Closed | The final state, indicating that the Downtime registration has been concluded. | Finalization: Administrative staff finalizes the Downtime registration in the web app, ensuring all necessary reporting is complete.
Historical Logging: Only closed Downtimes are logged as historical information. Resolved Downtimes will not be registered historically until they are closed. |
General Terminology
Open/Close Events: Marking a Location as either "in operation" (open) or "out of operation" (close). These events are used to calculate operational hours and can be logged by Users via the mobile app or by administrative staff via the web app.
Downtime Registration: Recording a single Downtime incident. This can be done by Users through the mobile app or by administrative staff via the web app.
Downtime Categories: Customizable categories created by administrative staff to identify the cause of Downtime. A single Downtime event can have multiple categories.
Actual Downtime: The total time a Location is non-operational due to Downtime, finalized by administrative staff in the web app. This is used to calculate the total Downtime for a Location.
Operational Log: A timeline of all open/close events for a Location, accessible in the Locations tab of the web app. Administrative staff can add, delete, or edit these logs. The log helps calculate the total operational hours for a Location.