How sample projects are upgraded

This section describes what happens to AVEVA sample projects installed on the customer environment, whenever an upgrade is in place for them. In summary:

• ACP and APS projects (E3D) get backed up and replaced with new versions.

• ASP (SEED) and ATP projects will NOT be upgraded.

Please refer to the details below for more information.

Background

Currently, when a new Unified Engineering environment is deployed, the following (latest & compatible) Sample projects are included:

• AVEVA Plant Sample, incorporating:

  • ACP - the AVEVA Catalogue Project containing typical piping components & specifications, structural steelwork, drawings backing sheets and symbols and so on.

  • APS - a sample project with typical project data referencing ACP for catalogue data.

• AVEVA Engineering SEED Sample, incorporating:

  • ASP - the AVEVA Engineering "starter" SEED project that customers update with their own data.

  • ATP - a sample project designed to demonstrate a single example of each key functionality within AVEVA Engineering.

The recommended standard practices for using the AVEVA Plant Sample and AVEVA Engineering SEED Sample projects are fundamentally different.

The sections below describe assumed standard practices and how Sample projects are processed when an AVEVA Unified Engineering environment is upgraded.
Please take careful consideration of this information as certain actions may be required post-upgrade.

AVEVA Plant Sample Catalogue Project (ACP)

The recommended (and assumed) standard practice for new AVEVA Plant customer projects is to reference (foreign) multiple catalogue projects that may or may not include ACP.

In either case, ACP should remain untouched by the customer.

When an AVEVA Unified Engineering environment is upgraded, the existing ACP project is always replaced with the latest compatible version.
Following the recommended standard practice for using ACP means that when an AVEVA Unified Engineering environment is upgraded, the AVEVA catalogue is automatically extended without affecting customer catalogue data.

However, there may be a situation where the standard practice is not followed. Replacing the existing ACP on upgrade would result in the loss of customer catalogue data.

As a safeguard measure, the following occurs when an AVEVA Unified Engineering environment is upgraded to allow the customer to manually move the catalogue data if required:

• The existing ACP project folder contents are moved to a new folder (P:\AVEVAFiles\Engineering\UpgradedSampleProjectsBackup\YYYYMMDDHHMI\ACP)

  In the UpgradedSampleProjectsBackup folder, we retain copies from only the latest three upgrades, to manage disk space usage.

  Note: Copies older than the latest three are automatically deleted.

• The new ACP project is installed to the existing (and empty) ACP folder

We encourage all customers to follow the recommended standard approach for using AVEVA Plant Sample Catalogue Project (ACP) to avoid the need for manual changes.

AVEVA Plant Sample Project (APS)

When an AVEVA Unified Engineering environment is upgraded, the existing APS project is always replaced with the latest compatible version.

Normally replacing any changes in the APS project is not an issue, as the APS is a Sample project only.

An edge-case exception occurs when the APS project is globalized. The globalized APS project will be replaced with a non-globalized APS project. In this scenario, the sole option is to copy the globalized APS project from the latest back-up.

As a safeguard measure, the following occurs when an AVEVA Unified Engineering environment is upgraded to allow the customer to manually reinstate or manipulate sample project data if required:

• The existing APS project folder contents are moved to a new folder (P:\AVEVAFiles\Engineering\UpgradedSampleProjectsBackup\YYYYMMDDHHMI\APS)

• In the UpgradedSampleProjectsBackup folder, we retain copies from only the latest three upgrades, to manage disk space usage.

  Note: Copies older than the latest three are automatically deleted.

• The new APS project is installed to the existing (and empty) APS folder

AVEVA Engineering Sample SEED Project (ASP)

The recommended (and assumed) standard practice for new AVEVA Engineering customer projects is to use ASP as a starter project that customers then update with their own data.

Therefore, ASP will remain untouched by the AVEVA Unified Engineering upgrade process.

Contrary to the approach for ACP, on upgrade of AVEVA Unified Engineering, the existing ASP project is never replaced with a newer version.

When we upgrade the AVEVA Engineering software on an AVEVA Unified Engineering environment to a newer version, customers have the choice to leave ASP as is or to manually apply the updates documented in the AVEVA Engineering release letter to incorporate new objects.

AVEVA Engineering Sample Project (ATP)

When an AVEVA Unified Engineering environment is upgraded, the existing ATP project is never replaced with a newer version.

This is to ensure feature alignment with the originally deployed AVEVA Engineering Sample SEED Project.

If the AVEVA Engineering Sample SEED Project has been manually upgraded by the customer and they wish to use the ATP project to demonstrate new object functionality, then a request can be made to AVEVA to copy the respective ATP project.