Source Phase Properties AF EventFrame Fields AF EventFrame Attributes Referenced elements Phase Name Name Start Time Start Time End Time End Time Unit Unit Phase Module Phase Module Template=”Phase” Category=”OSIBatch” By default, the interface captures and stores the following batch associated events as event frame attributes: Souce Batch “Event” Column Values AF Attrubute Name AF Attribute Value AF Attribute UOM Category Recipe Value Source “Description” Column value Source “Pvalue” column value Source “EU” column value Recipe Value Report Source “Description” Column value Source “Pvalue” column value Source “EU” column value Report Note: The Phase-level recipes automatically populate upper levels of the event frames hierarchy with the Procedure-level event frame Recipe attribute UnitProcedure- and Operation-level event frame Name field as the name of the source Phase recipe object. Phase-Level AF Event Frame Start-Triggering Events Data Source AF Event Frame Start-Triggering Event(s) DeltaV EVT The batch recipe event containing [Event] field = “State Change” and [Pvalue] field = “RUNNING”. The [Recipe] field contains the batch recipe hierarchy. DeltaV EVT with /ubr parameter enabled For Procedure-, Unit Procedure-, Operation- and Phase-level recipes, the batch recipe event containing [Event] field = “State Change” and [Pvalue] field = “RUNNING” is used to set the start time for a PISubBatch phase- level object. The [Recipe] field contains the batch recipe hierarchy. DeltaV SQL The batch recipe event containing [EventType] field = “State Change” and [EventDescript] field containing substring “RUNNING” is used to set the start time for a PISubBatch phase-level object. The event is retrieved from the “brecipestatechangeview” / ”batcheventview” view. The batch recipe hierarchy is specified in the event’s [Action] field.
There are four EVT files starting at different times and containing data written sequentially by Batch Execution System. The vertical axis is the file time, where the t1 is the earliest time and the t11 is the latest time. The alphabetical file name processing sequence is given in the table below. Order File Name Data Segments [start time – end time] written by the BES in parallel EVT files t1 – t2 t2 – t3 t3 – t4 t4 – t5 t5 – t6 t6 – t7 t7 – t8 t8 – t9 t9 – t10 t10 – t11 1 File 1 X X X X 2 File 2 X X X 3 File 3 X X 4 File 4 X The event time ordered processing is illustrated in the table below Order File Name Data Segments [start time – end time] written by the BES in parallel EVT files t1 – t2 t2 – t3 t3 – t4 t4 – t5 t5 – t6 t6 – t7 t7 – t8 t8 – t9 t9 – t10 t10 – t11 1 File 1 X 2 File 3 X 3 File 1 X 4 File 2 X 5 File 1 X 6 File 3 X 7 File 2 X 8 File 4 X 9 File 1 X 10 File 2 X Dealing with Irrelevant Recipes Sometimes it is necessary to exclude particular recipes from being processed into PI Server. Such recipes can be excluded from processing by using the INI file command skiprecipes. The switch contains the list of all recipes or recipe masks the interface should not evaluate. Everything related to specified recipe is not processed into PI Batch Database, PI Module database and PI Points databases. The filtering supports the following recipe types: Procedure, UnitProcedure, Operation, and Phase. For each event to be processed, the interface will check for the match in the recipe fields depending on recipe type: Procedure Recipe : [Procedure] field of event Unitprocedure Recipe: [UnitProcedure] field of event Operation Recipe: [Operation] field of the event Phase Recipe: [Phase] field of the event Multiple recipes or their masks can be specified with a comma separator. If there is a space in the recipe name, use double quotes for the entire switch (not required if specified in INI file).