Required Configuration

Configure the alarms and events within InTouch or Application Server. All tags must adhere to the AVEVA Batch Management tag structure for mapping units and connections to a batch. Only tags that start with a unit or connection name can be mapped to a batch. Tags that cannot be mapped to a batch are not associated to the alarms report. In order to determine the part of the "tagname" that is a unit or connection name, the "tagname" must have one of the following three delimiters after the unit or connection name (.-#) when written to the alarm database. For example, "Reactor1.Temp.Target" would map to unit "Reactor1".

The # delimiter was added to support the AVEVA Batch Management Phase Application Objects which are created when a process model is imported into Application Server. These Phase object "tagnames" do not typically have a delimiter between the unit and phase name. The AVEVA Batch Management IDE Import utility has an option to add the # delimiter to the "tagname" (between the unit and phase name) so the object alarms are eligible to be reported upon.

Note: Because the # character is legal to be used in the AVEVA Batch Management Process Model unit/connection name, there is a very rare chance of a false-positive alarm association. To avoid this, make sure your units/connections that use the # character do not match any of your other units/connection when you truncate it before the #. As an example, don't name your units Unit1 and Unit1# in the Process Model.

For more information on the AVEVA Batch Management tag structure, see Chapter 4, "Process Modeling."