Common Record Common Line How Implementing Common Record

Common. Record: Common. Line How Implementing Common. Record: Common. Line Can Benefit You Presented by [Enter your information here] Session 44

Session Overview l Common Record Background Information l What is XML? l Developing the CR: C Standard l Benefits of Common Record: Common. Line l Implementation and Next Steps 2

The Common Record Background Information l Consistent data packet layout l Across programs (Pell, DL, FFEL, Campus-based, loan counseling, transcripts, etc. ) l Major stakeholders (FSA, Common. Line, Meteor, AACRAO, MYF). 3

Importance of Standards l Standards facilitate efficiency l Standards make training and cross-training easier l Reduce change for the sake of change 4

Common Record Philosophy l l l Design a single standard Common Record Support all financial aid programs Eliminate multiple flat files Provide a simplified process for the submission of financial aid data Maintenance and enhancements managed by the Postsecondary Electronic Standards Council (PESC) 5

Common Record and XML: The Technology Solution l l Standard language of e-business and the internet. Lets the industry describe virtually any type of data. Allows easy inclusion of other student financial resource data in a single file (FFEL, ISIR, State Grant, etc. ) Standardized validation of data order and content. 6

The Common Record Terminology l Core Components Dictionary: l l Standard structure Naming conventions Change control oversight Schema: Defines structure and content for XML Documents 7

The Common Record Terminology l Common Record: l l l Common Origination and Disbursement COD (Direct Lending) Common. Line (FFEL and Alternative Loans) Transcripts (XML Transcript) XML ISIR (future release) Loan Counseling (in development) 8

Flat File Structure l Example @HPS 199900278502262309592004 COMMON A 004 TTG Univer @1 ATEST JOHN 603213435100 W. 14 TH ST NEW YORK @1 ATEST FRANK 603214234200 W. 14 TH ST NEW YORK @1 ATEST GARY 603549786300 W. 14 TH ST NEW YORK @1 ATEST HARRY 603363677400 W. 14 TH ST NEW YORK @1 ATEST JON 603497832500 W. 14 TH ST NEW YORK @1 ATEST ROB 603563409600 W. 14 TH ST NEW YORK @T 00000600000020040226230959 A 004 TTG UNIVERSITY 0033 9

XML File Example <Student> <Index> <SSN>313895522</SSN> <Birth. Date>1982 -02 -02</Birth. Date> <Last. Name>Price</Last. Name> </Index> <Person. Identifiers> <Drivers. License. State>NC</Drivers. License. State> <Drivers. License. Number>NC 394427</Drivers. License. Number> </Drivers. License> </Person. Identifiers> </Student> 10

Common Record Structure 11

What’s In It for Me? Session 44

Benefits of Implementing Common Record: Common. Line l Eliminate need for double data entry l Flexible Disbursement Processing l More than 4 disbursements l Separate disbursement dates for subsidized and unsubsidized loans l Ability to indicate disbursement amounts l Ability to override disbursement date profiles 13

Benefits of Implementing Common Record: Common. Line l Supports school-assigned student IDs l l l Addresses privacy concerns Allows use among all data partners Promotes real-time processing 14

Benefits of Implementing Common Record: Common. Line l Move from transaction-based to end-result changes l l l Eliminates need to determine transaction type (@1 -09, etc. ) Eliminates sending multiple transactions to achieve desired result Only changed fields will be sent to your service provider 15

Benefits of Implementing Common Record: Common. Line l Human-Readable l l l Loan Status Information l l Tags surround data <Last. Name>Smith</Last. Name> Plain English values vs. Codes Not limited to loan phase code Future software upgrades will be easier to manage 16

Implementation l l NCHELP Electronic Standards Committee has published the CR: C implementation guide. PESC has approved the CR: C schema. Most lenders, guarantors, and servicers are in various stages of implementation and are forecasting production ready between Spring ‘ 05 to Spring ’ 06. e-Library > Electronic Standards Documentation and Tools > Common Record - Common. Line Documentation 17

Some Considerations for Schools l l Prioritize CR: C benefits for your office. Use priorities to evaluate implementation options. Communicate priorities to your software providers and service providers. Involvement in NCHELP Electronic Standards Committee l School Advisory Group l Origination Standards Advisory Team 18

Information Sources l l NCHELP - The CR: C Implementation Guide is available in the e-Library at www. nchelp. org IFAP – COD news, technical documentation, updates are available at www. ifap. ed. gov PESC – XML Technical Specifications, Data Dictionaries, Schemas, assistance and approvals are available at www. pesc. org XML Registry and Repository – Current schema and dictionary are available at www. fsaxmlregistry. ed. gov 19

Contact Information l [Enter your information here] l Mark Putman Information Technology & Industry Standards Officer NCHELP mputman@nchelp. org 913 -724 -6655 20

Questions ? ? ? 21