The mobile app works as a convenient tool for the personnel out in the field to do immediate registrations of downtime for the locations under their responsibility. As described through the different Workflow Example and Usage Scenarios, the app is much more limited in its functionality when it comes to downtime registration and more rigidly obeys the different states – e.g. a location cannot be marked as In Operation via the app when there exists a blocking downtime registration.
Administrative users who do the bulk of their work in the back-office web application will experience a higher degree of freedom when creating, editing and closing downtime registrations. For example, while downtime registrations initiated via the mobile app will be marked with the timestamps when the actions are performed in the app, administrative staff will have the freedom to manually assign the dates and times to the downtime registrations. This is to allow for administrators to register downtime events and operational hours back in time in the case that the operator/technician forgets it or because operators aren’t equipped with the mobile app.
Manually creation “Operation Hours” records for Locations
Mobaro supports the situation where there’s a requirement to register operational hours on locations but where the staff might not be equipped with a device to run the mobile app.
In this case, the records for operational hours will need to be done via the back-office application. This can be done in one of two ways.
Manually toggling the locations
From the Location list, locations which support downtime registrations will have a toggle button to their right. This works identically to the function which users of the mobile app have through their “Operations” tile. In other words, there’s no functional difference between marking a location as In Operation from the back-office application or doing it via the mobile app.
Per the example in Measuring Downtime Duration, marking the location as In Operation should be done when the location is meant to start its operational hours, while switching it to In Operation should be done when the location is no longer in active operation. The span between these two events will be used to calculate the amount of operational hours.
Remember, that while downtime registrations have the ability to force a location out of their In Operation state, it will never automatically go into the In Operation state once a downtime registration has been resolved. This will always need to be done manually.
Creating log entries manually
Situations might arise, where locations are erroneously marked as In Operation or Out of Operation. Fret not, entries can be both deleted and edited from the back-office. Go the location’s Operational Log and select the entry you want to delete or edit.
Edit old Downtime Registrations
Despite hiding Closed downtime registrations by default, they are not entirely gone. To show the entire list of downtime registrations, just change the filter to include those in the Closed state.
From here, you have the same access as you usually have to open up the individual registrations and change their categorization or add a log message to the individual incident.