ERA Data Integrity 1 Overview n Desired Business

ERA Data Integrity 1

Overview n Desired Business Outcomes n Data Integrity Problems n Recommended Solutions n Single Point of Ownership n Concerns n Schedule 2

Desired Business Outcomes n n One Profile, and Only One Profile An Unambiguous Relationship n n n Structures and User Interfaces That Work n n Between Commons and IMPAC II profiles Grantee ownership of data Demographic data Addresses Degrees Data That Can Be Relied On 3

Problems n n Duplicate and incorrect data Business rules that allow creation of duplicate data Lack of a unique identifier for a person Lack of adequate controls n n Bridges and data loads Confusion n n Person collapses Name typeovers Profiles and roles Change PI, Edit PI Address, Degrees, Employment Possible Software Errors 4

Solutions n QRC Data Cleanup n Orphan Record Cleanup n Sunset the Forward Bridge of People Data n Redesign Persons Module 5

Person Module Redesign n Single Point of Ownership 6

Single Point of Ownership n Concerns n n n 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 7

Person Module Redesign n Single Point of Ownership n Changes arising from QRC business rule analysis n Change screens to clear up user confusion and meet business area needs n Changes to address and degree structure n Changes to role/profile structures and interface n Unified approach to people between Commons and IMPAC II 8

Schedule 9

Implementation Concerns n Schedule and Resources n Staffing n Validating Profiles n Updating Profiles n Schedule of QRC Tasks 1 and 3 n Decisions on Policy n Timing of Enterprise-wide Redesign 10