Batch Events and 10.3

We’ve just finished successfully upgrading our DeltaV batch demo system to version 10.3, so I thought I’d share my hands-on experiences with some of the new and enhanced features.

So one of the first one’s I was excited about was the ability of the batch executive to have “significant batch events” flow to the event chronicle. And while I’m sure OSI is happy about this one, everyone should be.

Let’s be clear as to what “significant batch events” are – it’s NOT everything that’s currently in the batch journal, but all events associated with creating, starting, ending, and unloading of procedures, unit procedures, and operations get to the event chronicle.

Note in the screenshot below how the batch ID is displayed – you get both the ID entered by the operator and the internal ID DeltaV uses for tracking in the historian:

Now, silly me, I thought that once I upgraded to 10.3, I’d just run a batch and BAM, the data would be in the event chronicle. Well, I should have known better – you have to enable it. Where you might ask? About the last place I’d look, but now that I’ve found it, maybe I’ll save you some time.

Launch the Batch Application manager, and on the Batch Executive tab, select the Advanced tab, then select the Configuration Settings tab – here you’ll find all sorts of BE trivia selections. Scroll down to the Enable Alarm and Events Journaling, and double click it: