Initialization file reference

evtdir=<path>

Required for event file data sources, specifies the folder that contains the event files. Example:

Source[1].evtdir = D:\TEST\RELEASE\test_1

excludestates=<list>

(Optional) Specifies a comma-separated list of phase states to ignore. Not case-sensitive. You can use wildcards for matching. Examples:

excludestates=COMPLETED,AB*ING,IDLING, COMPLE*

opcserver=<server name>

Optional for OPC alarms and events data source. Specifies the name of the alarms and events server, if you are not using the default server.

skipphases=<list>

(Optional) Specifies a comma-separated list of phases to ignore. Not case-sensitive. You can use wildcards for matching. The interface checks the list against the [Phase] field (batch recipe) or [PhaseModule] field (equipment). Examples:

skipphases=phase_1, ph*2,ph_test*, ph*ort*

skiprecipes=<list>

(Optional) Specifies a comma-separated list of recipes to ignore. Not case-sensitive. You can use wildcards for matching. The interface checks the list against the corresponding event field, depending on recipe type, as follows: Examples:

skiprecipes=recipe_1, rec*2,PRC_PAINT*, UP_TEST:2

skipunits=<list>

(Optional) Specifies a comma-separated list of units to ignore. Not case-sensitive. You can use wildcards for matching. The interface checks the list against the corresponding [Unit] field. Example:

skipunits = unit_1, u*2

NAME

[AREA]
[BATCHID]
[COMMENT]
[DESCRIPT]
[EU]
[EVENT]
[OPERATION]
[PHASE]
[PHASEMODULE]
[PHASESTATE]
[PHASESTEP]
[PROCEDURE]
[PROCESSCELL]
[PVAL]
[TIME]
[UNIQUEID]
[UNIT]
[UNITPROCEDURE]
[USERID]

[*,value=”Exact Field”],
[*,value=”Field Mask”],
advanced parsing

(Optional) Specifies how the property is to be named. You can use an expression to configure the name, but note that the resulting name must be unique. If two different name templates generate the same name, the property value will be overwritten and no error is logged. If you omit the name setting, the interface assigns a default name ("Event_n").

By default, properties are created at the level of the batch hierarchy that triggers their creation. To create a property at the top of the hierarchy, regardless of where it was triggered, specify "$" at the beginning of the expression that defines the name. For example: Property[1].Name = $\[Event]

VALUE

Same as NAME, plus [TAG]

(Required) Specifies the value to be stored in the property. To compose the value, you can use free text plus valid placeholders.

Basic example:

Property[1].Value = [BatchID] | event: <State*> | [Descript] | val: [Pval]

Advanced parsing:

Property[1].Value = [BatchID] | event: [*,value=”State*”] | [Descript] | val: [Pval]

TRIGGER

Same as NAME, except not [TIME]

Specifies the event that causes the interface to generate the property. To define a trigger, specify an expression composed of a placeholder and value. When the interface detects the specified value in the placeholder, it generates the property. You can specify multiple triggers for a single property. If you specify the triggers on a single line, the property is generated only when all the conditions are met (logical AND). If you specify the trigger expressions on separate lines, the property is generated when any of the conditions is met (logical OR). Examples:

Property[1].Trigger = [Parameter, value=”State Ch*”]
Property[1].Trigger = [Value, value=”tes*”]
Property[1].Trigger=[Event, value=”State*] [Pval,value=RUNNING”]

TRANSLATE

TRUE or FALSE

To specify that the value is to be translated according to the translation map you define set this setting to TRUE.

TYPE

STRING

FLOAT

INTEGER

AUTO

Specifies the data type for the value. To configure the interface to evaluate the data and assign the data type accordingly, specify AUTO.

CATEGORY

Same as NAME

(AF only) Specifies the AF category to be assigned to the attribute.

UOM or ENGUNITS or

EU

Same as NAME

Specifies the units of measure for the attribute. (See /UOBEV note for VALUE setting, above.)

ANNOTATION

Same as NAME

Annotate the tag using a string

ANNOTATION2

Same as NAME

Annotate the tag using a name/value object.

DESCRIPTOR

Same as NAME

Specifies how the descriptor field of the tag is populated.

EU

Same as NAME

Specifies the engineering units for the tag.

NAME

[AREA]
[BATCHID]
[COMMENT]
[DESCRIPT]
[EU]
[EVENT]
[OPERATION]
[PHASE]
[PHASEMODULE]
[PROCEDURE]
[PROCESSCELL]
[PVAL]
[UNIQUEID]
[UNIT]
[UNITPROCEDURE]
[USERID]

[*,value=”Exact Field”],
[*,value=”Field Mask”],
advanced parsing

Specifies how the tag is to be named.

PHASEALIAS

Same as NAME

Configures the naming convention for the phase module alias generated by the interface. The unit alias refers to the MDB module or AF asset representing the phase module associated with the incoming event.

TRIGGER

Same as NAME, except not [TIME]

Specifies the event that causes the interface to generate or update the tag. To define a trigger, specify an expression composed of a placeholder and value. When the interface detects the specified value in the placeholder, it generates or updates the tag. You can specify multiple triggers for a single tag. If you specify the triggers on a single line, the tag is generated only when all the conditions are met (logical AND). If you specify the trigger expressions on separate lines, the tag is generated when any of the conditions is met (logical OR).

TRANSLATE

TRUE or FALSE

To specify that tag settings are to be translated according to the translation map you define, set this setting to TRUE.

TYPE

STRING

FLOAT

INTEGER

AUTO

Specifies the data type for the tag. To configure the interface to evaluate the data and assign the data type accordingly, specify AUTO.

UNITALIAS

Same as NAME

Configures the naming convention for the unit alias generated by the interface. The unit alias refers to the MDB module or AF asset representing the unit associated with the incoming event.

VALUE

Same as NAME, plus [TAG] and [TIME]

(Required) Specifies the value to be stored in the tag. To compose the value, you can use free text plus valid placeholders.

VALUE

[AREA] [BATCHID] [COMMENT] [DESCRIPT] [EU] [EVENT] [OPERATION] [PHASE] [PHASEMODULE] [PHASESTATE] [PHASESTEP] [PROCEDURE] [PROCESSCELL] [PVAL] [TIME] [UNIQUEID] [UNIT] [UNITPROCEDURE] [USERID] [*,value=”Exact Field”], [*,value=”Field Mask”], advanced parsing

(Required) Specifies the name of the event frame to be linked to by the triggering event frame. To compose the value, you can use free text plus valid placeholders.

Basic examples:

DCSTemplate[1].Value = [Pval] DCSTemplate[1].Value = [BatchID] | event: <State*> | [Descript] | val: [Pval]

Advanced parsing:

DCSTemplate[1].Value = [BatchID] | event: [*,value=”State*”] | [Descript] | val: [Pval]

TRIGGER

[AREA] [BATCHID] [COMMENT] [DESCRIPT] [EU] [EVENT] [OPERATION] [PHASE] [PHASEMODULE] [PHASESTATE] [PHASESTEP] [PROCEDURE] [PROCESSCELL] [PVAL] [UNIQUEID] [UNIT] [UNITPROCEDURE] [USERID] [*,value=”Exact Field”], [*,value=”Field Mask”], advanced parsing

Specifies the event that causes the interface to generate the link. To define a trigger, specify an expression composed of a placeholder and value. When the interface detects the specified value in the placeholder, it generates the link. You can specify multiple triggers for a single link. If you specify the triggers on a single line, the link is generated only when all the conditions are met (logical AND). If you specify the trigger expressions on separate lines, the link is generated when any of the conditions is met (logical OR). Examples:

DCSTemplate[1].Trigger = [Descript, value=”WorkflowID”] DCSTemplate[1].Trigger = [Parameter, value=”State Ch*”] DCSTemplate[1].Trigger = [Value, value=”tes*”] DCSTemplate[1].Trigger=[Event, value=”State*] [Pval,value=RUNNING”]