Leveraging Your Batch Data

It seems everyone has drunk the “Collect all the Data” kool-aid, but forgot the “Analyze and Report” chaser.  One more raw, unformatted table passing off “Select * from myTable” as a batch report may just cause a singularity of suck that will destroy us all.

I’ll give the process engineers a pass. They’re used to a nice Pi vision interface and just need visibility into the alarms and events data to troubleshoot their magic.

But the systems integrators passing this off as a viable solution need to do better.

We’re fighting the same fight. The tools are hard to use. And a lot of the time, the person writing the report has zero process contextualization to make a good report.

However, there are actions you can take even if all you have is a set historical logs.

Build in filters. At a minimum, have a way to automatically build out event frames and present pull-down boxes for batches/cycles/whatever.

Use drill down linking. So even if folk don’t know what they want, it is possible to review from a high level and follow a set of links to get granularity.