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

AVEVA™ Production Management

Master Data Management workflow

  • Last UpdatedApr 03, 2025
  • 2 minute read

The Master Data Management workflow consists of six phases as shown in the following diagram.

Master data management workflow with its six phases from Configure, Load, Detect Changes, Notify admin, Manage conflicts, Resolve conflicts, and then repeat from Load.

Configure an MDM scenario

In Studio, you configure one or more Master Data Management scenarios. Each scenario details the following:

  • Model (equipment, personnel, or material)

  • Location of the B2MML file

  • Email addresses (for notification)

  • XML style sheets

  • Polling Interval

Load the scenario

For each configured scenario, AVEVA™ Production Management performs the following steps:

  • Gets the Master B2MML file from the configured directory.

  • Applies the Master XML style sheet to the Master B2MML file.

  • Gets AVEVA Production Management configuration as a B2MML file.

  • Applies the AVEVA™ Production Management XML style sheet to the AVEVA™ Production Management B2MML file.

Detect changes

After the XML files are loaded, AVEVA™ Production Management compares the two for differences. For each difference, AVEVA™ Production Management inserts a conflict into its Master Data Management service. A conflict represents the following:

Element

Description

Operation

The type of operation to be performed on the AVEVA™ Production Management configuration, such as Add, Rename, Update, Delete.

Model

The model that this conflict relates to, for example: Equipment, Personnel, or Material.

Type

The type of entity that the conflict is relating to. for example Class, Class Property, Model, Model Property, or Class Association.

Subject

The relevant location to perform the operation on. For example, if the operation is an Add, this details the parent item. If the operation is an Update, this details the actual item.

Object

Details the value of the conflict. For example, for an Update, this contains the new value. For an Add, this contains the name.

Meta Data

Contains metadata about the object.

Notify admin

For each scenario, if there are any differences, AVEVA™ Production Management emails a report of the conflicts to the configured email addresses.

Embedded Image (65% Scaling) (LIVE)

Manage conflicts

You can manage conflicts in the conflict resolution interface within AVEVA™ Production Management.

Resolve conflicts

When you want to resolve a conflict, AVEVA™ Production Management provides you with the following options.

Options

Description

Auto Resolve

Resolves the conflict and all child conflicts by automatically changing your project configuration.

Mark Resolved

Use this option when you have changed the configuration manually and want to mark the conflict as resolved.

Ignore

Marks the conflict as ignored and subsequent synchronizations do not show the conflict again.

Unignore

If you have previously ignored a conflict, this option un-ignores the conflict and the conflict appears on every synchronization until you have completed one of the above three options on it.

In This Topic
TitleResults for “How to create a CRG?”Also Available in