Source Phase AF EventFrame Fields AF EventFrame Referenced Properties Attributes 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 AF Attrubute AF Attribute Value AF Attribute Category Name UOM “Event” Column Values Recipe Value Source Source Source Recipe “Pvalue” “EU” column value column value Value “Description” Column value Report Source Source Source Report “Pvalue” “EU” column value column value “Description” Column value 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 = and [Pvalue] “State Change” field = The [Recipe] field contains the batch recipe hierarchy. “RUNNING”. DeltaV EVT with For Procedure-, Unit Procedure-, Operation- and Phase-level recipes, the /ubr parameter batch recipe event containing [Event] field = and [Pvalue] field “State Change” enabled = is used to set the start time for a PISubBatch phase- level “RUNNING” object. The [Recipe] field contains the batch recipe hierarchy. DeltaV SQL The batch recipe event containing [EventType] field = and “State Change” [EventDescript] field containing substring is used to set the start “RUNNING” time for a PISubBatch phase-level object. The event is retrieved from the / view. “brecipestatechangeview” ”batcheventview” The batch recipe hierarchy is specified in the [Action] field. event’s
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.
PI_EMDVB_3.0.0.57.docx