Data Standardization/Harmonization

This page serves as a centralized location to monitor and ensure data consistency across all applications in the SMDS ecosystem. Data harmonization ensures that all systems are aligned in terms of data format, structure, values, and business logic. This helps in reducing discrepancies and ensures smooth operations across the platforms.

Discrepancies & Issues

There are 26k customer records that are unable to flow to downstream systems due to various geo exceptions and failures in the DMDM process

Geo Exception Report

Issues	Current Geo Exception count	Status
Region mismatch between SMDS GEO and CMD	6646	In progress
City mismatch between SMDS and DMDM	3031	Completed
Postal code mismatch	16260	In progress
Geo Exception Failure due to city static mapping	1150	In progress
The postal code flag is mandatory in CMD, but the postal code is missing. Data correction is required in CMD.	25000	In progress

Turning off postal code

Turning off postal code validation in the MDMD process to avoid geo exception failures. Currently, an additional validation check is being performed, which causes geo exception failures when the postal code is not in sync between SMDS, CMD, and DMDM

Sanity check is performed in lower env and all looks fine, waiting for go ahead from the DMDM consuming application to proceed further

@morten

City Static Mapping between CMD and DMDM

There is an existing mapping between CMD and DMDM for the city, which is causing a city mismatch. This mapping needs to be removed after a thorough review to ensure there is no impact on downstream systems.

Mismatch between CMD and SMDS GEO

Customer Data Nexus - Power BI

Here is current snapshot and there are 151K city are having mismatch between CMD and SMDS GEO

Plan: