Download PI Interface for Emerson DeltaV Batch

Principles of Operation
the merged event frame. For each merged source batch, the interface creates a node in
Extended Properties of the event frame, named with the UniqueID of the source batch and the
value containg the XML containing the original source batch properties.
Note: A source batch can terminate unexpectedly without proper unloading by the
operator. The interface maintains such a batch in the local memory for 100 days,
after which the batch is considered abandoned and the interface closes the batch
with the latest known time stamp for this particular batch. The abandon timeout can
be changed using the command line parameter /abto=<days> (Abandoned Batch
TimeOut).
Procedure-Level AF Event Frame Start Event Combinations
Data Source
AF Event Frame Start-Triggering Event(s)
DeltaV EVT
The batch recipe event containing [Event] field = “State Change” and [Pvalue]
field = “CREATED”
The batch recipe type is determined by the recipe messages, such as the
system message “Procedure Started, Unit Procedure Started”, etc.
DeltaV EVT with
/ubr switch
enabled
The batch recipe event containing: [Event] field = “System Message” and
[Pvalue] field = “Beginning Of BATCH”. The associated [EU] field =
“Procedure” / “Unit Procedure” / “Operation” / “Phase” determines the type of
the particular recipe.
DeltaV SQL
The batch recipe event containing: [EventType] field = “State Change” and
[EventDescript] field containing substring “CREATED” is used to set the Start
Time for PIBatch. The batch recipe type is provided for each event by the
data source in the [Action ] field. The event is retrieved from
“dbo.brecipestatechangeview” or “dbo.batcheventview” views.
DeltaV SQL with
/ubr switch
enabled
The batch object with [ActivateTime] timestamp used to set the Start Time of
PIBatch. This batch objects are retrieved from SQL “batchview” view. The
batch recipe is determined by other batch recipe objects retrieved from
“batchrecipeview” view.
DeltaV OPCAE
The BATCH-EVENT event with Event Attribute [6] = “LOAD” is used to start
PIBatch object (0 based index)
Note: The batch recipe type is determined by any of the BATCH-EVENT’s
containing explicit action, such as Procedure Started/Finished, UnitProcedure
Started/Finished, etc. The Procedure-level event frame is not created until the
interface is able to identify the recipe type of the batch, which is normally
available as soon as the recipe is loaded and started.
Procedure-Level AF Event Frame End-Triggering Event Combinations
Data Source
AF Event Frame End-Triggering Event(s)
DeltaV EVT
The batch recipe event containing [Event] field = “State Change” and [Pvalue]
field = “REMOVED”
DeltaV EVT with
/ubr switch
enabled
The first out of two recipe events is used to set an End Time for PIBatch
object.
The batch recipe event containing [Event] field = “System Message” and
[Pvalue] field = “End Of BATCH”
The batch recipe event containing: [Event] field = “State Change” and
[Pvalue] field = “REMOVED”/ ”COMPLETE” / ”ABORTED”
DeltaV SQL
40
The batch recipe event containing: [EventType] field = “State Change” and
[EventDescript] field containing substring “REMOVED” is used to set the End
Time for PIBatch. This event is retrieved from “dbo.brecipestatechangeview”
or “dbo.batcheventview” views.