Understanding Downtime Trends

Using granular downtime data to understand trends in downtime related to shifts, products and machines.

Benefits

Gain insights into which issues cause the most downtime, to prevent future issues and maximise efficiency.

Setup

Downtime data can be used from Production Cycle monitoring, Utilisation Monitoring or Independent Process Speed.

For downtime related to production cycle monitoring:

• Each station to be monitored must have a production schedule. This can be created via Schedule Management page or Quick Schedule Start.

• All SKUs to be produced must have a Performance Target set. This is the ideal rate that the SKU should be produced, based on Cycle Time, Units per Minute, Units per Hour or an Independent Process Speed.

For Utilisation Monitoring:

• For each station to be monitored, set a utilisation downtime threshold. This is the minimum number of minutes that should be considered as excessive downtime of the station.

• Ensure the setting 'Assume All In Shift Time is Planned Production' is set to true.

For Independent Process Speed:

• Stations and SKUs must have a Performance Target set. This is the ideal rate that the station should run or SKU should be produced, based on Cycle Time, Units per Minute, Units per Hour or an Independent Process Speed.

A tablet for each station to be monitored.

Daily Workflow

1. An issue is detected by Busroot.

2. Production manager will receive a notification via email or by viewing the cockpit. Operator will see an alert on the tablet..

3. Either operator or production manager assigns a cause to the issue. During team meetings, the previous days Slow causes are reviewed and discussed.

4. Over longer periods of time this data can reveal trends with the most commonly occurring issues, so they can be prevented in future.