Product Release | Track root cause with reason codes

The latest version of Runtime introduces reasons, tags that you can assign to a downtime or idle event. Reasons allow you to more granularly see how time is spent and track the root cause of lost time.

You can define any reasons you want. For example, you may want to differentiate downtime caused by machine issues versus downtime caused by material replenishment. Each of these can be created as a reason and selected when downtime occurs. 

How it Works

When you navigate to the Runtime section of the web console, there’s a new tab for reasons. To add a new reason, click add and then provide a name. Select whether you want this reason categorized as down idle.

In the app, when you next start downtime or idle time, you will select from the list of reasons you created.

Runtime dashboards will also include data on your root cause reasons.

You can see a list of your top reasons, along with how often they’ve occurred and how much time you’ve spent on them.

We also provide a daily breakdown of time spent on each reason. The two columns represent down and idle reasons.

These views are available on the Runtime snapshot and the location detail pages.

Bottom line - reasons are a powerful update to Runtime that make your data more actionable. Give them a try and let us know what you think!

Review our full release notes here. 

If you've read this far, here's "The Reason" by Hoobastank. 

"I found a reason for me,
To update my factory,
A reason to track what we do,
And the reason is Runtime"