expression, which can be defined as Event Type itself (Example below: event type – Comment) or combination of placeholders, which is treated with AND logic. Providing multiple trigger expressions as below is treated with OR logic. Tag[12].Name = [Unit] Tester Tag[12].Value =[pval]-[Event] Tag[12].Type = string Tag[12].Trigger = [Event, value=”Report”] Tag[12].Trigger = [Event, value=”State Change”] Tag[12].Trigger = Comment Tag[12].unitalias = Testing [Unit] Tag[12].phasealias = Testing phase alias Note: In this example we do not have the [PhaseModule] placeholder or actual phase name embedded in the Tag Template Name. Therefore, phasealias will not be created or verified. Assume that we have 4 incoming events: Event 1 contains the following fields populated as: [Time]=08/12/2008 13:00:05.123 [Event]=Report [Unit]=U101 [Pval]=123.456 Event 2 contains the following fields populated as: [Time]=08/12/2008 15:20:01.998 [Event]=State Change [Unit]=U101 [Pval]=HOLDING Event 3 contains the following fields populated as: [Time]=08/12/2008 18:49:12.020 [Event]=Comment [Unit]=U101 [Pval]=Discard Product and Event 4 contains the following fields populated as: [Time]=08/12/2008 21:49:14.025 [Event]=Comment [Unit]= [Pval]=Discard Product As result, the Tag Template only gets triggered for the first 3 events. The last incoming Event 4 does not have the [Unit] field populated; therefore the Tag Name structure is not complete and cannot be processed. All events result in tag name as and tag “U101 Tester” unit level alias name as “Testing U101”. The resulting events are stored to PI as follows: Event TimeStamp Event Value (string) 08/12/2008 13:00:05.123 123.456-Report 08/12/2008 15:20:01.998 HOLDING-State Change
expression, which can be defined as Event Type itself (Example below: event type – Comment) or combination of placeholders, which is treated with AND logic. Providing multiple trigger expressions as below is treated with OR logic. Tag[12].Name = [Unit] Tester Tag[12].Value =[pval]-[Event] Tag[12].Type = string Tag[12].Trigger = [Event, value=”Report”] Tag[12].Trigger = [Event, value=”State Change”] Tag[12].Trigger = Comment Tag[12].unitalias = Testing [Unit] Tag[12].phasealias = Testing phase alias Note: In this example we do not have the [PhaseModule] placeholder or actual phase name embedded in the Tag Template Name. Therefore, phasealias will not be created or verified. Assume that we have 4 incoming events: Event 1 contains the following fields populated as: [Time]=08/12/2008 13:00:05.123 [Event]=Report [Unit]=U101 [Pval]=123.456 Event 2 contains the following fields populated as: [Time]=08/12/2008 15:20:01.998 [Event]=State Change [Unit]=U101 [Pval]=HOLDING Event 3 contains the following fields populated as: [Time]=08/12/2008 18:49:12.020 [Event]=Comment [Unit]=U101 [Pval]=Discard Product and Event 4 contains the following fields populated as: [Time]=08/12/2008 21:49:14.025 [Event]=Comment [Unit]= [Pval]=Discard Product As result, the Tag Template only gets triggered for the first 3 events. The last incoming Event 4 does not have the [Unit] field populated; therefore the Tag Name structure is not complete and cannot be processed. All events result in tag name as “U101 Tester” and tag unit level alias name as “Testing U101”. The resulting events are stored to PI as follows: Event TimeStamp Event Value (string) 08/12/2008 13:00:05.123 123.456-Report 08/12/2008 15:20:01.998 HOLDING-State Change
PI_EMDVB_3.0.1.76.docx