Emerson Deltav batch Interface

Property Templates

By default the interface does not store batch associated data into PIProperties. To store data in PIProperties, use Property Templates which define the subset of events and associated PIProperty value structure for each event to be stored in PIProperties. The Property Templates are not case sensitive and must be defined in the INI file associated with each specific instance of the interface. The Property Template can define only PIProperty values, but not the PIProperty names. This is dictated by the PISDK rule that states each PIProperty event name under the same PIProperty node should be unique. Each PIProperty name can be defined explicitly or if not defined, interface assigns the name as – ‘Event_’, where is the current number of events already stored under specific PI Property node. The Property Template usage as follows:

Property[index].Name = Name structure (hierarchy supported) (optional)

Property[index].Value = Value structure

Property[index].Trigger = Trigger expression

Property[index].Translate = true/false (default: false)

where index is an arbitrary 1-based positive number. Specify the value structure in the free text format with the placeholder names contained within the square brackets. The triggering expression must be embedded in the Value Structure or specified through explicit Trigger(s). Specifying multiple placeholders in a single triggering expression is treated as an AND logic and specifying multiple trigger expressions is treated as an OR logic.

Note: If /uobev switch is defined in command line parameter, the SQL batch data source will not have [Pval] and [EU] available as separate columns; instead they are embedded in [Descript] column. The description of Property Template is given in the Property Template Description, below.

Property Template Description

Template Name	Allowed Placeholders in Value	Value Description
Property[#].Name Optional	[TIME] [UNIQUEID] [BATCHID] [PROCEDURE] [UNITPROCEDURE] [OPERATION] [PHASE] [PHASESTATE] [PHASESTEP] [DESCRIPT] [EVENT] [PVAL] [EU] [AREA] [PROCESSCELL] [UNIT] [PHASEMODULE] [USERID] or [USER] or [*,value=”Exact Field”], or [*,value=”Field Mask”], advanced parsing	This property defines the Name structure of the PI Property. The triggering expression or Event Type must be embedded in the value structure. Allowed placeholders are not case sensitive. Due to the requirement that PI Property Names should be unique under the same PI Property If Template Property – Name is not defined, the PI Property names are created automatically by the interface as Event_(Same Node Event Count). Note: Warning, if Name is defined and there is an event which results in PI Property Name already existing in PI Server, then the interface will replace the existing PI Property value with the new one. Note: Each incoming event can trigger multiple Property Templates if it is defined in each as triggering event. In Name property, the hierarchy of names is supported. Example Property[1].Name = Materials\[Event] As result, if the Property Template is triggered then the interface creates under proper Recipe PIProperty – PI Property “Materials” and as child property – the value of [Parameter] placeholder.
Property[#].Value Required	Same as for Name. And [TAG]	This property defines the value structure of the PI Property. The triggering expression or Event Type must be embedded in the value structure. Allowed placeholders are not case sensitive. Due to the requirement that PI Property Names should be unique under the same PI Property Node, the property names are created automatically by the interface (default). Note: Each incoming event can trigger multiple Property Templates if it is defined in each as triggering event. Property Template Value: Defined by user as free text with optional placeholders. Placeholder – is the name of the source column. For each incoming event, placeholder in the template is replaced by corresponding field from the event structure. Note: for SQL data source(s), if /uobev switch is used then there are no explicit columns for [Pval] and [EU], instead, these columns are combined and appended to [Descript] column. Example : Property[1].Value = [BatchID] | event: | [Descript] | val: [Pval] Or using advanced parsing definition: Property[1].Value = [BatchID] | event: [*,value=”State*”] | [Descript] | val: [Pval]
Property[#].Trigger Optional	Same as for Name Property except [TIME]	Defines the triggering expression or Event Type which used to create and populate PI Properties. If trigger is defined, it overrides triggering expression in Value property if defined. Note: There can be multiple triggers defined for a single template property. Note: Interface uses only placeholders embedded into expression to trigger particular template. All free text is omitted and placeholders are treated as with AND logic. Using multiple Triggering expression allows to create OR logic for triggering. Example 1: Property[1].Trigger = [Parameter, value=”State Change”] Property[1].Trigger = [Value, value=”test”] or using mask: Property[1].Trigger = [Parameter, value=”State Ch*”] Property[1].Trigger = [Value, value=”tes*”] Example 2: Using triggering expression with two placeholders: Tag[1].Trigger=[Event, value=”State*] [Pval,value=RUNNING”] This expression will trigger tag template only if both conditions are met.
Property[#].Translate Optional	Values: true/false	If set to true this property allows the Property Template to use the translate map and replace words, phrases found in Value with the custom ones.