Reason codes

Reason code are selection options the front lines teams will see in their down times module.

Mandatory fields

• Name - The name the frontline teams will see in their list and their selection boxes. A tree sructure can be created from any of the reasons (names).

• Color - The color the frontline teams will see in their timeline and within tables

Optional fields

• Parent reason - Select an existing reason to build a tree. They will become availabe in the selection boxes when qualifying a down time

• Category - Selection of the down time categories for reporting purposes.

• Event codes - The fault / error / event codes that is passed on from the middleware. One can select multiple codes to be assigned to an individual reason code. This set up ensures:

  • Simplification for front line teams due to elimination of manual entries

  • Consistency in reporting thanks to automated allocation

• Requires issue - The system can help to shape the culture of continuous improvement by triggering employees to link issues. This will deepen the level of details when down times occur.

  • Yes - An issue is expected for this specific reason code.

  • No - Issues are not to be linked mandatory

  A table on the landing page of down times will show any open reason codes without issues

• Split after minutes - Automatic split of downtimes after a certain threshold. Often used to split planned downtime events into unplanned downtime events when passing the time limit.

  • Eg. The reason code "Planned Downtime - Change Over Packaging" is planned to take 10minutes. The change over lasts 16minutes. After 10 minutes, the downtime is split and a new reason code "Unplanned Downtime - Change Over Packaging" can be assigned.

• Can be final - Indicates whether a reason code is at the expected level of granularity. When not final, the table will indicate "uncoded" stops on the landing page

Initial set-up & Ongoing improvements

• Initial set-up - When starting up with Maecos, a bulk upload can be facilitated to ensure smooth and fast transition ot the new user interface. Eliminating manual work during the switch to your new dowtime mogging

• Ongoing improvements - There is no need for us to be the bottleneck during daily operations. You hold all the keys to continuously improve the system:

  • When new fault codes are created, you can quickly add them to a reason cide

  • When reporting needs change, you can update categories

  • When more granularity is required, additional reason codes can be created.