PI Batch End-Triggering Event combinations Data Source PIBatch End-Triggering Event(s) DeltaV EVT The batch recipe event containing [Event] field = and [Pvalue] “State Change” field = “REMOVED” DeltaV EVT with The first out of two recipe events is used to set an End Time for PIBatch /ubr switch object. enabled The batch recipe event containing [Event] field = “System and [Pvalue] field = Of Message” “End BATCH” The batch recipe event containing: [Event] field = “State and [Pvalue] field = / Change” “REMOVED”/ ”COMPLETE” ”ABORTED” DeltaV SQL The batch recipe event containing: [EventType] field = and “State Change” [EventDescript] field containing is used to set the End substring “REMOVED” Time for PIBatch. This event is retrieved from “dbo.brecipestatechangeview” or “dbo.batcheventview” views. DeltaV SQL with Uses source batch object [DeactivateTime] retrieved from SQL /ubr switch Batch Recipe type is provided for each object by the “dbo.batchview” table. enabled data source. DeltaV OPCAE The BATCH-EVENT event with Event Attribute [6] = is used to “REMOVED” set an End Time for PIBatch object (0 based index) Note, batch recipe type is determined by any of the BATCH-EVENT’s containing explicit action, such as Procedure Started/Finished, UnitProcedure Started/Finished, etc. PIUnitBatch A PIUnitBatch is created for each unit procedure as defined in the data source. The start and end times of a PIUnitBatch are intended to reflect the onset and completion of physical processing within a unit. The PIUnitBatch properties do not change if the parent object is a merged PI Batch. PIUnitBatch always contains original BatchID and Procedure name as it is defined in the source unless /tbid parameter was specified in command line parameters. This parameter enforces a stripped BatchID to be used for PIUnitBatch objects and for all events to be stored in PIPoints and PIProperties. When Operation or Phase level recipes are run, the interface uses the Operation/Phase name as the PIUnitBatch Procedure name.
PI Batch End-Triggering Event combinations Data Source PIBatch 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 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. DeltaV SQL with /ubr switch enabled Uses source batch object [DeactivateTime] retrieved from SQL “dbo.batchview” table. Batch Recipe type is provided for each object by the data source. DeltaV OPCAE The BATCH-EVENT event with Event Attribute [6] = “REMOVED” is used to set an End Time for PIBatch object (0 based index) Note, batch recipe type is determined by any of the BATCH-EVENT’s containing explicit action, such as Procedure Started/Finished, UnitProcedure Started/Finished, etc. PIUnitBatch A PIUnitBatch is created for each unit procedure as defined in the data source. The start and end times of a PIUnitBatch are intended to reflect the onset and completion of physical processing within a unit. The PIUnitBatch properties do not change if the parent object is a merged PI Batch. PIUnitBatch always contains original BatchID and Procedure name as it is defined in the source unless /tbid parameter was specified in command line parameters. This parameter enforces a stripped BatchID to be used for PIUnitBatch objects and for all events to be stored in PIPoints and PIProperties. When Operation or Phase level recipes are run, the interface uses the Operation/Phase name as the PIUnitBatch Procedure name.
PI_EMDVB_3.0.1.76.docx