meteor and financial aid delivery - immagic.com · the meteor project financial aid services • in...
TRANSCRIPT
Meteor and Financial Aid Delivery
Justin Tiltoninstructional media + magic, inc.
As presented atHEWI/AACRAO 2001 Student Aid Modernization Conference
September 26, 2001Arlington, Virginia
Th
e M
eteo
r P
roje
ctOverview
• Status report on the OSFA and some of the key initiatives that will impact the future of Financial Aid
• Emerging technologies: portals, uPortal, channels – and how this relates to Meteor
• The Meteor Project: description, status, and delivery timeline
Th
e M
eteo
r P
roje
ctFinancial aid services
• In the past, regulations drove practices and limited services
• Now, information technology drives practices and has the potential to increase service
________________
Using information technology, the U.S. Department of Education is improving its services, setting higher expectations
Th
e M
eteo
r P
roje
ctSome key initiatives
• Department of Education OSFA• Web enabled applications• Common Origination and Disbursements
• Student loan industry• ELM Resources• The Meteor Project
• College and university collaboratives• JA-SIG (Java in Administration Special Interest Group)
• Internet 2 and Shibboleth• MIT’s Open Knowledge Initiative
• Florida State University, University of Hawaii• “30 minute application to funds”
Th
e M
eteo
r P
roje
ctSFA Web-enabled applications
• FAFSA on the web
• Schools portalrelease 2.0 with single sign-on
• Financial partners portals – FY 2002
• Student on-line access todirect loan servicing
• API to SFA systems
Th
e M
eteo
r P
roje
ctWeb ApplicationFAFSA on the Web - 2001
Th
e M
eteo
r P
roje
ctFAFSA On The Web
FAFSA e-Filers
0.0
0.5
1.0
1.5
2.0
2.5
3.0
3.5
4.0
4.5
97-98 98-99 99-00 00-01
Mill
ions
of
studen
ts
Th
e M
eteo
r P
roje
ctSchools Portal Prototype
Th
e M
eteo
r P
roje
ctFederal Experience
• Customers using electronic services are more satisfied than those that don’t.
• Agencies that measure customer satisfaction
• Have better customer satisfaction that the federal government as a whole
• In general, are improving customer satisfaction
Th
e M
eteo
r P
roje
ctExpect...
• SFA Common Origination and Disbursements
• 2002-2003 Batch Processing Pilot
• 2004-2005 Schools required to communicate with COD using XML
• 2003-2004 Schools have the option to send real time messaging
As reported by Kay Jacks at the 2001 NASFAA Annual Conference
• Electronic Signatures
• Limited use of SFA PIN
• Replaced by Internet 2/SAML December 2002 (no official commitment)
As mentioned by Steve Hawald at the 2001 Summer JASIG Conference
Th
e M
eteo
r P
roje
ctExpect that...
• Alternative loans will be the largest source of financial aid by 2005
Estimated from a forthcoming report by the Advisory Committee on Student Financial Assistance
• The focal point of financial aid information and transactions will be the college or university
• “Web services” will be the basis for new information technology infrastructure
• New college and university administrative systems will be based on Web services; component architecture will become available 2003, and widely implemented between 2004 and 2005
Th
e M
eteo
r P
roje
ctImpact on colleges and universities
Changes:
• From Batch to Real-time Transactions,
• From Proprietary File Transfers to Internet XML Messaging Standards
• From SFA-defined to Industry Standard Message Content
• An integrated Student Experience
• Use of SFA-provided Java (J2EE)shared-components
Th
e M
eteo
r P
roje
ctNCHELP-sponsored “convergence”
• Business messages
OSFA Common Record, IFX Forum, CommonLine, PESC, industry XML
• Data transport
OSFA, CommonLine, PESC, industry SOAP and ebXML
• Authentication (in progress)
OSFA Internet 2/Shibboleth, JA-SIG, industry SAML, SOAP_DSIG
• Directory Services (soon)
• OSFA, Meteor, industry UDDI
Delete this slide
Th
e M
eteo
r P
roje
ctThe Meteor Project
• An initiative of the student loan industry
• Collaborative effort of 37 guaranty agencies, lenders, secondary markets, and servicers
• On-line, real-time information services
• Separate channels for students and financial aid professionals
• Aligned with industry, SFA standards
______________________
“Building the IT infrastructure for the next decade”
Th
e M
eteo
r P
roje
ctA Glimpse: Florida State University
In “30 minutes” on-line:
• Apply for admission and be accepted
• Apply for financial aid, including the FAFSA, receive an award, issue credits and initiate funds transfer
• Apply for housing and receive a housing assignment
• Enroll in classes
__________________
FSU reports general agreement with OSFA for their designRichard Tombaugh Aug 2001
Th
e M
eteo
r P
roje
ctStudents expectations shaped by...
• Their experience applyingfor federal financial aid
• Their use of financial services portals
• Their use of the Internet
• Their life in a “real-time, information rich” environment
Th
e M
eteo
r P
roje
ctStudents now expect...
• Customer service 24 hours a day, 7 days a week
• Complete information froma single source
• Delivery by Web, e-mail, telephone, facsimile, and wireless devices
• response time of 15 seconds for telephone, 10 seconds for Web, and 2 hours for e-mail and facsimile
• access to a complete customer history
Th
e M
eteo
r P
roje
ctCollege students choose a Web site...
Ranked by importance
• College or university’s portalif adequate
• Suggestions of other students
• Print advertisements
• Web search
Th
e M
eteo
r P
roje
ctIs technology important?
• Technology choices determine the quality of electronic services offered to Web-savvy prospective students, current students, alumni, faculty, staff and the public.
• Technology choices will determine with whom you do e-business and how it is done.
Th
e M
eteo
r P
roje
ctSFA technology choices
• XML - B2B Standard
• Business Messages
• XML Schema (data validation)
• Java - Transportable Programs
• Shared Java Components
• Web Implementations – FAFSA
• UML - Unified Modeling Language
Th
e M
eteo
r P
roje
cteBusiness Web services architecture
• XML “tagged” data contenteXtensible Markup Language
• SOAP data transportSimple Object Access Protocol
• XSL transformations for presentationeXtensible stylesheet language
• XML Digital Signature
for Server Authentication
• UDDI/WSDL directory servicesUniversal Description, Discovery, and Integration,and Web Services Description Language
Th
e M
eteo
r P
roje
ctTechnology standards
M - from Meteor installationO - optional
Industry
OSFA
Met
eor
JA-S
IGuPo
rtal
IBM
Web
Ser
vice
s
Mic
roso
ft.N
et
Sun O
ne
Java Programming Language
XML Markup Language
SOAP Data Transport M
UDDI Directory M
WSDL Service Description M
Th
e M
eteo
r P
roje
ctAnnounced support of Web services
• Feb 2000 OSFA U.S. DOE
• Sep 2000 NCHELP CommonLine ESC
• Oct 2000 NCHELP’s Meteor Project
• Dec 2000 IBM Corporation
• Feb 2001 Sun Microsystems
• Mar 2001 Microsoft CorporationDelete this slide
Portals, uPortal (JA-SIG), and Channels
Th
e M
eteo
r P
roje
ctPortal defined
• generally synonymous with a gateway, for a World Wide Web site that is or proposes to be a major starting site for users when they get connected to the Web
www.whatis.com, May 19, 2001
• “A portal’s main reason for existence is to integrate disparate systems and data into a unified, centrally accessible interface.”
Jim Paroza, “Enterprise value of portals is clear,”eWeek, Sep 13, 2002
Th
e M
eteo
r P
roje
ctYahoo, the portal “standard”
Delete this slide
Th
e M
eteo
r P
roje
ctMyYahoo, a personal portal
Delete this slide
Th
e M
eteo
r P
roje
ct
Administrative
Instruction
Library
Research
The Academic Web World
Th
e M
eteo
r P
roje
ctWhy a campus portal?
• Improves productivity and satisfaction
• Integrates divergent systems
• Creates a set of templates and standards for developing and delivering Web materials
• Becomes a platform to quickly and efficiently introduce new technologies (channels)
Th
e M
eteo
r P
roje
ctWhy are portals important?
• Helps knowledge workers to be more productive
• Preferred by users
• Market share
• Brand identity
• A viable architecture for information services
• Time to market
• Improved services
• Lower costs
Delete this slide
Th
e M
eteo
r P
roje
ctFeatures of uPortal
• Framework for presenting aggregated content (channels)
• Personalization
• Role-based access control
• Single signon to multiple systems
Th
e M
eteo
r P
roje
ctA student’s view of the Web
Th
e M
eteo
r P
roje
ctA student’s view of the Web
Delete this slide
Th
e M
eteo
r P
roje
ctA Customized Portal
Delete this slide
Th
e M
eteo
r P
roje
ctuPortal for the Pilot Implementation
• Open Source Software
• Features used by Meteor
• Readily available
Th
e M
eteo
r P
roje
ctJA-SIG
• Java in Administration Special interest Group
• A development collaborative and a clearinghouse for JAVA based software developed specifically by and for colleges and universities.
• Current focus: uPortal – an full feature enterprise web application portalDelete this slide
Th
e M
eteo
r P
roje
ctuPortal Interfaces
• Authentication
• Proving your identity
• Authorization
• Deciding what you can access
• User preferences
• Profiles, structure, themes, skins
• Channel information
• Availability and configuration
Th
e M
eteo
r P
roje
ct
XML
Stylesheet
XHTML: Web Browser
WML: Cell Phone
HTML: PDA
XSLTProcessor
Content Transformation
Th
e M
eteo
r P
roje
ctTab / Column Layout
Delete this slide
Th
e M
eteo
r P
roje
ctTree / Column Layout
Delete this slide
Th
e M
eteo
r P
roje
ctTheme: uosm
Delete this slide
Th
e M
eteo
r P
roje
ctTheme: java
Delete this slide
Th
e M
eteo
r P
roje
ctTheme: imm
Delete this slide
Th
e M
eteo
r P
roje
ctTheme: matrix
Th
e M
eteo
r P
roje
ctMultiple Target Devices
Th
e M
eteo
r P
roje
ctWhat is a Channel?
• Displays content
• XML feeds (events, news items, etc.)
• Legacy systems (registration, library)
• Interactive applications
• Meteor
• Bookmarks
• Email, chat, threaded discussions
Th
e M
eteo
r P
roje
ctXML “feed” Channel
Delete this slide
Where does The Meteor Project fit into all of this?
Th
e M
eteo
r P
roje
ctRelationship of Meteor and JA-SIG
JA-SIG
uPortal
Meteor Channel
The Meteor Project
Th
e M
eteo
r P
roje
ctThe Meteor Project
Meteor is the software and service to obtain a student’s own financial aid information from a number of different sources.
• The software can be installed on any Website--a school, lender, guaranty agency, secondary market, servicer, or collection agency.
• The software is Open Source--a “gift” from the Meteor sponsors to the financial aid community.
Th
e M
eteo
r P
roje
ctData from multiple sources, locations
The Pilot Implementation
Th
e M
eteo
r P
roje
ctReference implementation
The reference implementation includes:
• Authentication of the user
• A list of loans
• Details on any specific loan
• Error, warning, and information messages for the user
Th
e M
eteo
r P
roje
ctMeteor authentication
Th
e M
eteo
r P
roje
ctMeteor list of loans
Th
e M
eteo
r P
roje
ctSample Meteor loan detail
Th
e M
eteo
r P
roje
ctUser message, no Meteor service
Th
e M
eteo
r P
roje
ctUser message, please call
How does Meteor work?
Th
e M
eteo
r P
roje
ctMeteor in a nutshell…
Lender
XML
Value Entered
Value Entered
DETAIL
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
Value Entered
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
UDDI
Th
e M
eteo
r P
roje
ctThe first step…
The student chooses a portal to their Financial Aid information
Th
e M
eteo
r P
roje
ctNext, a secure connection
Please Log In
Log-in
SUBMIT CANCEL
$X,XXX.XX
$X,XXX.XX
Welcome to
oursitecom
Th
e M
eteo
r P
roje
ctRequests sent...
XML
<LoanHistoryRq><CustPermId>448377707</CustPermId><DateOfBirth>1980-09-03</DateOfBirth>
</LoanHistoryRq>
Guaranty Agencies
NSC
SFA
Th
e M
eteo
r P
roje
ctResponses returned
XML
SFA
GA
NSC
<LoanInformation><LenderIdType>OPEID</LenderIdType><LenderId>809063</LenderId><LenderName>Bank of Oklahoma</LenderName><SchoolIdType>OPEID</SchoolIdType><SchoolId>003152</SchoolId><SchoolBranch>00</SchoolBranch><SchoolName>University of Central Oklahoma</SchoolName><InformationSourceIdType>OPEID</InformationSourceIdType><InformationSourceId>809063</InformationSourceId><InformationSourceName>Bank of Oklahoma</InformationSourceName><InformationSourceDate>2000-11-12</InformationSourceDate></LoanInformation>
XML
XML
Th
e M
eteo
r P
roje
ctAggregated data in portal
Value Entered
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
Th
e M
eteo
r P
roje
ctStudent wants details
Value Entered
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
Th
e M
eteo
r P
roje
ct
Value Entered
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
Request for detail sent to Lender
Lender
XML
Th
e M
eteo
r P
roje
ctDetail screen displayed
Lender
XML
Value Entered
Value Entered
DETAIL
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
Value Entered
$X,XXX.XX
$X,XXX.XX
$XXX.XX
$X,XXX.XX
$XXX.XX
$XXX.XX
$XX,XXX.XX
Th
e M
eteo
r P
roje
ctDiagram of Meteor Concept
Web ServicesHTML
MeteorXML
StudentStudent Access ProviderAccess Provider Data Provider Data Provider
Th
e M
eteo
r P
roje
ctAs implemented ...
Web ServicesSecure HTML
MeteorSecure XML
StandardBrowser
StandardBrowser uPortaluPortal
MeteorSOAP
MeteorSOAP
MeteorSOAP
MeteorSOAP
DatabaseDatabase
Th
e M
eteo
r P
roje
ctThe development configuration
uPortalStandardBrowser
StandardBrowser uPortaluPortal
Meteor SOAPJAVA ComponentsMeteor SOAPJAVA Components
Meteor SOAPJAVA ComponentsMeteor SOAPJAVA Components
DatabaseJDBC ConnectionDatabase
JDBC Connection
LinuxApacheTomcat
LinuxApacheTomcat
Th
e M
eteo
r P
roje
ctSome history
• White paper
• Sponsors believe in the concept
• A convergence effort
• Development of Pilot
• Community awareness
• Enterprise software development
Th
e M
eteo
r P
roje
ctConvergence: Data Transport
September 2000 AprilMarch
SOAP [NCHELP ESC]
SOAP [SFA]
ebXML [PESC]
“Simple SOAP” [Meteor]
Th
e M
eteo
r P
roje
ctConvergence: Business Messages
June 2000 MayDecember
CommonLine XML [ESC]
LoanML [IFX]
Common Record [SFA]
CommonLine R5 [ESC]
Th
e M
eteo
r P
roje
ctConvergence: Authentication
December 2000 JuneMarch
SFA [NCS Proprietary]
SAML [Oasis]
S2ML [Netegrity]
AuthML [Securant]
XTASS [VeriSign]
Internet 2 [Shibboleth]
Th
e M
eteo
r P
roje
ctThe pilot demonstration
• To show the operation of Meteor, the demonstration presentation included the uPortal with a Meteor Channel on the top half of the screen and a secure telnet session showing the flow of traffic--specifically the SOAP messages that included in the XML content--to and from the Meteor server, on the bottom half. (A sample screen follows)
• The demonstration was a dial-in connection, to the Internet, accessing servers in the Washington, DC office. The dial-in connection was operating at 28.8 Kilobits per second (roughly 2,900 characters per second) . The message turnaround was less than one second.
January 13 and 17, 2001, Bal Harbour, Florida
Th
e M
eteo
r P
roje
ctSplit screen demonstration
Th
e M
eteo
r P
roje
ctMeteor student authentication
Th
e M
eteo
r P
roje
ctMeteor XML Request message
>>(Tue Jan 09 11:50:58 EST 2001) Processing SOAP request...
<SOAP-ENV:Envelopexmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd="http://www.w3.org/1999/XMLSchema"xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Body> <ns1:getLoanHistorySOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml"xmlns:ns1="urn:ifx-loan-server"> <IFXRequestEl> <IFX>
<SaisSvcRq><RqUID/><SPName>gov.studentclearinghouse</SPName><LoanHistoryRq>
<CustId><SPName>gov.ssa</SPName><CustPermId>448377707</CustPermId>
</CustId><DateOfBirth>1980-09-03</DateOfBirth>
</LoanHistoryRq></SaisSvcRq>
</IFX> </IFXRequestEl> </ns1:getLoanHistory></SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Th
e M
eteo
r P
roje
ctMeteor XML Response message [1]
Launching query ...
>>(Tue Jan 09 11:50:59 EST 2001) Sending SOAP response...
<SOAP-ENV:Envelopexmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd="http://www.w3.org/1999/XMLSchema"xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Body> <ns1:getLoanHistoryResponseSOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml"xmlns:ns1="urn:ifx-loan-server"> <return> <IFX>
<SaisSvcRs><Status>
<StatusCode>0</StatusCode><Severity>Info</Severity><StatusDesc>Successfull Retrieval</StatusDesc>
</Status><RqUID/><SPName>gov.studentclearinghouse</SPName><LoanHistoryRs>
<CustId>
<SPName>gov.ssa</SPName><CustPermId>448377707</CustPermId>
</CustId><CustName>
<FirstName>Sue</FirstName><MiddleName>B</MiddleName><LastName>Smith</LastName>
</CustName>continued
Th
e M
eteo
r P
roje
ctMeteor XML Response message [2]
<CustInformation><DateOfBirth>1980-09-03</DateOfBirth><PreviousPermId> </PreviousPermId><FormerLastName/>
</CustInformation><StudentStatus>
<CurrentlyEnrolled>Y</CurrentlyEnrolled></StudentStatus><LoanInformation>
<LenderIdType>OPEID</LenderIdType><LenderId>824607</LenderId><LenderName>Oklahoma Student Loan Authority</LenderName><SchoolIdType>OPEID</SchoolIdType><SchoolId>003152</SchoolId><SchoolBranch>00</SchoolBranch><SchoolName>University of Central Oklahoma</SchoolName><InformationSourceIdType>OPEID</InformationSourceIdType><InformationSourceId>824607</InformationSourceId><InformationSourceName>Oklahoma Student
Loan Authority</InformationSourceName><InformationSourceDate>2000-09-30</InformationSourceDate>
</LoanInformation>
continued
Th
e M
eteo
r P
roje
ctMeteor XML Response message [3]
<LoanInformation><LenderIdType>OPEID</LenderIdType><LenderId>809063</LenderId><LenderName>Bank of Oklahoma</LenderName><SchoolIdType>OPEID</SchoolIdType><SchoolId>003152</SchoolId><SchoolBranch>00</SchoolBranch><SchoolName>University of Central Oklahoma</SchoolName><InformationSourceIdType>OPEID</InformationSourceIdType><InformationSourceId>809063</InformationSourceId><InformationSourceName>Bank of Oklahoma</InformationSourceName><InformationSourceDate>2000-11-12</InformationSourceDate>
</LoanInformation><LoanInformation>
<LenderIdType>OPEID</LenderIdType><LenderId>831163</LenderId><LenderName>First Oklahoma bank & Trust</LenderName><SchoolIdType>OPEID</SchoolIdType><SchoolId>003152</SchoolId><SchoolBranch>00</SchoolBranch><SchoolName>University of Central Oklahoma</SchoolName><InformationSourceIdType>OPEID</InformationSourceIdType><InformationSourceId>831163</InformationSourceId><InformationSourceName>First Oklahoma
Bank & Trust</InformationSourceName><InformationSourceDate>2000-10-16</InformationSourceDate>
</LoanInformation></LoanHistoryRs>
</SaisSvcRs></IFX> </return> </ns1:getLoanHistoryResponse>
</SOAP-ENV:Body> </SOAP-ENV:Envelope>
Th
e M
eteo
r P
roje
ctuPortal Meteor Channel - loan list
Th
e M
eteo
r P
roje
ctPilot detail inquiry implementation
Access Provider Website
National StudentClearinghouse
National StudentClearinghouse
Loan Locator ListLoan Locator List
Student AuthenticationStudent Authentication
Home PageHome Page
•Loan 3•Loan 2•Loan 1
PHEAAPHEAAGreat LakesGreat LakesSallie MaeSallie Mae
Th
e M
eteo
r P
roje
ctWhat we learned...
• The XML/SOAP business message turnaround is less than 1 second; the industry’s best sites are 3 to 5 seconds
• Because of the scope of authorization for access and different uses, Meteor needed two separate channels
• Student and parental access to the student’s information
• Financial aid professionals access to information about students
Th
e M
eteo
r P
roje
ctProfessional - Authorization
Th
e M
eteo
r P
roje
ctSelection
Th
e M
eteo
r P
roje
ctDisplay
Why is Meteor important?
Th
e M
eteo
r P
roje
ctThe Meteor software
• Provides an information servicefor students and alumni
• Provides an information resource for financial aid professionals
• Becomes a first step toward implementation of the Department of Education’s real-time “Common Origination and Disbursement” -due in 2003
Th
e M
eteo
r P
roje
ctMeteor software will be available as:
• A channel in JA-SIG’s uPortal 2.0 or later
• A Java servlet that can in incorporated into any Website that supports servlets
• Possibly a channel in Apache Foundation’sJetSpeed portal (also IBM’s general portal)
The school experienceAuthentication, a barrier to
implementation
Th
e M
eteo
r P
roje
ctAuthentication and authorization
• “Level of identification”
• Incomplete standard protocols for authentication or authorization
• Web Single Signon • Internet2/Shibboleth (now Dec 2001)• SAML Security Assertion Markup
Language
• Indeterminate policies and procedures
• Legal - new law and lack of precedents• Lack of business experience
Th
e M
eteo
r P
roje
ctBoston College expectation
• Only ”regular” students and employees in the financial aid office will access Meteor through the College’s secure portal.
• The National Student Clearinghouse, and subsequently others, will “trust” the Boston College authentication.
Th
e M
eteo
r P
roje
ctThe “trusted” college
Secure Collegeenvironment
Secure Internetconnection
Employee Boston CollegeEmployee Boston College Clearinghouse Clearinghouse UserUser Access ProviderAccess Provider Data Provider Data Provider
User logonand password
College logonand password
Loan list messageWeb presentation
Th
e M
eteo
r P
roje
ctAs a proxy service
Secure collegeenvironment
Secure Internetconnection
Student collegeStudent college Clearinghouse Clearinghouse UserUser Access ProviderAccess Provider Data Provider Data Provider
User logonand password
User logonand password
Loan list messageWeb presentation
Th
e M
eteo
r P
roje
ctMeteor supports localization
• Why localize Meteor?
• The Meteor channel becomes consistent with the access providers “look and feel”
• The user has a consistent experience
• Users can use local authentication to achieve “single signon”
_______________________
Personalization combined with localization and useful local content (channels), increases user satisfaction and their loyalty to a particular Website or portal.
Delete this slide
Th
e M
eteo
r P
roje
ctMeteor Project standards
Implements SFA’s information technology standards
• Business messaging using XML
• Software components using Java
• Systems design using UML
• Data transport using Internet, SSL/TLS, and SOAP
• Directory of Participants using UDDI
SFA Software Developers ConferenceMarch 2001
Feb2000
Mar2001
Delete this slide
Th
e M
eteo
r P
roje
ctWhy is that important to schools?
• Schools need to implement XML business messaging to participate in Common Origination and Disbursement (COD)[Real-time in 2003]
• Schools need to use Java to implement SFA’s Java based software components
Need analysis EFC, entrance and exit interviews, and Pell Grant computationDelete this slide
Th
e M
eteo
r P
roje
ctCan Meteor access school systems?
• We are briefing student information system vendors about the Meteor software and implementations
• The Meteor sponsors will determine a schedule to release the software and documentation to vendors
• Software developers may test using the Meteor development site--it is open to anyone for demonstration and testing
Delete this slide
Th
e M
eteo
r P
roje
ctVersions of the Meteor channel
• 0.7 - Current version support loan lists
National Student Clearinghouse pilot
• 0.9 - Access to lenders, guaranty agencies
NSC multiple guaranty agency, lender pilot
1.0 - Shared authentication, distributed data sources
Delete this slidec
Th
e M
eteo
r P
roje
ctRecommendations to the community
• Invest in the these technologies • XML as used for e-commerce• Java technologies
• Focus on customer behavior and preferences• Students and parents (Student Channel)• Faculty and Staff (Professional Channel)
• Keep an eye on the industry leaders• NCHELP - standards, industry directories• JA-SIG - Portal technology, Java and XML
Delete this slidec
Th
e M
eteo
r P
roje
ctMeteor sponsors
American Education ServicesAmerican Student AssistanceBank OneCollege Foundation, Inc. [NC]The College Board/CollegeCredit Education Loan ProgramConnecticut Student Loan FoundationEducation Assistance CorporationEducation Funding AssociationFlorida Department of Education, OSFAGeorgia Higher Education Assistance CorporationGreat Lakes Higher Education Guaranty CorporationGuaranTec, LLPHigher Education Student Assistance AuthorityIllinois Student Assistance CommissionIowa Student Loan Liquidity CorporationKentucky Higher Education Assistance AuthorityKey Education ResourcesLoanStar Systems, Inc.
Th
e M
eteo
r P
roje
ctMeteor sponsors
Michigan Higher Education Assistance AuthorityMontana Guaranteed Student Loan ProgramNational Student Loan Program, Inc.New Hampshire Higher Education Assistance Foundation New York State Higher Education Services Corporation North Carolina State Education Assistance Authority Northwest Education Loan Association (NELA)Oklahoma Guaranteed Student Loan ProgramOregon Student Assistance Commission Panhandle-Plains Student Loan CenterRhode Island Higher Education Assistance AuthoritySallie Mae, Inc.Southwest Student Services CorporationStudent Loan Finance AssociationStudent Loan Guarantee Foundation of ArkansasStudent Loans of North DakotaTexas Guaranteed Student Loan CorporationUnited Student Aid FundsVermont Student Assistance Corporation
Th
e M
eteo
r P
roje
ctAnd we had help...
• The National Student Clearinghouse’s Roberta Hyland and Joy Wang provided data access and programming assistance to make their database available to Meteor users.
• Interactive Business Solutions Software Engineer (and Harvard University graduate student) Peter Karchenko joined the Meteor team working on the project.
• Priority Technologies, Inc. extended the Meteor software and contributed the UDDI/WDSL implementation.
• Credit Online’s Dennis Warnke and Glenn Leyba shared LoanML drafts and their experience implementing IFX SOAP messaging.
• Great Lakes’ Steve Marganeau provided CommonLine XML as it was being produced in December 2000.
• Sigma Systems Inc.’s Andy Sprague provided test data and design guidance and Randy Timmons gave Meteor briefings and demonstrations.
The endwww.meteorproject.org
www.meteorproject.net:8080/portal/and
www.immagic.com