Packages and the SCADA Package Admin role

As an AVEVA Enterprise SCADA Package Admin, you can use the Management of Change (MoC) Package tool (dnapackage) to do the following:

• create a package

• add metadata to a package

• add existing datatype editor changesets (RealTime database [RTDB] or display) to an existing MoC package

• link packages to create package dependencies

• unlink packages to remove package dependencies

• view MoC packages

• list MoC packages

• attach files to a package

• extract file attachments from an existing MoC package

• promote a package to the MOCOrchestrator service using the publish command

• install package contents to a system

• roll back a package installed on a system

Use the MoC Package tool (dnapackage) to create a package and the Package Orchestrator software to manage a package.

Note: If you are running the dnapackage tool outside the domain of the MOCOrchestrator service, remote DAL configuration is required to connect to the MOCOrchestrator service.

The MOCOrchestrator service is an internal, back-end process used to store configuration packages, and the MOCAgent service interacts with the MOCOrchestrator service to distribute and roll back packages. Use the Network Management Console (NMC) to view and control the MOCOrchestrator service and the MOCAgent service.

As a group of changesets, the package will enable you to prepare the necessary components for distribution as a single update to systems in other MoC zones.

Notes: RTDB changesets are created by the AVEVA Enterprise SCADA Admin using the DNAChangeset tool. Changes within the changeset can be created using the Advanced Database Editor (ADE) (or a similar tool).

Only completed changesets can be included in a package.

On any one system, you may be working with multiple Package Admins on different changesets simultaneously, as large pipeline companies often have several projects ongoing concurrently. Additionally, you may be working with multiple changesets. For example, you may be working on a multi-week project to install a new station, and then be interrupted to perform an emergency fix for a failed transmitter.

You can roll back a package later if the changes in a package are found to cause problems. A roll back of changes reverses the changes in the end server and automatically reverts the database to the previous stage in the process.

Key Concepts

• The MoC Package tool (dnapackage) can be used to do the following:

  • create a package

  • add metadata to a package

  • add existing datatype editor changesets (RTDB or display) to an existing MoC package

  • link packages

  • unlink packages

  • view packages

  • list packages

  • add file attachments

  • extract file attachments

  • promote a package

  • install a package

  • roll back a package

• The Package tool is used to create a package and the Package Orchestrator software is used to manage packages

• The MOCOrchestrator service is a store of configuration packages

• The MOCAgent service is used to distribute and roll back packages

• Packages are a group of changesets which get promoted to subsequent stages

• Package distribution can be executed as a single update to systems in other MoC zones

• Changesets are created by an AVEVA Enterprise SCADA Admin and can only be included in a package when they are complete

• Multiple changesets can be worked on simultaneously

• A package can be rolled back if it causes problems

• A package rollback will reverse the changes in the end server and revert the database and display file(s) to the previous state

Key Tasks

• Understanding the MoC package tool

• Creating a new MoC package

• Adding metadata to an MoC package

• Adding existing datatype editor changesets (RTDB or display) to an existing MoC package

• Linking packages to create package dependencies

• Unlinking packages to remove package dependencies

• Viewing the contents or summary of an MoC package

• Listing MoC packages

• Attaching files to an existing MoC package

• Extracting file attachments from an existing MoC package

• Publishing a MoC package

• Applying the MoC package contents to a system

• Rolling back the MoC package contents on a system