See here for advanceinfo on Deployment Units 

Introduction

Deployment Units (DUs) simplify the planning of the deployment phase of the migration. They allow users to be split into groups which will typically represent a location or department that is being migrated during a specific period.

By default, DUs are enabled for User Migrations only but also apply to the Applications, Devices, Mailboxes and Bespoke modules.

TABLE OF CONTENTS

• Introduction
• Enabling DUs at the Module Level
• Creating a New Deployment Unit
  • Information Required for a New DU
• Deployment Unit Tabs
  • Details
  • Discovery
  • Schedule
  • Schedule Config
  • Defects
  • Tasks
  • Contacts
  • Surveys
  • Dependencies
  • Attachments
  • History
• Further Support

Enabling DUs at the Module Level

DUs are enabled in the Administration section for supported modules:

Step	Example
Switch to Administration and choose a module. User Migrations, Applications, Devices, Mailboxes, and Bespoke support DUs. Click DeployUnit & Self-Schedule in the Surveys, Sign-Offs & Self Schedule panel.
Click the toggle at the top to switch the DU status from Disabled to Enabled (1).  Click Save Changes (2).

Creating a New Deployment Unit

Switch to the Deployment Unit module and click click the New button in the Toolbar:

Information Required for a New DU

The Create New Deployment Unit wizard requires the information specified below.  Once populated, click the New button at the bottom to create the DU.

Target Module: Choose from a list of supported modules. By default, User Migrations is the only module enabled. Deployment Unit: The name of the DU. For example, this could be an area, campus, office or building. Location: The geographic location of the DU. Process: Choose the correct process for the project workflow. In most cases, this will be the default process to signify a newly created DU. Sub Process: Choose the appropriate subprocess for the new DU.

Deployment Unit Tabs

Details

The Details tab contains the core information about the DU:

Discovery

The Discovery section contains information about the DU that isn't related to the scheduling, such as the address and primary contacts.  By default, ManagementStudio ships with three tabs:

• Site Information: Site address, contacts, nature of the site, DR site, and operating hours
• PPE & Safety: Health and safety summary, contacts, site access pre-requisites, allergy information, and site restrictions
• Asset Shipping: Information about assets shipped to site

For further information about managing the Discovery tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000108621

Schedule

The Schedule tab is prefixed by the DU's target type.  For example, the tab title for a user-based DU would be User Migrations Schedule.

The Migrations Schedule tab provides a summary of all the items belonging to the DU, including the status, and start/end-time of the migration.

For further information about working with the Schedule tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000110582

Schedule Config

The Deployment Unit schedule is by default based on a globally defined schedule.  The Schedule Config tab is used to apply the global schedule or to create a customised local schedule, specify days that should be excluded from the schedule, and view slot utilisation to maximise engineering resource.

The tab consists of five core sections:

• Toolbar (1)
• Slot Configuration Grid (2)
• Suspended Days Grid (3)
• Slot Utilisation (4)
• Slot Calendar (5)

For further information about working with the Schedule Config tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000110583

Defects

Defects are used throughout ManagementStudio to track issues that impact the project.  For Deployment Units, this could be an issue with an application that's required by a user in that DU or a site that doesn't meet particular health and safety requirements (e.g. not nut-free).

The Defects tab is used to view and manage the defects associated with the DU, including adding new defects, attaching existing defects, and viewing the defect details.

For further information about working with the Defects tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000108622

Tasks

Tasks are a versatile way for project administrators to record and track outstanding activities with a Deployment Unit.  Project users that are assigned to a task will be notified by ManagementStudio.  The Tasks tab is used to view and manage all tasks associated with the DU.

For further information about working with the Tasks tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000122464

Contacts

Individuals that are involved with the deployment for a particular site or area are linked to the DU in the Contacts tab. This could be the Site Manager, Office Administrator or Health and Safety Coordinator. Linking a contact makes it easier for a project user to identify primary contacts for the deployment phase and access key contact information, such as email and telephone numbers.

A DU can have one or more contacts linked to it.

For further information about working with the Contacts tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000108623

Surveys

Surveys are web-based forms that are used to gather additional information about a DU from users that don't have access to the ManagementStudio interface.  For example, the project team are creating a new DU for the Trentham office and require information regarding location, office opening times, and PPE to build the DU schedule.  The primary contact will receive an email that invites them to complete the information via ManagementStudio's web portal.

In this example, the information returned is located in the Discovery tab, providing the project team with quick access to real-time information.

For further information about working with the Surveys tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000108626

Dependencies

A DU might have several dependencies that could impact the rollout.  For example, before upgrading a site to the latest version of Windows, a new link needs to be installed to support the deployment method.  The Dependencies tab lists all the items that a DU is dependent on and the status.

In addition, the Dependencies tab will also list the other objects that the DU is a dependency of. In the example above, the DU ST4-Trentham is a dependency of Ea-Cambridge. Viewing the Cambridge DU (below) will show the Trentham DU as a primary dependency in addition to all the children dependencies. This enables the project team to fully manage and track all activities related to the deployment.

For further information about working with the Dependencies tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000114086

Attachments

Whilst preparing a site or office for a deployment, it may be necessary to add supporting documentation to the DU record.  For example, this could include health and safety certificates or induction documentation.  In addition, all Survey responses are also stored as PDFs that can be downloaded and shared with colleagues that don't have access to ManagementStudio.  These documents are stored in the Attachments tab.

For further information about working with the Attachments tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000108628

History

All activities made against a DU record within ManagementStudio are recorded in the History tab. This enables project administrators to review changes and data-mine for specific events or activities during certain time frames.

For further information about working with the History tab, please refer to:

https://support.managementstudio.com/a/solutions/articles/14000108629

Further Support

If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.