# Presentation: 326679

## Standard Student Identification Method

- Jeanne Saunders

***Session 16***

## Agenda

- Opening Remarks/Introduction
- Overview of Data Strategy
- Standard Student Identification Method (SSIM) Update
- Next Steps

## Data Strategy Purpose

***The Right Data to the Right People at the Right Time.***

- Consolidation of Data into Shared Source
- Focus on Data Quality

- Standard Student Identification Method
- Trading Partner Management
- Routing ID
- Access Management

- Integrated Student View
- Integrated School View
- Foundation for more Timely and Efficient Processing

## Data Strategy Initiatives

_**Data Framework**_
- As-Is and Target State Data Flows
- Data Quality Mad Dog and Quality Assurance Strategy
_**XML Framework**_
- XML ISIR
- XML Registry and Repository
_**Common Identification**_
- Standard Student Identification Method
- Routing ID
_**Trading Partner Enrollment and Access**_
- Single Sign-up
- Single Sign-on
_**Technical Strategies**_
- FSA Gateway

*Right Data*

*Right People*

*Right Time*

## Data Strategy Desired Outcomes

_**Cross-Program Integration**_
- _Business objective_ gathering sessions comprised of _cross-channel business owners _and the establishment of _Standard Identifiers for Students and Schools_
_**Improved Data Quality**_
- Through the execution of a _Data Quality Mad Dog_ and the creation of a _Quality Assurance and Implementation Plan_
_**Improved Organization and Distribution of Data**_
- Creation of an _XML Framework_ and _Internal_ and _External Data Exchange Strategy_
- Establish a _**Data Storage Strategy**_
- Data Warehouse and Data Mart Strategy
- Plan for organizing data to answer broader, deeper business questions

*The Data Strategy defines FSA’s enterprise data vision and strategy for how it will combine tools, techniques and processes to handle its enterprise data needs.*

## Standard Student Identification Method (SSIM) Overview

- What is SSIM?
- SSIM seeks to establish a simple framework by which FSA and Delivery Partners can consistently identify students/borrowers across all phases of the Student Aid Lifecycle
- What will SSIM do?
- Consistently and systematically link customer records across the FSA enterprise
- Support changes and updates to key customer attributes (i.e., updates to SSN, First Name, DOB, Last Name)
- Ensure student privacy protection; minimize unauthorized/unauthenticated access to student data
- System identification requirements should not prevent valid customers from receiving aid or progressing through the repayment phase (i.e., deferments, rehabilitations, consolidations)

## Standard Student Identification Method (SSIM)

- Why is SSIM needed?
- Unique customer records can be inappropriately merged created privacy concerns
- A customer’s records cannot be linked appropriately preventing FSA from viewing data about a customer across all phases of the lifecycle
- What causes these Problems?
- All FSA systems may not be using the same additional identifying data.  Most systems employ different rules for determining uniqueness or identities for inbound or outbound interfaces
- Some FSA systems complete an SSN verification with SSA before data is processed; others do not perform the SSA match when new information is received
- Changes or corrections to identifying fields (i.e., SSN) are not consistently supported or propagated throughout the FSA enterprise

## SSIM Solution Summary

- Three-Pronged Recommended Solution
- Primary Identifier Verification with the Matching Algorithm
- Additional SSA Verification
- Consistent Error Handling and Change Processing
- This solution leverages effective, proven identifier solutions already being used in some parts of the FSA lifecycle.  Roll-out of these tools and processes consistently shall tighten controls and improve data integrity/consistency.

## SSIM Implementation Recommendation

- 	The recommended SSIM implementation option consists of two stages following a pilot that will allow early realization of the SSIM benefits, but also maintain alignment with the FSA Data Strategy overall vision
- SSIM Pilot
- SSIM logic will be implemented in CPS for renewal FAFSAs only (planned for ’04 – ’05)
- Stage One - Implement the algorithm at the system level and use centralized routing (Enterprise Application Integration -- EAI) for error handling and change processing
- Individual application's implementation of the matching algorithm option for processing input files from one system to another
- Error handling and correction processing would be implemented through centralized routing (EAI) to allow communication/propagation to systems as determined
- Implementation would begin with the next requirements cycle (’05 – ’06) with CPS, NSLDS, and COD as _*potential*_ candidates
- Stage Two – The team will create a picture and high level plan on how to include SSIM in the overall Data Strategy end state vision
- The team will assess how SSIM will fit into the overall Data Strategy vision

## SSIM Implementation Recommendation – Stage 1

**** Because of current CSB and PIN efforts, these systems are not targeted for Stage One implementation***

## SSIM Matching Algorithm

- What is the Matching Algorithm
- Requires a combination of data fields common to all systems
- Social Security Number is primary identifier, but it will be verified through enterprise-wide business rules and tolerances with additional data fields:
- First Name, Date of Birth, Last Name
- Why a Matching Algorithm
- Consistently identify customers throughout internal (FSA) data exchange and external data exchange
- Use of this algorithm is a proven practice within FSA internal and external data exchange
- Requires only data currently existing in FSA systems
- Provides flexibility in allowing a phased implementation

## SSIM Matching Algorithm

- 	The matching algorithm will be a series of 4 comparisons of identifying data.  Any one successful comparison constitutes a successful match.

## Error Handling Highlights

- Centralized routing (EAI) will be used to send error notifications to FSA systems based on business rules.  Usually errors will be sent from the receiving system to the sending system.

## Error Handling Highlights

- Error Handling
- Sending and receiving systems will work in combination to resolve the error
- Sending systems will be *primarily* responsible for resolving SSIM errors
- Error notifications should only be sent to the sending system
- In Stage 1 there is no need for a centralized error handling team
- Resources should be dedicated at the system level to resolve errors

## Change Processing Highlights

- Centralized routing (EAI) will be used to propagate Change/Correction Processing to multiple FSA systems simultaneously based on business rules.

## Change Processing Highlights

- Change Processing
- All validated SSN, Name, and DOB changes should be sent to all systems forwards and backwards in the lifecycle
- Centralized router will help determine appropriate recipients of change
- All open status records should be updated
- Systems will need to determine how to handle closed, archived, and record not found updates

## SSIM Next Steps

- Begin SSIM Pilot on Renewal FAFSAs in CPS
- Select Stage 1 Participants and Begin Requirements Gathering for the 2005-2006 Software Release
- Continue to align SSIM with the Data Strategy End State Vision (Stage 2)

## Technical Assistance

- We appreciate your feedback and comments.  We can be reached at:
- Phone:  Jeanne Saunders
- Email:    jeanne.saunders@ed.gov