Scribd
Upload
2K views

Module 1 Answer PDF

This document summarizes data received from Sprocket Central Pty Ltd, noting data quality issues encountered like inconsistent customer IDs between tables and missing or inconsistent values. It outlines the methods used to mitigate issues, like only using customer records that exist across all tables and standardizing address values. Recommendations are made to enforce input restrictions and data type constraints. The client is asked to validate the data statistics and cleaning assumptions. Further engagement with a data subject matter expert is proposed before continuing model analysis.

Uploaded by

Yeji
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2K views

Module 1 Answer PDF

This document summarizes data received from Sprocket Central Pty Ltd, noting data quality issues encountered like inconsistent customer IDs between tables and missing or inconsistent values. It outlines the methods used to mitigate issues, like only using customer records that exist across all tables and standardizing address values. Recommendations are made to enforce input restrictions and data type constraints. The client is asked to validate the data statistics and cleaning assumptions. Further engagement with a data subject matter expert is proposed before continuing model analysis.

Uploaded by

Yeji
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Note: The data and information in this document is reflective of a hypothetical situation and client.

This document is to be used for KPMG Virtual Internship purposes only.

Dear [Client point-of-contact],

Thank you for providing us with the three datasets from Sprocket Central Pty Ltd. The below table
highlights the summary statistics from the three datasets received. Please let us know if the figures are
not aligned with your understanding.

Table name No. of records Distinct Customer IDs Date Data Received
Customer -insert value- -insert value- -insert value-
Demographic
Customer Address -insert value- -insert value- -insert value-
Transaction Data -insert value- -insert value- -insert value-
Notable data quality issues that were encountered and the methods used to mitigate the identified data
inconsistencies are as follows. Furthermore, recommendations have been provided to avoid the re-
occurrence of data quality issues and improve the accuracy of the underlying data used to drive business
decisions.
● Additional customer_ids in the ‘Transactions table’ and ‘Customer Address table’
but not in ‘Customer Master (Customer Demographic)’

Mitigation: Please ensure that all tables are from the same period. Only customers in the Customer Master
list will be used as a training set for our model. 

This indicates that the data received may not be in sync with each other which may skew the
analysis results if there are missing data records. Please refer to excel file ‘data_outliers.xlsx’ for
the list of outliers between tables. 


● Various columns, such as the brand of a purchase, or job title, have empty values in
certain records

Mitigation: If only a small number of rows are empty, filter out the record entirely from the training set for
prediction. Else, if it is a core field, impute based on distribution in the training dataset. 

For key datasets, such as transactions, less than 1% of transactions (totalling less than 0.1% of
revenue) have missing fields. These records have been removed from the training dataset.

● Inconsistent values for the same attribute 



(e.g. Victoria being represented as “V”, “Vic” and “Victoria”)

Mitigation: Use regular expression to replaced extended values into abbreviations to ensure consistency
across addresses.

Recommendation: Enforce a drop-down list for the user entering the data rather than a free text field.

In order to construct meaningful variables for the model, the data has been cleaned to avoid
multiple representations of the same value. Additionally, gender records where ‘U’ have been
replaced based on the distribution from the training dataset.

● Inconsistent data type for the sameattribute



(e.g. numeric values for some fields and strings for others)

Mitigation: Convert selected records in characters to numeric. Remove non-numeric characters from string. 

Recommendation: Ensure that fact tables in the given database have constraints on data types.

Having different data types for a given field make it difficult to interpret results at the later stage.
Therefore, appropriate data transformations are made to ensure consistent data types for a given
field.
Moving forward, the team will continue with the data cleaning, standardisation and transformation process
for the purpose of model analysis. Questions will be raised along the way and assumptions documented.
After we have completed this, it would be great to spend some time with your data SME to ensure that all
assumptions are aligned with Sprocket Central’s understanding.

Kind regards,
[Junior Consultant Name]

You might also like