Top Banner
UGA Identity Management and SSN Removal Update Presented for ITMF February 3, 2011 Office of the CIO EITS The University of Georgia
13

Office of the CIO EITS The University of Georgia.

Jan 03, 2016

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Office of the CIO EITS The University of Georgia.

UGA Identity Management and SSN Removal Update

Presented for ITMFFebruary 3, 2011

Office of the CIOEITSThe University of Georgia

Page 2: Office of the CIO EITS The University of Georgia.

2

EMT Initiative Approval

Phase 1: Identity Repository and Infrastructure Unique Identifier (UGAID) Translation Tools

Phase 2 EMT Priorities: SSN Removal/Mitigation in Distributed

Systems—estimated Dec 2011 SSN Removal/Mitigation in CORE/Enterprise

and Mainframe Systems—estimated Dec 2012

12 Total Slides

Page 3: Office of the CIO EITS The University of Georgia.

12 Total Slides 3

Planned Parallel Path Approach

FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN JUL DEC JAN JUL DEC JAN JUL DEC JAN

2009

7/31/09(Estimated)

IdM Infrastructure and Process IdM Infrastructure and Process

SSN Replacement (timeline to be determined by scope)

SSN Replacement (timeline to be determined by scope)

SSN PHASE I

SSN Replacement Analysis & Planning

SSN Replacement Analysis & Planning

Single, consolidated view

of ALL Identities

Ongoing SSN Replacement Efforts Ongoing SSN Replacement Efforts

Current Efforts

IMS to DB2/SSN Removal (convert IMS database to DB2 and remove SSN from core administrative systems)

IMS to DB2/SSN Removal (convert IMS database to DB2 and remove SSN from core administrative systems)IMS/SSN

SSN PHASE II

SSN Replaced in Initial Systems

Initial systems for SSN Replacement

chosen

Discovery Complete

Implementation End

7/31/09(Estimated)

6/30/10(Estimated)

12/31/09 12/31/12

2010 2011 2012

SSN Replacement (timeline to be determined by scope)

SSN Replacement (timeline to be determined by scope)

SSN Replaced in Remaining

Systems

2013

12/31/11(Estimated)

DOAS Contract Negotiations DOAS Contract Negotiations

Page 4: Office of the CIO EITS The University of Georgia.

Reported SSN Removal

Original Total 12.6 M Removed 5.5 M

0

1,000,000

2,000,000

3,000,000

4,000,000

5,000,000

6,000,000

7,000,000

8,000,000

9,000,000

10,000,000

11,000,000

12,000,000

Jul-0

5

Oct-0

5

Dec-0

5

Feb-

06

Apr-0

6

Jun-

06

Aug-0

6

Oct-0

6

Dec-0

6

Feb-

07

May

-07

Jul-0

7

Sep-

07

Nov-0

7

Jan-

08

Mar

-08

May

-08

Jul-0

8

Sep-

08

Nov-0

80

1,000,000

2,000,000

3,000,000

4,000,000

5,000,000

6,000,000

7,000,000

8,000,000

Actuals

Goal

SSN

Record

s

12 Total Slides 4

Page 5: Office of the CIO EITS The University of Georgia.

12 Total Slides 5

Noted Accomplishments

Unit SSNs Removed

Unit SSNs Remove

d

Parking Services 1,896,980 Student Affairs  35,000

Libraries 1,169,771 BigCard 35,000

EITS         1,034,315 Printing 10,000

UGA Card Services  1,000,040 Food Services 7,200

Arts & Sciences 266,999 Golf Course 3,000

Admissions 220,000 Political Science  1,500

Graduate School 73,000 Admin Services  1,100

School of Law  48,887 Regents Center 400

Page 6: Office of the CIO EITS The University of Georgia.

12 Total Slides 6

Major Challenges

1. DOAS Procurement Delays -- IMS/DB2 Conversion RFP

2. Complexity of CORE/Distributed Processes and Systems

3. Distributed Units Require Intensive EITS Assistance

4. Data Discrepancies5. Resources/Priority Conflicts

If identified challenges are not addressed, original timelines are likely to change

Page 7: Office of the CIO EITS The University of Georgia.

7

Complexity and Lack of Integration of CORE Administrative Systems

Student System Diagram

12 Total Slides

Page 8: Office of the CIO EITS The University of Georgia.

12 Total Slides 8

Challenges with SSN Removal from the CORE/Enterprise and Mainframe

Lengthy DOAS procurement process

Complexity 3+ million lines of code 14,000 programs 5381 tables and views 348 major databases

Existing/potential institutional priorities requiring IDM resources e.g., ADDM projects, SACS, next generation

administrative systems, new email system

Page 9: Office of the CIO EITS The University of Georgia.

12 Total Slides 9

Challenges with SSN Removal for Distributed Systems

Lack of resources in distributed units

Interdependent on CORE systems

EITS resources are needed for all projects

Data Discrepancies between Student, HR and BigCard Systems

UGAID Assignment for Professional Schools not available at application

Some unit technical staff unwilling to move forward or causing delays because of disagreement with technical aspects of the approach

Page 10: Office of the CIO EITS The University of Georgia.

12 Total Slides 10

Remaining SSNs in Distributed Systems

In Process 225,955 Ready to

Execute 774,520

Potential Barriers 2,587,941

Known Barriers 1,759,060

Required to Keep 1,802,772

Secure in “Fort Knox”

Page 11: Office of the CIO EITS The University of Georgia.

11

Data Discrepancies: Existed before IDM Tools

Types of data discrepancies Historical New

▪ Some business/system processes continue to propagate discrepancies

IDM has identified discrepancies/duplicates Initial number ~100,000

▪ Both historical and active ▪ Identified by IDM

Reduced to 21,382▪ Estimated 1,000 – 2,000 discrepancies in active

records12 Total Slides

Page 12: Office of the CIO EITS The University of Georgia.

12 Total Slides 12

Suggested Next Steps

Academic and Administrative unit heads confirm targets Confirm or re-specify the dates their units have

previously set for the elimination of SSNs in their units

Accountability for progress Require progress reports from unit heads on quarterly

basis

Complete process mapping and data error identification

Continued…

Page 13: Office of the CIO EITS The University of Georgia.

12 Total Slides 13

Suggested Next Steps

Move forward without waiting for “perfection”

▪ Units should move forward without 100% discrepancies resolved

▪ Implement data discrepancy controls▪ Units that are reliant on SSNs from Core Systems

should assess using IDM tools prior to the IMS/DB2 conversion

Resources/Priorities If additional resources are not available, then

support is needed for changes in priorities due to resource reallocations required for IDM priorities