Batch Events in PHV

Back in April, I wrote about how major batch events can now make their way into Process History View. So what’s that look like? How do I find these batch events? Well, there’s a new Category named BATCH-EVENT. So if I go into PHV, and filter on Category equal to BATCH-EVENT, I get something like this (I’ve hidden some columns that don’t pertain to batch events to make it easier to read):

One of the first things to note is the Parameter column contains both the unique Batch ID as assigned by DeltaV and the Batch ID as entered from the Create Batch view. The State column gives you a taste of the different “major batch events” now being captured. Here’s a non-comprehensive list of major batch events:

BATCH ADDED
BATCH REMOVED
CAMPAIGN CREATED
LOAD
Manual Phase Started
Mode Change
Operation Finished
Operation Started
Operation Started with Equipment
Phase Finished
Phase Started
Phase Started with Equipment
Procedure Finished
Procedure Started
REMOVED
Resource Acquired by recipe
Resource Released by recipe
State Changed
Unit Procedure Finished
Unit Procedure Started
Unit Procedure Started with Equipment

Noticeably absent from the list are report parameters. If I could somehow get report-like parameters into PHV, I’d have some pretty useful information. Enter the LOG EVENT function. The LOG EVENT function has been around a long time (go to BOL on how to use it), but the cool thing is how it looks in PHV. And it looks different, depending if it’s used in a regular module as opposed to phase logic:

When it’s used in just a regular module, the Desc1 column is empty. When it’s used in phase logic, the Desc1 column contains the Batch ID!

So for this example, if I look at the Parameter column to contain Acme11May2009 or the Desc1 column to contain Acme11May2009, and sort the result by Date/Time…to be continued.