---
pdfexport: true
alias: tutorials-change-package-prerequisites
description: "Prepare connected environments, access, and Master Data for Change Package scenarios"
---

# Prerequisites

Complete the following preparation before starting a Change Package scenario. Each scenario identifies the required source and destination MES versions, deployment configuration, and Master Data.

## Customer Environments

Prepare the source and destination Customer Environments for the selected scenario:

- Confirm you have access to the destination Critical Manufacturing MES instances before starting the scenario.
- Confirm that the source and destination Customer Environments are registered in Customer Portal.
- Ensure that each environment is deployed remotely using one of the available remote targets and belongs to an infrastructure with a connected Infrastructure Agent, so it is reachable.
- Confirm that each environment has an active Critical Manufacturing MES license that includes the **Global Data Orchestrator** module.
- Confirm that the destination runs the MES version required by the selected scenario.
- Confirm that the Local Customer Environment ID in the source system identifies the source Customer Environment.

## Permissions

Use accounts with the following access:

- In the source environment, permission to show, create, edit, verify, set effective, and publish **Change Packages**.
- In Customer Portal, permission to create and manage **Master Data Deployment Plans**, view **Transport Packages**, inspect **Master Data Deployment Instances**, and initiate manual deployments or approvals when the scenario requires them.
- In the destination environment, permission to view the generated **Master Data Package** and its execution results.

## Master Data

Prepare the Master Data required by the selected scenario in the source environment. Unless the scenario states otherwise:

- Confirm that non-versioned objects are Active and versioned objects are Effective.
- Confirm that the objects are exportable and can be included in a **Change Package**.

For the [[tutorials-change-package-basic-flow]] scenario, prepare the effective `Belgas [A]` **BOM** and the dependencies displayed when you add it to the **Change Package**.

## Master Data Deployment Plan

When you create the **Master Data Deployment Plan**, add only the destination Customer Environments as **Master Data Deployment Plan Items** in Customer Portal. The source Customer Environment does not need to be added as a **Master Data Deployment Plan Item**.

Obtain the Secret reference from your System Administrator before creating the **Master Data Deployment Plan**. The referenced Secret must already exist and be accessible to the destination deployment process. Customer Portal does not create the Secret or transfer its value.

!!! info

    For more information, see the [Global Data Orchestrator](https://portal.criticalmanufacturing.com/Help/global-data-orchestrator/) documentation.

    For encryption key requirements and Secret setup, see [[operation-guide-global-data-orchestrator-encryption]].

## Before You Start

Confirm that all prerequisites are complete before continuing with the selected scenario.