1. Improving your Business with Technology and Standards May 2006

2. Information for New Workgroups Rob Boisen Manager, Industry & Government Relations Great Lakes Educational Loan Services, Inc. May 2006

3. Initial Project Steps Review the PESC Policies and Procedures Manual –This manual is your roadmap to achieving your goal of developing an industry-accepted, PESC-approved standard

4. Initial Project Steps Review the PESC Policies and Procedures Manual –The manual contains: Information on the Standards Forum Standards Submission and Approval Process The Change Control Process PESC Guidelines for XML Architecture and Data Modeling XML Registry and Repository for the Education Community User Guide

5. Initial Project Steps Document the standard to be developed including: –Business drivers –History –Expected Outcomes –Benefits –Need for collaboration

6. Initial Project Steps Submit Letter of Intent to PESC (Sample Letter available at: www.pesc.org/info/policies-procedures.asp) PESC Accepts the Letter of Intent Submission Advisory Board assigns a “Mentor” –The Mentor will assist the workgroup by guiding them through the standard development process Workgroup Co-Chairs are selected Mentor and the Project Sponsor plan industry conference call Community is notified of the conference call

7. Development Steps Initial Conference Call Goals –Review intent of project –PESC Policies and Procedures Manual (www.pesc.org/info/policies-procedures.asp) –Determine if it is necessary to break projects into phases –Plan for completing project –Set conference call schedule Notes should be taken, appropriately distributed, and posted in the Workgroup Section of the PESC website for each conference call

8. Development Steps Identify business processes that may be impacted by the development of this standard For XML standards, identify data elements currently in use for this process –Gather current standard and/or proprietary formats that organizations are currently using to exchange this data –Resolve redundant, overlapping data –Reach consensus on tag names, business definitions, lengths, contents, etc.

9. Development Steps Review each data element for clarity of purpose and usage Match data elements with the PESC Core Components in the XML Registry and Repository for the Education Community –The Registry and Repository has an excellent search feature that can be used to find components that have already been defined by the Education Community

10. Development Steps Workgroups should verify the status of the components in the Registry and Repository –The Status should be “Approved” –The Status could also contain the values of “Submitted”, “Withdrawn”, or “Deprecated”

11. Development Steps Review to ensure compatibility of elements and identify new elements Each element should be entered into the Core Component Submission Template (www.pesc.org/info/policies-procedures.asp) Submit to PESC for review by the Submission Advisory Board Following review by the Submission Advisory Board, the Core Components are submitted for final review by the Change Control Board

12. Development Steps The new and modified components are updated into the XML Registry and Repository The workgroup then develops the schema according to business rules and PESC Guidelines for XML Architecture and Data Modeling The schema is submitted to PESC Submission Advisory Board for review Following review by the Submission Advisory Board, the schema is submitted to the Change Control Board

13. Development Steps Following review by the Change Control Board, the proposed standard is released for a 30 day public comment period Public comments are reviewed by the workgroup Once all public comments have been addressed, then the proposed standard is submitted to the PESC Membership for a vote The proposed standard must be approved by 80% of the votes cast

14. Development Steps For non-XML standards, the Mentor from the Submission Advisory Board will review the appropriate development steps The review and approval steps are the same regardless of the type of standard being developed

15. Final Approval If the proposed standard receives at least an 80% affirmative vote (of the members who vote), then it is presented to the PESC Board of Directors for ratification Following Board ratification, then the public announcements are released and the schema(s) and appropriate documentation are posted to the PESC website

17. Using the XML Registry and Repository

18. Documentation Complete documentation for the XML Registry and Repository can be found under the “Standards & Info” section of the PESC website by clicking on XML Registry & Repository User Guide – v 1.0.0 or at: http://www.pesc.org/info/policies/XML-R- R-User-Guide.doc

26. Improving your Business with Standards and Technology Panel Discussion May 2006

27. Oracle Corp. Curtiss Barnes Senior Director, Applications Strategy Education & Research

28. Standards – Why? The “elusive 40%” –IT budgets overwhelmed by hard-coded integrations: data integrity and security risk Technology Standards –Reality of heterogeneous environments –Goal: make it behave like one Process Standards –Education at an inflection point? –Darwinian model: change or…

29. Oracle Fusion Architecture Unified Portal Business Process Orchestration Process models BPEL Engine Fusion Service Bus Multi-protocol routing Message transformation Services and Event Mediation Grid Computing Activity Monitoring Fusion Service Registry Application Integration Services Process Integration Services Data and Metadata Services Business Intelligence ClusteringSecurity ProvisioningConfiguration Data ManagementDirectories Identity ManagementWeb Cache Oracle AppsCustom AppsISV Apps Standard Development Framework Security, Management & Monitoring A Reference to support heterogeneous environments

30. Oracle Fusion Architecture Standards drive reality JSR-170, JSR-168, WSRP BPEL XSLT, WSIF, JMS, JBI SQL, WS-Security, WS-Addressing, SAML… JSR-227, SVG UDDI, WSIL, JAX-RPC, WSDL, SOAP, XML Schema JSR-227, SVG Oracle AppsCustom AppsISV Apps JMX, SAML1.1, SAML2.0 J2EE, JSF, EJB 3.0, SDO…

31. e-Education Framework Ecosystem of Integration and Business Process Orchestration Portal & Collaboration Solutions Business Activity Monitoring Registry, Services, Integration Protocols Business Intelligence SECURITY MANAGED SERVICES Legacy AppsCustom AppsISV Apps Grid Computing ClusteringSecurity ProvisioningConfiguration Data ManagementDirectories Identity ManagementWeb Cache Business Process Orchestration Process models BPEL Engine Applications Student AdministrationGrants Management Academic ManagementProcurement Human ResourcesAsset Management Financials/GLCRM Constituents: Students, Faculty, Staff, etc.

32. E X A M P L E Student Enrollment

33. What SOA Will Mean to Higher Education from sequential, siloed, labor intensive, difficult to change Recruiting Admissions to parallel, collaborative, adaptive LMS Student-Life Progress Outsourced Recruiting & Admissions Student Shared Service or Other Application Supplier Student Online Application Marketing Shipping (UPS) Finance (AR) Evaluate Credentials Verify Transfer Credits Degree Audit Acceptance--Eligible to Enroll Enroll Provisioning Bookstore Pay Tuition Library Housing ID, etc.

34. Adaptive when you need to change your processes or services: Outsourced Recruiting & Admissions Student Shared Service or Other Application Supplier Student Online Application Marketing Shipping (UPS) Finance (AR) Evaluate Credentials Verify Transfer Credits Degree Audit Acceptance--Eligible to Enroll Enroll Provisioning Bookstore Pay Tuition LMS Student-Life Progress Library Housing ID, etc. Finance Pay Tuition Acceptance Eligible to Enroll Degree Audit Enroll Degree Audit Verify Transfer Credits Marketing 2. Students can verify transfer credit before submitting application 1. Students must pay tuition before they are eligible to enroll What SOA Will Mean to Higher Education

35. Datatel, Inc. John Van Weeren Product Manager, Technology

36. Ecosystem Driving Standards Enterprise Service Bus B2B Connections and Remote Web Services Other Enterprise Business Systems Business Process Orchestration Colleague Applications Business Intelligence Enterprise Data SAS Business Objects ASG System Administration (SA Valet) Messaging Gateway Copyright Datatel, Inc. -- Strategic Software Architecture

37. Our Philosophy on Standards Two parts when exchanging with partners: –Format of business transaction (data layout) –Negotiate transport parameters (data delivery) Encapsulation (EDI, XML, CSV, etc.) Protocol and routing (IP - sftp, https, etc.) Verification of requester/sender identity Agreement on request/response handling –Both parts needed for standard to be adopted Allows for competition on price and service

38. PESC Benefit/Value to Datatel Completion of DTS (2.0) –Significantly reduce maintenance required for partner/government and B2B transaction interfaces –Focus R&D resources on new functionality Completion of Workgroup Standards –Common Line, Postsecondary Transcript Lowers cost to our clients for transactions Fewer steps and manual handling improves productivity and lowers cost

39. Datatel Involvement in PESC Workgroups –DTS: Expertise and reference implementation source code –Common Record/Common Line –Degree Audit, Transcript, Admissions App Board of Directors – Pete Nalli Steering Committee – John Van Weeren Change Control Board – Graham Tracey

40. SunGard Higher Education Involvement Ed Hauser Executive Director Student & Enrollment Services Solutions

41. SunGard Higher Education Involvement PESC Board of Directors –Jack Kramer, Senior Vice President PESC Standards Forum Steering Committee –Ed Hauser, Chairman 2001-2005 Work Groups – SunGard HE participants  Rhonda Allen, financial aid  Shirley Benson, student  Mark Bolembach, integration  Dayna Flath, student  Sue Laird, financial aid  Jan Levsen, financial aid  Bill Zimmer, student  Others from Plus & Matrix

42. SunGard Higher Education Involvement Work Groups – SunGard HE participants –Postsecondary transcript – DONE! –Common Record: CommonLine (CR: C) –Transcript Request & response –Degree Audit request & response –High School Transcript –Architecture/Tech Committee –Admission Application –On-line loan counseling –Student Aid Inquiry –Test Scores –Data Transport –PECS policies and procedures

43. SunGard Higher Education Involvement GBR Transcript Project –Collaborative development GBR, services & development PESC workgroup –XML Transcript Capability Added XML transcript capability to current transcript request process Includes immunization information Baseline Release 7.3 - May 2006

44. SunGard Higher Education Involvement Community collaboration Importance of collaboration Why we participate? Why clients should participate - if already not? Why collaborate with competitors? “Coopetition” Why others in the community participate? SunGard future plans with PESC standards? –High school transcript –Admission application –PESC workgroup summits and tech conference

45. Contact Information If you have questions or need additional information, please contact : –Curtiss Barnes curtiss.barnes@oracle.comcurtiss.barnes@oracle.com –Rob Boisen rboisen@glhec.orgrboisen@glhec.org –Ed Hauser Ed.Hauser@sungardhe.comEd.Hauser@sungardhe.com –Monique Snowden monique@oar.tamu.edumonique@oar.tamu.edu –John Van Weeren jvw@datatel.comjvw@datatel.com