1

ERA Data Integrity

2

Overview Desired Business Outcomes

Data Integrity Problems

Recommended Solutions

Single Point of Ownership

Concerns

Schedule

3

Desired Business Outcomes One Profile, and Only One Profile An Unambiguous Relationship

Between Commons and IMPAC II profiles Grantee ownership of data

Structures and User Interfaces That Work Demographic data Addresses Degrees

Data That Can Be Relied On

4

Problems

Duplicate and incorrect data Business rules that allow creation of duplicate

data Lack of a unique identifier for a person Lack of adequate controls

Person collapses Name typeovers

Bridges and data loads Confusion

Profiles and roles Change PI, Edit PI

Address, Degrees, Employment Possible Software Errors

5

Solutions QRC Data Cleanup

Orphan Record Cleanup

Sunset the Forward Bridge of People Data

Redesign Persons Module

6

Person Module Redesign Single Point of Ownership

IMPAC II

Validated Profiles

IMPAC II Users

Validated Profiles

OER Data Quality

New Profile Registration

Profile Updates

Profile Updates

IC Central User

7

Single Point of Ownership

Concerns Do we cut off update access to all

profiles? Can’t slow down grant award Can’t slow down application receipt

process Consultants, fed staff SREA users

Need for Careful Analysis

8

Person Module Redesign Single Point of Ownership

Changes arising from QRC business rule analysis

Change screens to clear up user confusion and meet business area needs

Changes to address and degree structure

Changes to role/profile structures and interface

Unified approach to people between Commons and IMPAC II

9

Schedule

2/02Jan 28, 2002 Nov 1, 2002

3/02 4/02 5/02 6/02 7/02 8/02 9/02 10/02

Sunset Forward Bridgeof People Data

Lock on ValidatedProfiles

Single Point of OwnershipImplementation

Persons Module Redesign

10

Implementation Concerns Schedule and Resources

Staffing Validating Profiles

Updating Profiles

Schedule of QRC Tasks 1 and 3

Decisions on Policy

Timing of Enterprise-wide Redesign