Modernize On-Premises Objects > Managing modernization projects > Summary of modernization projects
  

Summary of modernization projects

After you modernize MDM Hub objects, you can view a consolidated summary of modernization progress for your modernization projects. The summary aggregates key metrics and details by object type so that you can track your modernization progress from the MDM Hub to MDM SaaS.
You can create up to five summaries. A summary can include both active and archived projects, but not deleted projects. You can view summaries, but you can't export or download them. If you delete a project that a summary includes, you can't regenerate the summary.

Creating a summary of modernization projects

You can create up to five summaries of modernization projects. To create more summaries, delete some of your summaries.
    1On the Modernization page, click Create Summary.
    2In the Create Summary dialog box, enter a unique summary name.
    3Select the projects to include in the summary.
    Note:
    You can select up to 5 projects to include in the summary.
    4Click Create.
    The Modernization Summary page appears.

Modernization summary

Use the Modernization Summary page to track your modernization progress across projects. You can use the modernization metrics and modernization details to see which objects are in progress, yet to start, or failed.

Modernization metrics

The modernization metrics show the count of MDM Hub objects in the selected projects and their modernization status.
The following table describes each metric:
Metric
Description
Total Objects
Total number of MDM Hub objects in the selected projects.
Note:
If a summary includes more than one project, the summary counts each MDM Hub object once in the overall total, even if the object appears in more than one project.
Successfully Modernized
Number of MDM Hub objects that are modernized.
In Progress
Number of MDM Hub objects that are currently undergoing modernization.
Yet to Start
Number of MDM Hub objects that aren't modernized yet.
Skipped
Number of MDM Hub objects that are skipped because they already exist in MDM SaaS.
Failed
Number of MDM Hub objects that failed to modernize.
Overall Progress
Percentage of successfully modernized MDM Hub objects out of the total objects in the selected projects.
Note:
The overall progress includes skipped MDM Hub objects. If all the MDM Hub objects in a project already exist in MDM SaaS, the progress of the project shows 0%.

Modernization details

The modernization details display the mapping between each MDM Hub object and its corresponding MDM SaaS object, along with the modernization status. You can view the modernization details to track the modernization status of each object and identify the objects that aren't modernized.
When you select an object type, you can view its modernization metrics, including the total number of objects and how many are successfully modernized, in progress, yet to start, or failed.
You can view the modernization details for one object type at a time. Select an object type, such as lookup table or user, to view its mapping details. You can filter the modernization details by status. For example, you can filter a lookup table by status to view only the objects that failed to modernize.

Lookup Table

The following table describes the mapping details that you can view for a lookup table:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Lookup Table
Lookup table retrieved from the MDM Hub configuration.
Reference 360 Code List
Reference 360 code list that the MDM Hub lookup table is mapped to.
Mapping Type
Type of mapping applied.
The mapping type can have one of the following values:
  • - One-to-One (Name Unchanged). An MDM Hub object is mapped to a code list.
  • - Many-to-One. Multiple MDM Hub objects are mapped to a single code list.
  • - Create as New. An MDM Hub object is created as a code list in MDM SaaS.
  • - Yet to Map. The MDM Hub object isn't mapped to any code list.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Base Object

The following table describes the mapping details that you can view for a base object:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Base Object
Base object that stores master data in the MDM Hub.
MDM SaaS Business Entity
Corresponding business entity in MDM SaaS.
Mapping Type
Type of mapping applied.
The mapping type can have one of the following values:
  • - One-to-One (Renamed). An MDM Hub object is mapped to a target business entity and renamed in MDM SaaS.
  • - One-to-One (Name Unchanged). An MDM Hub object is mapped to a predefined MDM SaaS business entity.
  • - Many-to-One. Multiple MDM Hub objects are mapped to a single MDM SaaS business entity
  • - Yet to Map. The MDM Hub object isn't mapped to any MDM SaaS business entity.
  • - Unmapped. The MDM Hub object isn't transformed and appears as is.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Business Entity

The following table describes the mapping details that you can view for a business entity:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Business Entity
Business entity that defines the data model in the MDM Hub.
MDM SaaS Business Entity
Corresponding business entity in MDM SaaS.
Mapping Type
Type of mapping applied.
The mapping type can have one of the following values:
  • - One-to-One (Renamed). An MDM Hub object is mapped to a target business entity and renamed in MDM SaaS.
  • - One-to-One (Name Unchanged). An MDM Hub object is mapped to a predefined MDM SaaS business entity.
  • - Many-to-One. Multiple MDM Hub objects are mapped to a single MDM SaaS business entity.
  • - Yet to Map. The MDM Hub object isn't mapped to any MDM SaaS business entity.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Match Rule Set

The following table describes the mapping details that you can view for a match rule set:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Business Entity
Business entity that the match rule set is configured for in the MDM Hub.
MDM SaaS Match Model
Corresponding match model in MDM SaaS.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Source System

The following table describes the mapping details that you can view for a source system:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Business Entity
Name of the source system in the MDM Hub.
MDM SaaS Business Entity
Corresponding business entity in MDM SaaS.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Hierarchy Relationship

The following table describes the mapping details that you can view for a hierarchy relationship:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Hierarchy Relationship
Hierarchy relationship between records in the MDM Hub.
MDM SaaS Hierarchy Relationship
Corresponding hierarchy relationship in MDM SaaS.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Network Relationship

The following table describes the mapping details that you can view for a network relationship:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub Network Relationship
Non-hierarchical relationship between records in the MDM Hub.
MDM SaaS Non-Hierarchical Relationship Graph
Corresponding non-hierarchical relationship graph in MDM SaaS.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

User Role

The following table describes the mapping details that you can view for a user role:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub User Role
User role defined in the MDM Hub.
MDM SaaS User Role
Corresponding user role in MDM SaaS.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

User

The following table describes the mapping details that you can view for a user:
Mapping Details
Description
Project Name
Name of the project.
MDM Hub User
User defined in the MDM Hub.
MDM SaaS User
Corresponding user in MDM SaaS.
Status
Modernization status of the object.
The status can have one of the following values:
  • - Yet to Start. The object isn't modernized yet.
  • - In Progress. The object is currently undergoing modernization.
  • - Migrated. The object is successfully modernized.
  • - Failed. The object failed to modernize.
  • - Skipped. The object was excluded from modernization.

Regenerating summaries

As you continue to modernize on-premises objects, the metrics and statuses in an existing summary might become outdated. Regenerate a summary to update it with the latest modernization progress for the selected projects. Regenerating updates the existing summary instead of creating a new one.
You can regenerate a summary only after the modernization process compiles the summary data.
    1On the Modernization page, click Generated Summaries.
    2Select the summary you want to regenerate.
    3On the Modernization Summary page, click Regenerate.
    The summary is regenerated.
    Note:
    If you delete a project that a summary includes, you can't regenerate the summary.

Deleting summaries

You can create up to five summaries. If you've reached the limit, delete a summary before creating another.
    1On the Modernization page, click Generated Summaries.
    2Select the summary you want to delete, and click Delete.
    A confirmation dialog box appears.
    3Click OK.
    The summary is deleted.