Integration Assistant Project Analysis Report

The Integration Assistant's Project Analysis Report presents a list of discrepancies detected in a Plant SCADA project that need to be addressed prior to integration.

The report is located in the following directory:
%ProgramData%\AVEVA Plant SCADA Integration Assistant\Reports

The following is the complete list of the issues that may appear in the report (if detected).  

Project

The following is reported at a project level.

• The project has duplicate alarm categories.

• The project includes unsupported built-in labels.

• The project has labels that clash with values used internally.

• The project has include (text) files (@<filename>.cii) which are not supported.

• The project includes Equipment Types with States configured. States are not supported.

• There are tags starting with a digit.

Equipment types and instances

A Plant SCADA project requires a correctly configured equipment hierarchy to successfully integrate with Application Server.

• Each Equipment Type needs to contain valid Items with supported elements.

• Each Equipment Type needs at least one associated Instance, otherwise it will not be integrated.

• Each Item needs to have a unique name within an Equipment Type.

• Expressions are not supported in Item names.

• Items with a name that start with an underscore (_) or backslash (\) will be integrated as hidden attributes.

• If an Equipment Instance is not associated with a valid Equipment Type, it will be integrated into Application Server using a generated template.

• Equipment Type names that are longer than 28 characters are truncated.

• If an Equipment Type, Item, or Instance have invalid characters in their name, the character is replaced with an underscore (_).

• Equipment Types/Instances have a limit of 500 Items. Items in excess of this limit will not be integrated.

• Instances with no associated variable, alarm or trend tags are integrated using the $PSBaseTemplate.

• If there are Equipment Types containing Items created by Equipment Editor that do not have a user defined Item name, the Items will not be integrated.

Variable tag elements

If an Item has a variable tag defined as an element, it must meet the following requirements. 

• A variable tag must specify a valid data type. If an unrecognized data type is used, or the data type definition contains an expression, the variable tag will not be integrated. 

• A variable tag will not be integrated into Application Server if its data type is defined as ULONG. 

If you have manually added any additional variable tags for a piece of equipment directly in Plant SCADA Studio, make sure they use an Item Name that is unique for the associated Equipment Type.

You can only associate one variable tag element with each Item. Any additional variable tag elements will not be integrated.

Alarm elements

If an Item has any alarms defined as an element, they need to adhere to the following conditions.

• Digital alarms and time stamped digital alarms

  • If an Item has a digital alarm defined as an element, the Item's variable tag element needs to have its Data Type set to DIGITAL.

  • If a digital alarm is defined as an element, it needs to have either Variable Tag A or Variable Tag B configured correctly. To be valid, the alarm needs to reference the Item's variable tag element.

  • If a digital alarm has both Variable A and Variable B defined, both need to point to items on the equipment instance that the alarm is defined on.

• Analog alarms and time stamped analog alarms

  • If an Item has an analog alarm defined as an element, the Item's variable tag element cannot have its Data Type set to DIGITAL or STRING.

  • If an analog alarm is defined as an element, it needs to have its Variable Tag field configured correctly. To be valid, the alarm needs to reference the Item's variable tag element.

  • If an analog alarm uses an expression in either the Variable Tag or Setpoint field, it needs to be suitable for conversion to QuickScript. For more information, see Support for expressions in QuickScript.

  • If an analog alarm has delays configured for any alarm limits (High High Delay, High Delay, Low Delay, Low Low Delay), make sure they are all set to the same delay period. Application Server will only support one delay period for alarm limits.

• Advanced alarms

  If an Item has an advanced alarm defined as an element, the Expression field needs to include an expression that can be converted to QuickScript. For more information, see Support for expressions in QuickScript.

• Multi-digital alarms

  Application Server does not support multi-digital alarms. However, multi-digital alarms that only have two states configured can be converted to a digital alarm.

  • If an Item has a multi digital alarm defined as an element, the Item's variable tag element needs to have its Data Type set to DIGITAL.

  • If an Item has a multi digital alarm defined as an element, only use Variable Tag A. Leave Variable Tag B and Variable Tag C empty. The alarm will not be integrated if more than one variable tag is configured.

  • Variable Tag A needs to be configured correctly. To be valid, it needs to reference the Item's variable tag element.

  • Trigger 000 and Trigger 00A should be set to '0' or '1' and should not be the same value.

  • State 000 and State 00A need to have distinct values. The alarm will be integrated, but 'True' and 'False' labels will be used as default values.

• Unsupported alarms

  The following alarms are not supported in Application Server and will not be integrated:

  • Time-stamped alarms

  • Double point status alarms

  • Multi-digital alarms with more than one source tag configured

  • Advanced alarms containing Cicode functions that cannot be converted to QuickScript.

Trend tag elements

If an Item has a Trend Tag defined as an element, the Expression field needs to include an expression that can be converted to QuickScript. For more information, see Support for expressions in QuickScript.

Trend triggers are also not supported in Application Server. 

SPC tag elements

If an Item has an SPC Tag defined as an Element, the SPC tag will not be integrated into Application Server.

Accumulators

If an Equipment Type has an accumulator defined as an Item, the accumulator will not be integrated into Application Server.

Note: Some unsupported fields can be optionally added to a special metadata attribute. For more information, see Plant SCADA fields imported as metadata.