Watch 4-minute video 👇

Editing Downtime in the Downtime Console

Overview

Have you ever realized that you labeled downtime incorrectly only after it was too late?

Historically Amper has allowed customers to make edits to downtime events only if they are unlabeled. Now, customers can view and edit (split, label/re-label, comment, etc.) all downtime events, whether or not they’re labeled or unlabeled.

View All Downtime with the Downtime Console

All downtime events and corresponding details are now visible from the Downtime Console found under the Timelines section of the app.

Each downtime event shows the date/time range, Downtime Reason (or Unlabeled), and Downtime Comments.

The filter header at the top of the page contains an Unlabeled Only checkbox. When selected, you will only see your unlabeled downtime. When unselected, both labeled and unlabeled downtime will be shown.

Note: Make sure you click the blue Apply button after making filter changes!

Unlabeled only checkbox highlighted

📣

The Unlabeled Only checkbox is selected by default. This means that when you first go to the downtime console you will only see unlabeled downtime.

Edit Downtime Events

All downtime labels and comments can be edited from the downtime console. You can edit many events at once!

Select the checkbox(es) next to the downtime event that needs to be edited. Once selected, the timeline in that downtime event will highlight in blue.

Here we will be changing the selected downtime events (indicated by the blue check marks at the left of the image)

Select the downtime reason you’d like to apply by using the downtime reason picker at the bottom of the page. This will change all downtime periods selected to the same reason selected.
When you are satisfied with the selections, click the check mark to apply those changes. Once applied, any changes made to the data will be highlighted in blue.

Notice the blue downtime reasons at the right of the image showing these were edited. We changed both of these downtime events to be labeled for Repair/Rework.

If you want to make additional changes, repeat the process.

Here we will be editing the selected downtime event and changing it from Waiting on Maintenance to Mechanical

📣

New Downtime Comments can also be added during this process by clicking directly on the Add Comment text and typing.

Add Comment text highlighted

Here we will be typing Mechanical Issues

🚨

Once all changes have been made, click on the Review & Save button at the bottom of the screen.

Review, Save, and Cancel Edits

The Review & Save button will bring you to the Summary page. Here you can review all edits made, choose to Commit those changes or Cancel and continue editing.

All pending changes will be highlighted in blue on the summary page.

In the example below:

The first downtime event has an updated downtime comment and downtime reason.
The second and third downtime events have updated downtime reasons.
The last downtime event has only an updated downtime comment, while the downtime reason remains unchanged.

The Cancel button will bring you back to the previous screen with the pending changes, where you’ll be able to continue editing or clear all changes.

If you select Commit Changes, all changes will be saved and you’ll return to the main downtime console screen.

View Edits & Changelog

Once the changes are saved, any user can view whether or not a downtime event has been edited from the downtime console by looking for the Edited indicator in line with each edited downtime event.

When the Edited indicator is clicked, a change log will expand below the edited downtime reason to show the date and time of all edits and the user(s) that made those edits. Click on the Edited indicator again to collapse the change log.

After clicking Edited the change log will show below the selected reason to describe the change that occurred.

How do I get it?

No action required. Once released, this will replace the existing downtime console in all factories.

What's not here?

You cannot unlabel a downtime reason. Once a downtime event has a downtime reason you can only update it to a new label, but you cannot bring the reason back to ‘unlabeled’.