Reference · for Engineers
OEE Loss Waterfall
A dashboard item that steps planned production time down through stop reasons, speed loss and quality loss to the fully productive time.
The OEE Loss Waterfall shows where planned production time went. Use it next to an OEE figure, when the question is not how high OEE is but what took the rest.
The chart starts with the planned time and steps down bar by bar:
- Stop reasons. One bar for each stop reason you bind (faults, changeovers, waiting and so on). Stop time that no bound reason covers is shown as other stops. Together they take planned time down to run time.
- Speed loss. The time lost by running slower than the ideal rate.
- Quality loss. The time spent making units that were rejected.
- Fully productive time. What remains, which is OEE multiplied by the planned time.
Every bar carries its time and its share of the planned time. On a wide item the bars run from left to right; on a narrow one, such as a phone, from top to bottom. With several lines in the data, the buttons above the chart show All lines or one line's own losses.
Data fields
| Field | Kind |
|---|---|
| Line | Dimension |
| Planned time (min) | Measure |
| Run time (min) | Measure |
| Stop reasons (min) | Measure (one or more) |
| Actual output | Measure |
| Ideal output | Measure |
| Good units | Measure |
| Rejected units | Measure |
Planned time and Run time are required, in minutes. Stop reasons takes one measure per reason, each the minutes lost to it. Actual output with Ideal output gives the speed loss, and Good units with Rejected units the quality loss; leave them out and the chart stops at run time.
Settings
| Setting | Values | Default |
|---|---|---|
| Time unit | Automatic, Minutes, Hours | Automatic |
Time unit shows the bars in minutes or hours. Automatic picks hours once the planned time is long enough for minutes to be hard to read.
Where to see it
The Meridian demo plant uses it on Meridian · Line Performance and Meridian · OEE Command Center.
Related
Was this page helpful?
Evaluating Proxus? See it on your own machines in a 30-minute technical session.