With the addition of “Downtime Registration” you are now able to register incidents which result in downtime on a location as well as register assignments related to a particular downtime incident.
For those who want exact measurements on the downtime/uptime percentages, you are also able to capture operational hours on locations by marking them as “in operation” via either the app or the back-office web application.
This bundle of articles will cover the overall concepts of downtime registration, registration of operational hours as well as the workflows supported for administrative personnel who will be working with downtime events in the back-office application. Articles covering how downtime events can be started and closed from the app as well how locations are marked as operational or out of operation, please go here.
Downtime Registration is intended to support your organization's requirements for downtime registration and handling downtime events in 3 different usage scenarios, depending on whether you want to capture downtime, downtime as well as operational hours or whether you want to tie downtime registrations into your assignment workflow in Mobaro.
Before we head into the different usage scenarios, here is an introduction to some key terminology:
- Open/Close events: The act of marking a location as either “in operation” or “out of operation”. Operational hours are calculated based on the timespan between each “open” event and the following “close” event. This can be done by the operators/technicians from the Mobaro app as well as by the office staff on the Location list in the back-office application.
- Downtime Registration: The individual downtime events which can be registered by operations/technicians through the Mobaro app or created by office staff in the back-office application.
- Downtime Categories: Downtime registrations can be associated with one or more categories. This is done by the administrative staff when handling or finalizing a downtime registration. Categories are customizable by you and is meant to ease reporting by providing a category to aggregate downtime by (e.g. so you can get the total amount of downtime attributed to “Weather”).
- Downtime Duration: A downtime registration, when finalized by administrative staff, can be set to have incurred an amount of downtime. This is done in the back-office application and is the basis for the calculation of the total amount of downtime for an individual ride.
- Operational Log: The log attached to each location which is accessible from the Locations list in the back-office application. A timeline of all the open/close events registered on any individual location. Administrative staff can add, delete and edit these. This is the list of open/close events used to calculate the accumulated Operation Hours for a location.