# Presentation: 663874

## <date/time>

## Session 44

***CommonLine and the Common Record***

## The Common Record

**Concept of consistent data packet layout across programs (Pell, DL, FFEL, Campus-based).**
**Concept of consistent data packet layout across major stakeholders (FSA, CommonLine, Meteor).**

- Session 44

## The Common Record

***The Common Record***

**Core Components Dictionary – PESC**
**Schemas**
**Common Record **
**Common Record – COD**
**Common Record – FFEL and Alt**
**Common Record – ISIR**

- Session 44

## 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**

- Session 44

## The Common Record

**Document Structure allows you to send data for:**
**Multiple Schools**
**Multiple Years**
**Multiple Awards**
**In ****ONE**** Transmission!**

- Session 44

## The Common Record – Schema Structure 

- Session 44

## XML:  The Technology Solution

- 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**

- Session 44

## XML:  The Technology Solution	

- XML is the **standard language** of e-business and the internet
- XML lets the industry **describe virtually any type of data** and deliver it across a network
**XML **would allow for** easy inclusion** of other student financial resource data (FFEL, ISIR, State Grant, etc.)

- Session 44

## XML:  The Technology Solution

***XML Bridges the Technology Gap***

**Legacy Systems**

**XML**

- Transport Mechanism

- Standards

- Common Elements

- Session 44

## CommonLine Strategy

- CommonLine Converging with the Common Record
- Convergence – taking the best of all programs and creating a new standard, not adoption of one over another

- Session 44

## Collaboration

- CommonLine was the foundation of the Common Record
- Department of Education ESC Participation
- PESC XML Forum

- Session 44

## 	To design a single standard XML-based Common Record to support all financial aid programs, including FFEL and Direct Lending, eliminate multiple flat files, and provide a simplified process for the submission of financial aid data by schools and their SIS partner. The initial effort will focus on incorporating FFELP business flows into the Common Record, merge like terms and processes between the various programs and capitalize on the efficiencies of the XML technology. The resulting system standards will still allow each program to maintain features within the Common Record that are unique to their program and business processes. In addition, this effort will develop/produce specifications and proposed standards which take into account existing FFEL industry standards and the need to support translations between specifications as well as an anticipated phased adoption and implementation of the new specifications by SIS vendors and the FFEL community.  Future convergence activities will look to further streamline the process within Common Record.

***ESC XML Mission***

- Session 44

## ESC XML Mission

**To design a single standard XML-based Common Record**
**to support all financial aid programs, **
**eliminate multiple flat files**
**provide a simplified process for the submission of financial aid data by schools and their SIS partner**

- Session 44

## ESC XML Mission

**Initial effort will focus on incorporating FFELP business flows into the Common Record, **
**merge like terms and processes between the various programs **
**capitalize on the efficiencies of the XML technology **

- Session 44

## ESC XML Mission

**The resulting system standards will still allow each program to maintain features within the Common Record that are unique to their program and business processes**
**Develop specifications and proposed standards which take into account existing FFEL industry standards and the need to support translations between specifications as well as an anticipated phased adoption and implementation of the new specifications by SIS vendors and the FFEL community.  **

- Session 44

## 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**

- Session 44

## 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**

- Session 44

## Reengineering Proposal

**Example – pre-disbursement cancellation :**
**In the reengineered process:**
**LoanAmount****	****	****(new value)**
**DisbursementNumber****	****(old value)**
**DisbursementAmount****	****(zero)**
**CancellationDate****	****	****(new value)**

- Session 44

## Proposed Implementation Schedule

**12/15/2002  – ****	****Close all open issues**
**4/1/2003 ****	****– ****	****First draft of documentation**
**6/1/2003 ****	****– ****	****Final documentation ****	****	****	****completed**
**12/1/2003 ****	****– ****	****Testing begins**
**4/1/2004 ****	****– ****	****Implementation begins**

- Session 44

## Next Steps for FFELP

**November 11, 2002 – Presentation to schools and SIS vendors**
**Received a *****GREEN***** light from vendors**
**Received a *****GREEN***** light from schools**
**Received a *****GREEN***** light from service providers**

- Session 44

## Next Steps for FFELP

**Final comments on the proposal were due to the ESC by 11/22/2002**
**ESC will review all comments and offer resolution to the school and vendor community via a series of conference calls the week of 12/09/2002**

- Session 44

## Next Steps for FFELP

- Final review and approval of proposal
- Finalize schema development
- Training, education and outreach!

- Session 44

## Next Steps for FSA

**Simplify business process and technology for Schools**
**Map data to business processes**
**Utilize open technology supporting future**
** ****	****enhancements**

***Next Steps for FSA***

- Session 44

## Comments, Questions, Feedback, and Contact Information

- <footer>

***Comments, Questions, Feedback, and Contact Information***

**Paul Hill**
**Phone:  (202) 377-4323**
**Email:  Paul.Hill.JR@ED.GOV**
**Tim Cameron**
**	****Phone:  (202) 822-2106**
**	****Email:  tcameron@nchelp.org**