Time per Stop Reason

Hi James

This is a really good use-case for Flow.  Being a partner product, I know the guys at Canary won't mind me sharing this with you on the Canary forum.  There are 2 ways to do what you are looking for, depending on how much information you require.

1. Create a Flow measure for the time period (e.g. Hourly), point it to the Canary "fault code" tag, select the "Time in State" primary aggregation with a state of 46.  Flow will then calculate the downtime duration caused by fault 46 for every hourly time period.  You can backfill this to as far back as you need to.  You can also perform a secondary rollup aggregation to calculate how much downtime was caused by fault 46 per day for example.  You can then trend the hourly or daily values in a Flow dashboard, or push the values back to a Canary tag to display in Axiom.

2. The previous method would effectively be "hard coded" for fault code 46.  A more generic option would be to create a Flow event for "Downtime".  You would define start and end triggers for the "Downtime" event using the "Machine Running" tag.  This will automatically transform the time based tag data into downtime transactions, each with a duration already calculated.  You can then configure additional "context" you would like to capture against each event transaction.  So in your example, you would attach the "fault code" tag as context you would like to capture.  You can even give each fault code a description (e.g. 46 = "Machine starved", etc.).  Using this method will capture all downtime events and "allocate" the reason to them.  You could allocate additional information to each event transaction (e.g. "Product", "Operator", "Work Order", etc.).  This information can then be visualized on a Flow dashboard in a Pareto Chart.

Hope this gives you a taste of the capabilities of Flow.  This is a common use case.

Cheers

Graeme