Master Data Management Data Evaluation

Once we have received Data Extracts, the next step in the Master Data Management Discovery process is to document the files.  The documentation includes the total number of records as well as the number of records that contain each data element that can potentially be used for our Master Data Management match.  We also look to see if each record has a unique ID so that we can properly keep track of the records for importing and matching purposes in the Master Data Management application. 

In addition to examining the quantity of the data, we also take a look at the quality of the data that is to be integrated as part of the Master Data Management system.  For example, we look to see if there is data in an Address field, such as the continuation of the Company Name, that does not belong in an Address field.  It is very common for representatives to put data in a field that does not belong.  Sometimes this happens because the database does not have an appropriate field for the specific data element being entered or the appropriate field in the database cannot handle enough characters.  Other times this happens because the rep is working quickly “in the heat of battle” and mistakenly types the information in the wrong field.

Once we have documented and evaluated the data, we can begin to determine some of the items needed for the Master Data Management match.  Note, we do not interfere with any operational systems and we only make adjustments in the Master Data Management system for matching and linking purposes within the MDM system.  Some of the items to consider are:

1. Data Transformation – What pre-thought out processes within the Master Data Management application should be used to change the data for matching purposes?

2. Data Pre-processing – Do we need to develop any custom processes to change or derive data for matching purposes?

3. Knockout Data – Do we need to remove any data for matching purposes?

4. Hierarchy Data – Does the client’s data contain any information that indicates that records are part of the same corporate hierarchy or in any way related to each other?

5. Third-Party Data – Does the client have any third-party data that indicates that records are part of the same corporate hierarchy?

6. Match Data Elements – What data elements should be imported and used in the match?

7. Hierarchy Levels – What are the elements of each level of the corporate hierarchy match?