Session 15

Data Strategy Overview
Keith Wilson
1

Data Strategy Purpose
The Right Data to the Right People at the Right Time.
11 12 1 10 2 9 3 8 4 7 6 5

 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
2

Data Strategy Summary
Vision
Gather Business Objectives

Target State and Strategy
Strategic Focus Target State

Roadmap

Implementation Plan

Data Strategy

As-Is

Data Quality Discussions Data Strategy Team Findings And Input

Current State

 Gather Desired Outcomes and Current State  Create the Target Vision for Enterprise Data Usage  Facilitate Paradigm Shift from Current to Target State
3

Data Strategy Desired Outcomes
The Data Strategy defines FSA’s enterprise data vision for how it will combine tools, techniques and processes to handle its enterprise needs.
 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
4

Data Strategy Initiatives
 Data Framework
    As-Is and Target State Data Flows Data Quality Mad Dog and Quality Assurance Strategy XML ISIR XML Registry and Repository

Right Data

 XML Framework

 Common Identification
    Standard Student Identification Method Routing ID Single Sign-up Single Sign-on

Right People

 Trading Partner Enrollment and Access

 Technical Strategies
 FSA Gateway

Right Time
11 12 1 10 2 9 3 8 4 7 6 5

5

Data Quality Methodology
Improving Data Quality results in better information enabling better decisions.
 Data Quality “Mad Dog”
highlights the high priority data quality issues facing FSA data owners and users.

 Data Quality Assurance Strategy
plan for the continual improvement of FSA data quality and the maintenance and refinement of data across the enterprise.

 Key Concepts
 Fewer data stores = less redundancy  Standardized Definitions and Terminology via XML Framework
6

XML Framework
FSA will use XML, via a single set of enterprise and community standards, to simplify and streamline data exchange across postsecondary education.
Benefits  Data Exchange Standard – Standardize FSA’s data exchange using XML as the data exchange technology standard.  Consistent Accurate Data – The framework will define data standards, as XML Core Components, for data exchange to achieve consistent and accurate data.  Data Cleanup and Maintenance – Enable data cleanup and maintenance activities.  Standard Data Tools and Processes – Establish standard data tools and processes, to support consistently performed data/XML modeling.  System Flexibility – Provide system flexibility to simplify future interface changes and support new application and data exchange requirements, through XML-based data modeling.
7

Standard Student Identification Method (SSIM)
The Standard Student Identification Method 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.
Key Identification Problems in the Current Environment
 Unique customer records can be inappropriately merged creating privacy concerns.  A customer’s records cannot be linked appropriately preventing FSA from viewing data about a customer across all phases of the lifecycle. Three-Pronged SSIM Solution: Each part 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.
FSA Application Level For flow of student records through the lifecycle from one FSA system to another PIN
SSIM Matching Algorithm Logic
Alias Table Valid Fi eld Edits

CPS
SSIM Matching Algorithm Logic
Alias Table Valid Fi eld Edits

COD
SSIM Matching Algorithm Logic
A lias Table Valid Field Edits

CSB
SSIM Matching Algorithm Logic
Alias Table Valid Field Edits

NSLDS
SSIM Matching Algorithm Logic
Alias Table Valid Fi eld Edits

• • •

Primary Identifier Verification with the Matching Algorithm Additional SSA Verification: Consistent Correction Processing and Error Notification

SSIM Data Changes and Corrections for Students

FSA Centralized Routing (EAI) For changes and corrections to student SSIM data that must be communicated across the enterprise SSIM Centralized Routing (EAI) Correction Processing and Error Notification

Files containing SSIM change records and error notifications Student files progressing through FSA lifecycle

8

Single Sign-Up / Sign-On
RID Enrollment Management Access Management Participation and Delivery
RID Provisioning and relationship establishment

RID Management
Generate RID Add/Maintain Roles

Attribute Management
Add/Maintain Attributes
Identity Manage information, Identifiers credentials, access rules

Relationship Management
Assign Relationships Maintain Relationships

Trading Partner entity and relationship information for Access Management Attribute and relationship management

Audit

Reporting

Oversight

Communicate RID Data
Reporting

9

Technical Strategies: FSA Gateway  Enable trading partners to discover FSA
capabilities by consolidating information and providing uniform access  Provide right-time access to FSA data and business functions  Leverage standard data formats in data exchange  Use common data definitions for data exchange and validation  Integrate with existing FSA capabilities and other initiatives  Incorporate with Trading Partner Management and security efforts to enable uniform communication between FSA and trading partners 10

Data Strategy Key Findings To Date
The Data Strategy teams have confirmed several key findings.
  Data should be organized by business process, not by system. “As-Is” Data Flow Discussions have facilitated a broader understanding of End-to-End Business Processes across all FSA program areas. Verified that using a Matching Algorithm with SSN, First Name, Last Name, and DOB is the most flexible and tolerant way to identify customers. Need to develop an single Enterprise solution for all Trading Partner Identification and Access. Providing data access to business experts is the key component of improving the enterprises’ ability to make informed business decisions.
11

More Detailed Information
For More Information Regarding the Standard Student Identification Method
Please attend the SSIM Breakout Session
FSA Application Level For flow of student records through the lifecycle from one FSA system to another PIN
SSIM Matching Algorithm Logic
Alias Table Valid Field Edits

CPS
SSIM Matching Algorithm Logic
Alias Table Valid Fie ld Edits

COD
SSIM Matching Algorithm Logic
Alias Table Valid Field Edits

CSB
SSIM Matching Algorithm Logic
Alias Table Valid Field Edits

NSLDS
SSIM Matching Algorithm Logic
Alias Table Valid Field Edits

November 4 November 5

1:30 – 2:45 10:45 – 12:00

SSIM Data Changes and Corrections for Students

FSA Centralized Routing (EAI) For changes and corrections to student SSIM data that must be communicated across the enterprise SSIM Centralized Routing (EAI) Correction Processing and Error Notification

Files containing SSIM change records and error notifications Student files progressing through FSA lifecycle

For More Information Regarding Single Sign-Up / Single Sign On
Please attend “A Session with a Twist: Whatever Happened to Single Sign-on” November 4 November 5 1:30 – 2:45 1:30 – 2:45

12

Technical Assistance
I appreciate your feedback and comments. I can be reached at:
Email: Keith.Wilson@ed.gov

13