Understanding Management of Change (MoC)

Management of Change (MoC) provides the ability to safely collect all the changes that logically represent new functionality and configuration. It greatly reduces the manual effort involved in promoting those changes through an AVEVA Enterprise SCADA Enterprise Distributed System. The changes may include database configurations, display edits, Application Calculation Engine (ACE) code edits, and any other types of changes that are supported by MoC.

The collection of changes, referred to as a changeset, can then be packaged, deployed, and applied to a destination AVEVA Enterprise SCADA Enterprise Distributed System in a safe, automated manner, with minimal impact to operations. Typically, the process involves creating changes in a development environment, deploying those changes to a testing environment, and then, after testing is complete, applying the changes to the production environment. MoC package contents can also be rolled back, uninstalling the changes in all changesets in the reverse order they were applied.

The following is an example system illustrating the change promotion and rollback process.

MoC includes two levels of functionality:

• The Package Orchestrator is the top level and can be thought of as an orchestrator of package deployment. It is used to move the package from one AVEVA Enterprise SCADA system to the next. It sets the state of a package and controls which systems the package can be deployed to by following rules defined by a state machine.

• Editor Suites are the bottom level and are made up of different data types. Each data type has its own Editor Suite that consists of version control and editor processes. Typically, there is a process for editing that locks the data type and associates the changes with a changeset. For example, RealTime configuration data can be changed interactively using the Advanced Database Editor (ADE). For more information, refer to Specify a Management of Change (MoC) changeset using AVEVA Enterprise SCADA tools.

Key Concepts

• MoC will allow you to safely collect and group changes together.

• The manual effort to promote changes through the AVEVA Enterprise SCADA Enterprise Distributed System is minimal.

• MoC supports the following types of changes:

  • Database configurations

  • Display edits

  • ACE code edits

• A collection of changes is called a changeset.

• Changesets can be grouped together into a package.

• Packages are deployed and applied to an AVEVA Enterprise SCADA Enterprise Distributed System with minimal impact to operations.

• Changes are created in development, deployed to testing, and applied to production.

• Package contents can be rolled back.

• The Package Orchestrator is used for package deployment.

• Editor Suites are made up of data types and control processes and versioning.

Key Tasks

• Understanding the MoC workflow

• Executing the MoC workflow

• Understanding MOCOrchestrator service

• Understanding MOCAgent service

• Locating logs/events of MoC data changes