Amper Learning Hub
Experience Downtime Periods
🗂️

Experience Downtime Periods

Downtime Periods

A Downtime Period is a length of time where a machine is not running production. Operators can use the Operator Interfaces to add a Downtime Code to a given Downtime Period. Labeling these Downtime Periods allows your factory to track your root causes of downtime and better understand how to improve your operations.

How are Downtime Periods Generated?

Downtime Periods are generated based on two main thresholds to help control how you track your Downtime:

‣

Downtime Period Start Threshold

The Downtime Period Idle Threshold determines the amount of consecutive Idle/Off time needed to begin a Downtime Period.

For example, let's say a machine has a Downtime Period Idle Threshold set at 5 minutes and is not currently in a Downtime Period. If your machine is idle for 3 minutes, a Downtime Period will not be created since this is below the 5 minute threshold. Once the machine is idle for 5 minutes, the Downtime Period will be created.

The default value for this threshold is 5 minutes, but it can be adjusted to any full minute value on a factory wide basis.

‣

Downtime Period End Threshold

The Downtime Period Production Threshold determines the amount of Production time needed to end a Downtime Period.

For example, let's say a machine has a Downtime Period Production Threshold set at 5 minutes and is currently in a Downtime Period. If your machine has Production for 3 minutes, the Downtime Period will not end. Once the machine does have production for 5 consecutive minutes, the Downtime Period will end.

The default value for this threshold is 5 minutes, but can be adjusted to any full minute value on a factory wide basis.

If the downtime reasons in your system need to be edited, you can learn how to do that in your system settings on this page:

.

‣

How to Create Actionable Data from Downtime Labeling

Set up Operator Interfaces on the floor (computers or tablets)
Make sure 8-digit codes are accessible for logins
Set goals for downtime labeling (ex. 10% or less of downtime should be unlabeled)
Conduct a formal training and kickoff Downtime Labeling with Operators
Create an Audit Plan

Example:

Once labeling is happening consistently, schedule a data review meeting with your CSM or check out Data Driven Projects

Learn how operators can enter their downtime reasons to provide you with robust data for Root Cause Analysis
👇
To go back to the main page, click below
👥
Learn the Operator Interface