1. Common Record Paving the Way for Electronic Standards in Higher Education Common Record – COD Common Record – CommonLine Common Record – ISIR Collaboration GO Convergence

2. Why did FSA Adopt XML?  XML is technology-neutral allowing trading partners to use different technologies in their own applications  XML allows schools to use one Common Record between disparate databases or different systems  XML allows users to share information seamlessly  XML is future-oriented XML: The Technology Solution

3. XML Bridges the Technology Gap Legacy Systems XML

4. Common Record Expansion  ORIGINAL VISION: Use XML Technology to create financial aid data packet standards. Financial Aid Office ISIR FFEL PELL DL

5. Common Record Expansion  REVISED VISION: Use XML Technology to create higher education or cross-industry data packet standards. Educational Institution AdmissionsRegistrarsFinancial Aid

6. Educational Institution AddressLine AddressCity AdmissionsRegistrarsFinancial Aid AddressLine AddressCity AddressLine AddressCity AddressLine AddressCity Common Record Expansion

7. Common Record Expansion Convergence of Standards XML Forum Core Components XML Forum Core Components Financial Aid Core Components Financial Aid Core Components Admissions/ Registrar Core Components Admissions/ Registrar Core Components ASC X12 EDI ASC X12 EDI Common Line Common Line Meteor Common Record Common Record ebXML

8. Common Record Expansion Core Components Data Dictionary Core Components Data Dictionary Sector Library Sector Library Sector Library Sector Library Sector Library Sector Library Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema Application Schema

9. The Common Record  Core Components Dictionary – PESC  Schemas Common Record Common Record – COD Common Record – CommonLine Common Record – ISIR

10. The Common Record  Format is student-centric, showing data for multiple financial aid programs in one student complex element  The entire common record or only those portions of the common record which changed can be transmitted  XML allows the Common Record to be easily changed (extensible)  Format is human-readable, facilitating problem solving

11. The Common Record uDocument Structure allows you to send data for:  Multiple Schools  Multiple Years  Multiple Awards In ONE Transmission! ’02’03’04

12. The Common Record Schema Structure

13. New Common Record XML Schema  Common Record and Schema revised based on work with PESC to meet EBXML standards  Abbreviations eliminated from all tag names  Some tag names changed all together  Full Participants are required to use the new schema for all 03-04 awards  Full Participants may either continue to use the old schema for 02-03 awards or may switch and use the new schema for both 02-03 and 03-04 awards

14. Using XML and Developing Standards will: Simplify business process and technology for Schools Map data to business processes Utilize open technology supporting future enhancements ISIR Institutional Student Information Record COD Common Origination And Disbursement NSLDS National Student Loan Data System Award Year 2004-05 Schedule and Phase-in process for the Lending Community and Schools to be determined Award Year 2002-03 50 Schools Award Year 2003-04 1,000 or more *FFEL Expansion Implementation 2004-2005 Award Year 2004-05 All Schools Phase-in process for schools to be determined * Effort led by FFELP Next Steps for FSA

15. Data Strategy Framework The Framework will help FSA define its standards and approach for: Access Methods Data Standards Data Quality Data Architecture Data Ownership

16. Overview - XML Framework Objective: The FSA XML Framework will outline FSA ’ s target state and implementation strategy for using XML across the enterprise. The XML Framework will provide standards, processes, and a toolset for implementing XML.

17.  Define FSA’s XML Strategic Assessment and Enterprise Vision.  Analyze current XML environment at FSA – strategy, standards, and technology.  Based on industry proven practices for guidance.  Provide standards and guidelines for consistent XML schema development.  Define the governance process for XML standards. Vision/Where are we going?

18.  Develop a Core Component Library.  Implement a Registry and Repository for storing and accessing XML documents.  Identify implementations that may leverage XML.  Architect an enterprise Data Quality Approach (using Core Components). Vision/Where are we going?

19. The Common Record: CommonLine  CommonLine Converging and Aligning with the Common Record -COD standards with the flexibility of FFELP -Supports all functionality available in CommonLine Release 5

20. The Common Record: CommonLine  Designed to meet the needs of -Schools -SIS Vendors

21. The Common Record: CommonLine Progress Report  November 11, 2002 -Detailed presentation of proposal to schools, SIS vendors and service providers

22. The Common Record: CommonLine Progress Report  Collaboration continues to move us forward! -Schools, The College Board, Datatel, SCT Corp., PeopleSoft, and Sigma Systems have all indicated their support of the ESC proposal

23. The Common Record: CommonLine Progress Report  Documentation development has begun! -ESC review of draft documentation - April 2003 -First draft for public review - May 2003 -Final documentation due - July 2003

24. Reengineering Proposal  Streamlining the Application and Disbursement Processes All records sent in a single file Pre- and Post-guaranty changes can now be sent together Routing is at the record level

25. Reengineering Proposal  Streamlining the Application and Disbursement Processes Moving from Transaction Based to End Result Based Changes Support of Real Time Functionality in an XML Based Record

26. Reengineering Proposal  Example -- pre-disbursement cancellation: -In the CLR5 process: Change Type Code Loan Type Code Disbursement Identification Number Disbursement Date Cancellation Date Cancellation Amount Revised Disbursement Amount

27. Reengineering Proposal  Example--pre-disbursement cancellation: -In the reengineered process: LoanAmount(new value) DisbursementNumber(old value) DisbursementAmount(zero) CancellationDate(new value)

28. Proposed Implementation Schedule  5/1/2003 - First draft of documentation  7/1/2003 - Final documentation completed  12/1/2003 - Testing begins  4/1/2004- Implementation begins

29. Next Steps for FFELP  Finalize schema development  Finalize documentation development  Training, education and outreach!

30. Additional Information and Contact Information Electronic Standards Committee Page www.nchelp.org Candy Pfeiffer Chair, ESC 608.246.1631 cpfeiffer@glhec.org School Portal/ IFAP www.sfa4schools.ed.gov Paul Hill, Jr. Schools Channel 202.377.4323 paul.hill.jr@ed.gov

31. Comments, Questions, and Feedback

32. Thank You!!! Paving the Way for Electronic Standards in Higher Education Common Record – COD Common Record – CommonLine Common Record – ISIR Collaboration GO Convergence