The Project allows you to track the following information for your transformation project:
Name: A friendly name for the project that is unique in your organization. The name must begin with a letter or number. It can contain only letters, numbers, and the following special characters: space, hyphen, underscore, apostrophe, percent, ampersand, comma, and period.
Organization: The name of the parent organization for the project.
Description: (Optional) A brief description of the project.
Start Date: The date that the transformation of workloads is planned to begin.
End Date: The date that the transformation of all workloads must be completed successfully.
Mode: Specify a mode for the project. You can switch between the modes if needed.
Planning: Planning Mode allows the widest variety of supported transformation methods and planning options.
Use Planning Mode to plan transformations that you execute manually or using third-party migration tools. You can also configure individual workloads for automation.
Automated: Automated Mode allows you to plan and execute workload migrations in your PlateSpin Migration Factory environment. It provides additional settings that apply only to migration with PlateSpin Migrate servers, while limiting some options to those supported by automation. See Section 1.3, PlateSpin Migration Factory Environment.
Use Automated Mode to plan transformations that you execute using automated or semi-automated options in a PlateSpin Migration Factory environment. You can also configure individual workloads for manual or third-party migration.
NOTE:Planning Mode is automatically selected for any workload that has a transformation method that is not supported for automated migration such as Decommission and Virtual File Move.
Custom Field Names: Additional information types that you want to track for a project. You can define 1 to 7 custom fields. Each custom field is independent, and can be used for any purpose. Uses might include a new attribute, a logical tag, a priority system, contact information, and so on.
For example, if you want to identify the workload with its day-to-day IT administrator, you might define the Custom 1 field name to be Contact for the project. Values might be the contact person’s name, user name, or email address, as appropriate for your project. You specify a workload’s value for the Contact field in the Workload dialog.
Associations: Associations define the relationship between a variety of components and the project. You can also perform the same tasks on each tab that you can on their primary tab, with the exception of the Workloads tab. For workloads, you can view information about the original and proposed workloads associated with the project.
Planning
Waves (Create, Edit, View, Delete) - See Managing Waves.
Batches (Create, Edit, View, Move, Delete) - See Managing Batches.
Applications (Create, Edit, View, Delete) - See Managing Applications.
Workloads (Original, Proposed) - See Configuring Workload Transformations.
Resources
Credentials (Create, Edit, View, Delete) - See Managing Credentials Resources.
Hosts - See Managing Host Resources.
Source (View)
Target (Create, Edit, View, Delete)
Migration Servers (Create, Edit, View, Delete) - See Managing Migration Server Resources.
Networks - See Managing Network Resources.
Source (View)
Target (Create, Edit, View, Delete)
Datastores - See Managing Datastore Resources.
Source (View)
Target (Create, Edit, View, Delete)
Resource Pools (Create, Edit, View, Delete) - See Managing Resource Pool Resources.
Environments (Create, Edit, View, Delete) - See Managing Environment Resources.
Users
Project role assignments at the project level are automatically inherited by their child components.
Dashboard Viewer (View, Add, Remove) - See Dashboard Viewer Role.
Migration Specialist (View, Add, Remove) - See Migration Specialist Role.
Project Architect (View, Add, Remove) - See Project Architect Role.
Project Manager (View, Add, Remove) - See Project Manager Role.