ReasonState vs. Reason vs. State
There are 3 fields you’ll see in the Analytics Portal that appear to show similar results, however they are all slightly different.
The reason behind this to allow you the flexibility to analyze your data in the exact way you want, regardless of your unique scenario.
We highly recommend that you use ReasonState in almost every scenario, but we’ll cover it here last in order to better break down the differences, as it initially may seem confusing.
State
When you select State, the system will provide you with the data records for your actual machine States.
This means you will NOT get back data for any downtime “reasons” that your team entered during shifts, days, etc. It will only provide you with true machine states.
Examples of true machine states you’ll see in the portal:
Running
Idle
Slow Running
Micro Stoppage
Examples of when to use State:
When you want to see the number of occurrences when a machine was in certain states
When you want to find how long a machine was in a Slow Running state
When you want to figure out the cumulative duration a machine had Micro Stoppages throughout the day
Reason
When you select Reason, the system will provide you with data related directly to operator-entered (or automatic) downtime Reasons.
This means you’ll only get data for entered Reasons, and you won’t see anything that says “Idle” or “Running” etc. (unless your company configured them to be their own ‘Reasons’).
Examples of when to use Reason
When you want to see the number of times “Machine door open” reason occurred over a shift, time period, etc.
When you want to sort all your downtime Reasons by the total duration, to easily figure out your top 5 problem reasons
etc.
In other words, use “Reason” when you’re trying to analyze specific reasons
ReasonState
This is the most commonly used metric, and one Shoplogix recommends for most of our existing customers, as it behaves very similar to our previous reporting platform.
When you select ReasonState, the system will give you back all records where your team entered a Reason--and if a reason wasn’t entered, the system will provide the underlying State instead.
Example of how this works:
Let’s say you configured a reason called “Machine Door Open”, and it correlates with the “Idle” state
Your machine goes Idle 10 times in a shift. Your operator enters “Machine Door Open” for 7 of these Idle states, but doesn’t enter any reason for the remaining 3
ReasonState will provide you with:
Machine Door Open: 7 occurrences
Idle: 3 occurrences