Prerequisite

• Access to the File > Downtime reason (MA054) menu.

Introduction

A downtime reason indicates the specific reason why the operation of an asset has been interrupted. Understanding and recording downtime reasons is crucial to maintaining the efficiency and productivity of operational processes.

Examples of downtime reasons

• Operational: power outage, lack of supplies, shift change.
• Technicians: preventive maintenance, corrective maintenance, technical failure.
• Environmental: adverse weather conditions, natural disasters.

Practical example

During the operation of a production line, it is possible to record downtime reasons in the system, such as preventive maintenance or lack of supplies. These reasons are entered into the downtime records associated with the assets involved. This allows for a detailed analysis of the causes of interruptions and facilitates the implementation of corrective actions.

Adding a downtime reason

1. Access the File > Downtime reason (MA054) menu.

2. Click on the toolbar button.

3. On the screen that will open, enter an ID # and a name for the downtime reason.

4. Check the Delete downtime for usage rate indicators option so that the downtime records with this reason do not influence the calculations of usage indicators.

5. Configure the Approval section so that the downtime reason record goes through approval. For further details, click here.

6. Check the Create corrective maintenance when generating a downtime record option so that, when a downtime record with this reason is generated, a corrective activity is automatically created.

7. In this case, select one of the following options:

• Generate one WO for each asset: a corrective activity will be created for each asset associated with the downtime record. To this end, data must be entered, and one activity must be closed at a time.
• Generate one WO associating all assets: a corrective activity will be created for all assets associated with the downtime record. To this end, data must be entered, and the activity must be closed only once.

8. In the corresponding field, select the standard activity from which the corrective maintenance activities will be created.

9. Click on the button to enable the Attribute tab.

10. In the Attribute tab, define the attributes that will complement the downtime records with this reason. For further details, click here.

11. Click on the button to save the record.

Conclusion

Once saved, the record will be ready to be associated with a downtime record.

Using the downtime reason feature is essential to ensuring the continuity and efficiency of operational processes. This allows the organization to quickly identify the causes of interruptions, implement effective solutions, and maintain high standards of productivity and quality in its operations.