Note: Each incoming event can be used to create/populate multiple PI Tags, if it is defined as triggering event in multiple Tag Templates. Same as for This property defines the event value structure for AlarmTag[#].Value Name property the specific PI Point. Allowed placeholders are not and case sensitive. Required The event timestamp is taken from the incoming [TIME] event [Time] field. [TAG] String Defines the type of the PI Point to be created and AlarmTag[#].Type how to treat the events written to this tag. Float Required Integer Same as for Defines the triggering expression which used to AlarmTag[#].Trigger Name property create and populate PI tags. If trigger is defined, it overrides triggering expression in Name property if Optional defined. Note: There can be multiple triggers defined for a single template tag. 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: Tag[1].Trigger = [Attribute, value=”HI*”] Using triggering expression with two placeholders: Tag[1].Trigger=[Event, [Attribute, value=”Alarm”] value=”HI*”] This expression will trigger tag template only if both conditions are met. Same as for This property defines the unit level alias name AlarmTag[#].Alias Name property structure for specific template tag. The contained field can be defined as exact phrase or mask. If Optional resulting Alias Name contains illegal characters such as * ? | ` then these characters are ‘ “ replaced by Optional sub [module] “_” character. path can be specified within alias name. symbol “\” should be used to separate parent\child modules and symbol should be used to separate module “|” path and the actual alias name. Default: uses Name property as [module] level alias name. Note: The names for PI Aliases must be unique. Starting from version 1.0.2.0, interface allows creating aliases on PI modules based on absolute module path. This can be achieved by placing the sign as the first module in ‘$’ module path. stands for root module. If ‘$’ /smp=<Start Module Path> switch is used – then is the leaf node of the hierarchy ‘$’
Note: Each incoming event can be used to create/populate multiple PI Tags, if it is defined as triggering event in multiple Tag Templates. AlarmTag[#].Value Required Same as for Name property and [TIME] [TAG] This property defines the event value structure for the specific PI Point. Allowed placeholders are not case sensitive. The event timestamp is taken from the incoming event [Time] field. AlarmTag[#].Type Required String Float Integer Defines the type of the PI Point to be created and how to treat the events written to this tag. AlarmTag[#].Trigger Optional Same as for Name property Defines the triggering expression which used to create and populate PI tags. If trigger is defined, it overrides triggering expression in Name property if defined. Note: There can be multiple triggers defined for a single template tag. 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: Tag[1].Trigger = [Attribute, value=”HI*”] Using triggering expression with two placeholders: Tag[1].Trigger=[Event, value=”Alarm”] [Attribute, value=”HI*”] This expression will trigger tag template only if both conditions are met. AlarmTag[#].Alias Optional Same as for Name property This property defines the unit level alias name structure for specific template tag. The contained field can be defined as exact phrase or mask. If resulting Alias Name contains illegal characters such as * ‘ ? | ` “ then these characters are replaced by “_” character. Optional sub [module] path can be specified within alias name. “\” symbol should be used to separate parent\child modules and “|” symbol should be used to separate module path and the actual alias name. Default: uses Name property as [module] level alias name. Note: The names for PI Aliases must be unique. Starting from version 1.0.2.0, interface allows creating aliases on PI modules based on absolute module path. This can be achieved by placing the ‘$’ sign as the first module in module path. ‘$’ stands for root module. If /smp=<Start Module Path> switch is used – then ‘$’ is the leaf node of the hierarchy