Hi @aish_TF ,

 

If your Ataccama MDM instance is running and you need to implement standardization changes to phone numbers, it will likely affect matching for any new records that are ingested into MDM and could potentially create new master IDs, since simply changing the standardization rules won't automatically update existing records.

Here's how this change impacts Ataccama MDM specifically:

Impact on Matching:

• Matching Rules: Ataccama MDM uses flexible matching rules defined in the "Match" processor. Depending on the algorithms like "Exact Match," "Fuzzy Match," or "Regular Expression" used in these match rules for the phone number field, the standardization changes will affect how these algorithms evaluate similarity.
• Weights and Thresholds: Each matching rule has a weight, and Ataccama calculates a composite weight to determine matches. Changing the phone number format can alter these weights and potentially push records below the matching threshold.
• Survivorship Rules: Ataccama uses survivorship rules (selection rules in merge step) to determine which value to retain for the golden record. If the phone number format changes, the survivorship rules may need adjustments to ensure the standardized value is selected.

Scenarios where new Master IDs are created:

• Unmatched Records: If the standardized phone number doesn't match any existing records according to your rules, Ataccama might create a new master ID for it.
• Changes in Clusters: Even if records still match after standardization, the change might affect how records are clustered. This could lead to records being split into different clusters or merged into new ones, potentially resulting in new master IDs.
  
  To ensure your Ataccama MDM system accurately reflects the phone number standardization changes, you should initiate a rematch/reprocess operation (https://docs.ataccama.com/mdm/latest/configuration/batch-interface.html#reprocess-operation) for the affected entity. This is crucial because simply changing the standardization rules won't automatically update existing records. 
  Things to consider before initiating rematch/preocess:
• Master ID Changes: Be prepared for potential changes to Master IDs. As matching and clustering may shift due to the standardization, some records might be assigned new Master IDs.
• Impact Assessment: Before initiating the operation, analyze the potential impact on downstream systems and processes that rely on Master IDs.
• Performance: Rematching and reprocessing can be resource-intensive. Plan the operation during off-peak hours to minimize performance impact on other MDM tasks.
  
  Cheers!
  Vysakh Indrasenan

Hi @ivysakh 

I did check and made sure of the above factors. In my scenario, standardization did not impact contact master creation, there does seem to be new master ids present.

Thank you