Version Control and Audit Trail (VCAT) has features you can use to determine if database object versions were incremented as a result of an upgrade or because of user configuration changes.
To use Version Control histories and comparisons to determine which version changes are due to an upgrade of DeltaV software, you must have followed the upgrade instructions in the root directory of the DeltaV installation disk #1.
Synchronizing the VCAT database after upgrading DeltaV software can increment the VCAT version of configuration objects. Incrementing the version maintains the history on changes made by the DeltaV Database Migration Utility, which is run during an upgrade. Synchronizing VCAT also catalogs any new elements of the configuration introduced in the latest version of the DeltaV software (for example, new functionality).
These version changes are always visible in subsequent VCAT comparisons, but are not marked as being due to an upgrade unless you have performed the following tasks:
You must perform these tasks to mark all version changes resulting from the upgrade. If you do not perform these tasks some changes caused by the upgrade do not appear until you check items out and back in. You will be unable to easily determine if these changes are the result of configuration changes or the upgrade.