Does anyone know if DeltaV provides a way to recall batch recipe history? Our plant needs a way to do this, and are looking into third-party software which extracts the info from DeltaV, but I'd much rather stick with DeltaV if there is a way to do it.
I haven't taken the batch class yet, so a lot of the batch programming/configuration is unknown to me.
Thanks
First, Do you have a batch historian configured? A batch historian will take the .evt files created by the batch executive for batch history recording and organize the data into a SQL database.
From the SQL database, the DeltaV Batch History View client can be used to evaluate batch history.
Without the Batch historian, you can look at the batch event journal through the Batch Operator Interface application.
In reply to Youssef.El-Bahtimy:
I have not personally set up batch historian, but that does not mean it is not configured.
I can open "Batch History View" but I'm not sure if it is pulling the correct data from a SQL database. The history seems to be intermittent/sporadic.
If I can open Batch History View and there is data to look at, does this mean that we definitely have Batch Historian?
Guess I need to figure out how this historian works and configure it properly. Can you point me toward any resources that might help?
In reply to depthcharge623:
If you can open batch history view and you see batches represented as a gantt chart, then you have a batch historian.
The question is what kind of data are you looking for.
In DeltaV, historical data is recorded in 3 major formats/databases
1. Alarm and Event chronicle - These are discrete process events not directly associated with a batch. It includes things like process alarms, system status alerts, user logins, phase loading/unloading.
2. Batch History - This is a record of discrete events associated directly with recipe execution in the batch executive. It includes things like recipe state changes, operator prompt issuance and responses, recipe and report parameter values. Alarm and Event Chronicle information can be stored in the Batch History database to allow correlation of non-batch discrete events to batch events, however batch history view cannot do this correlation.
3. Continuous History - These are the non-discrete records associated with analog process values. Unlike discrete events generated by the source, these values are polled or requested by the historian scanner at a regular frequency. They are not necessarily stored at a regulary frequency, as a tolerance for storage is defined so that when a value is unchanging, database space is preserved . This data has no correlation to batch data, implictly.
So the inquiry about how to view batch data could mean having to aggregate information from all of these sources in the context of a batch or campaign (which may not even line up with the recipe design, depending on how the recipes were coded).
Currently, the main desire is to recall batch recipe parameters.
It appears that the most recent data available in Batch History Viewer is from 9 months ago. I don't know what changed, but it appears to have stopped archiving the files. Where do I need to go to configure this?
The batch historian service has probably stopped. It is not setup by default to start automatically. If your batch historian was restarted, the service will need to be restarted manually.
I suggest setting the service to start automatically through the Windows Services console. (Run-->services.msc-->DeltaV Batch Historian--Startup Type = Automatic).
Start the service either through the console or through the Batch Historian Administration application on the historian.
The bad news is, the batch executive automatically purges .evt files older than a configurable age (45 days is the default I think). If the service was down longer than this setting, you have most likely lost the batch history.
When the service is started, it may take a few hours or longer to work through the unprocessed .evt files and display the data in the client.
Recipe parameters are visible through the batch history view client at the individual phase level. Additionally, you can setup templates in BHV if you will be routinely looking for the same set of recipe/report parameters for each batch.
In reply to Raj Bharath:
In reply to ELvin John: