Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Purpose

To keep the business rules of Matching and Merging of CRM client profiles and Applications (service deliveries) as consistent as possible across all HSI lines of businesses

Definitions

TermDefinition
MatchCRM Identifies and Flag that two objects are potential duplicates/match
MergeTo merge multiple Profiles into one; can be done auto or manual; when merging, a master record must be identified, and business rules to select values must be identified
AttachTo associate different CRM objects with one another, e.g. attaching an application to a profile, or an interaction to an application (service delivery); can be done auto or manual
Manual-A CRM user completes this task
Auto-CRM completes this task without user intervention
ProfileCRM Object - Client Profile created
ApplicationCRM Object - Service Delivery created

Business Scenarios

Scenario Fields - exact match except First NameInterchangeable?
CurrentLegacy IDFirst Name (fuzzy?)Last Name DOBPostal CodeEmailPhone Number Mobile NumberOther Phone
Matched Profiles for Manual Merging
xxx




Fair Pass Applications (Current) to Client Profiles: SAMS ClientSAMS MIDxxx




Fair Pass Applications (Current) to Client Profiles: TCS ClientCSIS Household IDxxx














Future - Additional 








Matched Profiles for Auto-Merging - Option 1n/a - duplicatesxxxx



Matched Profiles for Auto-Merging - Option 2n/a - duplicatesxxx

x
Matched Profiles for Auto-Merging - Option 3n/a - duplicatesxxx
x


FP Application (Expansion) to Client Profiles: ALL - Option 1n/a - non-OW/TCSxxxx



FP Application (Expansion) to Client Profiles: ALL - Option 2n/a - non-OW/TCSxxx

x
Welcome Policy Applications to Client Profiles - Option 1n/a - newxxxx



Welcome Policy Applications to Client Profiles - Option 2n/a - newxxx

x
Welcome Policy Applications to Client Profiles - Option 3CLASS Household PINxxx




CRM Scenarios

Scenario Fields: x = Exact Matches unless identified as Fuzzy Interchangeable?

Legacy IDFirst Name
Last Name DOBPostal CodeEmailPhone Number Mobile NumberOther Phone
Criteria A - CRM Matches but Does Not Merge/Attach; Manual Merge/Attach by User
A.1 SAMS MID







A.2CSIS Household ID







A.3YARDI Applicant (P-Code) ID







A.4CLASS Household PIN







A.5n/axxx




Criteria B - CRM Match and Auto-Merge/Attach; No User Intervention required
B.1SAMS MIDFuzzyxx




B.2CSIS Household IDFuzzyxx




B.3YARDI Applicant (P-Code) IDFuzzyxx




B.4CLASS Household PINFuzzyxx




B.5n/aFuzzyxxx



B.6n/aFuzzyxx
x


B.7n/aFuzzyxx

x
  • No labels