Post on 01-Jan-2016
Information for New Workgroups
Rob BoisenManager, Industry & Government Relations Great Lakes Educational Loan Services, Inc.
May 2006
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
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
Initial Project Steps
• Document the standard to be developed including:– Business drivers– History– Expected Outcomes– Benefits – Need for collaboration
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
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
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.
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
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”
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
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
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
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
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
Review by Submission
Advisory Board & Steering
Committee
Approved?
Notification toSteering
Committee
PESCMembership
shop vote
Step One: Request
Made Initial Submission
Change Control Board
Review
Step Two:
Workgroup Formed –
Submission Development
Step Three: Completed Candidate Proposed
Step Four: Public
Comment
Step Five: PESC Membership Vote
Step Six: Ratification
Returned withExplanation
Workgroup Formed
Approved?
Approved?
Returned for additional information
Returned with Explanation
Standards Submission and Approval Process
N
Y
N
N
Y
Y
Using the XML Registry and Repository
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
Improving your Business with Standards and Technology
Panel Discussion
May 2006
Oracle Corp.
Curtiss BarnesSenior Director, Applications Strategy
Education & Research
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…
Oracle Fusion Architecture
Unified Portal
Business Process OrchestrationProcess models BPEL Engine
Fusion Service BusMulti-protocol routing
Message transformationServices and Event Mediation
Grid Computing
Activity Monitoring
Fusion Service RegistryApplication Integration Services
Process Integration ServicesData and Metadata Services
BusinessIntelligence
Clustering SecurityProvisioning ConfigurationData Management DirectoriesIdentity Management Web Cache
Oracle Apps Custom Apps ISV Apps
Sta
nd
ard
Dev
elo
pm
ent
Fra
mew
ork
Secu
rity, Man
agem
ent &
Mo
nito
ring
A Reference to support heterogeneous environments
Oracle Fusion ArchitectureStandards 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 Apps Custom Apps ISV Apps
JMX
, SA
ML
1.1, SA
ML
2.0
J2E
E,
JSF
, E
JB 3
.0,
SD
O…
e-EducationFrameworkEcosystem of Integration and Business Process Orchestration
Portal & Collaboration Solutions
Business Activity Monitoring
Registry, Services, Integration Protocols
Business Intelligence
SE
CU
RIT
Y
MA
NA
GE
D S
ER
VIC
ES
Legacy Apps Custom Apps ISV Apps
Grid ComputingClustering SecurityProvisioning ConfigurationData Management DirectoriesIdentity Management Web Cache
Business Process OrchestrationProcess models BPEL Engine
ApplicationsStudent Administration Grants ManagementAcademic Management ProcurementHuman Resources Asset ManagementFinancials/GL CRM
Constituents: Students, Faculty, Staff, etc.
E X A M P L E
Student Enrollment
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 Serviceor Other Application
Supplier
Student Online Application
MarketingShipping (UPS)
Finance (AR)Evaluate CredentialsVerify Transfer Credits
Degree Audit
Acceptance--Eligible to Enroll
Enroll
Provisioning
Bookstore
Pay Tuition
LibraryHousingID, etc.
Adaptive when you need to change your processes or services:
Outsourced
Recruiting &Admissions
Student
Shared Serviceor Other Application
Supplier
Student Online Application
MarketingShipping (UPS)
Finance (AR)Evaluate CredentialsVerify Transfer Credits
Degree Audit
Acceptance--Eligible to Enroll
Enroll
Provisioning
Bookstore
Pay Tuition
LMS
Student-Life Progress
LibraryHousingID, 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
Datatel, Inc.
John Van WeerenProduct Manager, Technology
B2BConnectivity
CollaborativePortal
Ecosystem Driving Standards
Enterprise Service Bus
B2B Connections and Remote Web Services
Other Enterprise Business Systems
Business Process Orchestration
Colleague ApplicationsBusiness
IntelligenceEnterprise Data
SA
S
Bu
sin
ess
Ob
ject
s
AS
G
System Administration(SA Valet) Mes
sag
ing
Gat
eway
Copyright Datatel, Inc. -- Strategic Software Architecture
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
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
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
SunGard Higher Education Involvement
Ed HauserExecutive Director Student & Enrollment Services
Solutions
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
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
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
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
Contact Information• If you have questions or need additional information,
please contact:
– Curtiss Barnes curtiss.barnes@oracle.com
– Rob Boisen rboisen@glhec.org
– Ed Hauser Ed.Hauser@sungardhe.com
– Monique Snowden monique@oar.tamu.edu
– John Van Weeren jvw@datatel.com