CRM Person Contact Data Synchronization Phase 1


CRM Person Sync.png
Quick View
Summary: 

Person contact information in CRM does not match HRSA (source system). Discrepancies in person name, email, phone number, and address result in degraded service function of the CRM system. For example, auto email notifications to CRM customers are lost and some ERMS cases get associated with general customer name vs actual customer due to missing email addresses. Additionally, application support efforts to address reported discrepancies continue to increase while user confidence decreases due to data issues.

Addressing the problem will result in increased confidence in the system due to higher levels of data integrity, which will result in fewer cases related to manually changing person data.

Start Date: 
May 6, 2009
Go Live: 
October 20, 2009
End Date: 
October 30, 2009
Current Milestone: 
10/20/2009 - Initial clean-up complete
Stage: 
Critical
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Katherine Ranes
Contact for more information: 
Katherine.Ranes@asu.edu
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Katherine Ranes
More Info
Source: 
Internal
Priority: 
Medium
Scope: 

Implement an SQR solution to scan person records and identify person name, email, phone number, and email discrepancies. Correct data is moved to a temporary record from HRSA (source system) and inserted into the CRM record.

Initial clean-up will be a manually controlled and coordinated effort (batch process).

Discrepancies will continue to occur, therefore, a batch process will need reoccur and scheduled on a recurring basis.

This solution will not address and remove the duplicate person records in CRM.

This solution will not address messaging errors between HRSA and CRM.

The solution will address the errors related to person name, email, phone number, and address caused by the broken messaging process.

The solution is an incremental step to decrease recurrent cases and customer requests to fix contact information. The solution will restore user confidence in the system.

Note: The Solution is partially developed.

Required resources: PM/Lead Business Analyst, CRM developer

All Milestones and Schedule: 

Determine scope of cross-reference anomalies and establish baseline data - 06/10/09
Confirm scope of data to be corrected - 06/10/09
Develop, test, and migrate to prod person email sync SQR - 08/08/2009

Develop, test, and migrate to prod person phone number sync SQR - 08/08/2009 - complete
Develop, test, and migrate to prod person address sync SQR - 08/08/2009 - complete
Manually process SQRs for intial data sync - 08/10/2009 - 09/15/2009 - Delayed - Target 11/20/2009
Schedule SQR processing via batch - Delayed - 11/30/2009

Deliverables: 

SQR processes to sychnronize CRM person contact information (person name, email, phone number, address) with HRSA person record (source system).

Initial clean up of person records using developed SQR processes.

A scheduled batch process to run SQRs on a recurring basis.

Risk & Threats: 

Constraints

  • Availability of testing environments
  • Scheduling of HRSA update/fix cycle
  • Quality of user cross-reference table
  • Availability of batch processing windows near start of semester
Syndicate content