Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

Model Integrity Tool

  • Last UpdatedOct 24, 2025
  • 3 minute read

Use the Model Integrity Tool to detect, analyze, and resolve structural and referential inconsistencies in the data model.

By default, the application performs a database check for broken references between database elements when launched. For example, an element may have been deleted without an associated reference being removed.

On the Data Model tab, in the Evaluation group, select Modify Integrity Tool to display the Model Integrity Tool window.

The Model Integrity Tool window displays a list of issues found during the database check. Select the required check boxes to fix the issues.

The Processing Model Integrity Tasks window displays the progress of the issue fixing process.

If the database check does not identify any issues, a message displays.

Repair invalid database references

In rare circumstances, project files can become corrupted, resulting in invalid Dabacon references within Resource Description Framework (RDF) structures. When the application is launched, the broken references may not be handled correctly, which can cause certain data to be hidden from the main code. For example, a class association might appear without its inverse.

The application may process the broken items unexpectedly, leading to inconsistencies. For example, a class association which displays in the attributes collection of a class in the Properties window, even though it lacks a valid inverse or reference.

If invalid database references are found when the application is launched, a warning message displays summarizing the problem.

The Model Integrity Tool window can be used to repair invalid database references. Data Integrity Checking (DICE) validation can also be used to determine project issues.

LOV Label/value issues

Focuses on List of Value (LOV) data cleanup and consistency, and addresses the following typical issues:

  • Trim Spaces: Removes leading and trailing spaces from LOV labels and values.

  • Ensure Consistency: Aligns LOV labels with their corresponding values, using the value as the authoritative source.

  • Remove Duplicates: Eliminates repeated LOV entries, retaining only the first valid record.

Cardinality Violations

Removes all irrelevant records beyond the first valid entry with the following criteria:

  • Single Instance Enforcement: Ensures attributes only have one record. For example, maximum value and minimum value attributes.

  • Duplicate Detection: Uses the first attribute instance when multiple instances are found.

Clean and compress Identity data

Removes invalid Identity data, this issue is caused by an historic bug.

Clean and compress LOV item data

Removes orphaned LOV items which no longer reference an owning LOV, this issue is caused by an historic bug.

Clean and compress Non Default LOV data

Removes orphaned non-default LOV data for which the owning LOV has been deleted from an attribute on its owning class. The original non-default LOV implementation propagated data to child classes, but subsequently failed to clean-up data.

Clean Domain and Range

Addresses domain and range records, and validates them according to the following criteria:

  • Single Instance Enforcement: Uses the first domain and/or range record when multiple instances are found.

  • Cleanup Action: Removes all irrelevant records beyond the first valid entry.

Duplicate LOV

Removes duplicate LOVs.

Remap item URIs (Not backward compatible)

Resolves a blank node URI data issue by remapping the node.

The issue was that some objects were created with RDF Blank Node URIs (for example, _:bNNNNNNNN), which caused issues during import/export, the URIs were either omitted or resulted in import errors.

The resolution remaps Blank Node URIs from _:bNNNNNNNN to item:bNNNNNNNN, this ensures consistent handling across the import/export processes.

Remove legacy Identity data

Removes identity data from the original implementation of identities which is now deprecated and no longer visible. Identities were only used internally and were only visible based using an environment variable setting. The data may remain in the project.

Related Links
TitleResults for “How to create a CRG?”Also Available in