Master Data Management

1. What is master data management (MDM) in AG5?

In AG5 you can centrally create, edit, and delete your organizational master data. Additionally, you can control the quality of your master data with an approval process. This approval process allows you to collaborate and centrally maintain the master data while controlling the quality of your master data.

Master data such as:

• Skills (Also known as qualifications)

• Skill requirements

• Organization items such as Department & Job Roles

With the master data approvals feature activated for your organization, any change in the master data will go through the approval process. For any change first, a so-called ‘Change request’ will be created. Only after approving the change request, the data will become visible and active in the system.

2. What is the purpose of master data management?

The purpose is to ensure a higher quality of your organizational master data within your skills management across your whole organization.

For example, large organizations experience consistency problems within their skills master data. And inconsistencies can lead to differences within the skills management across an organization.

3. Managing master data

Who can change master data?

The master data can be changed by users who already have the right to these changes. The only difference is that with this feature activated the master data changes need to be approved.

Users with the following rights are able to change master data:

• Admin users

• Superuser edit rights

• Skill edit rights

• Grouping edit rights

When a change is made the user will see a message that the change needs approval.

As long as the Change request is waiting for approval, it will be listed in the specific ‘change requests list’. Below you can see an example list. The purpose of this list is to see and understand the open changes to avoid duplicated change requests.

In this list, you can not approve the change requests, for that you have to go to the control center (see below).

Who can approve change requests?

Approvals can be done by the admin or by the manager of the user who changed the master data. Additional policy settings can be added to allow admin users to make changes to the master data without an approval process.

4. How to manage the master data?

As an admin, you can configure AG5 to the needs of the organization (the first setup). When any of the master data is changed in a later change then this needs to be approved by the admin or manager before it is visible and active.

There are 3 types of changes:

• Newly created item (e.g. a skill)

• Edited existing item

• Deleted item

How to approve master data?

When master data is changed, this change will first be listed in the ‘Change requests’ with the status ‘waiting for approval’. After it is approved, it will become active and visible within the system.

Below you can see in the control centre that there are change requests waiting for approval.

Below you can see the approval list and when selecting a change request you can see the details of the requested change. Approve or reject the changes, and click 'save' to confirm your choices.