Agenda  Message Class Update  SAIG Transmission Header Changes  School Testing  Software Developer Feedback

Message Class Options  Full Participants will be able to choose the message class in which they send and receive documents to and from the COD System.  Message class options will include the following:  Non-program specific and non-award year specific  Non-program specific and award year specific  Program specific and non-award year specific  Program specific and award year specific  Each system generated Doc Type will have its own message class.  Message class options apply to the award year only.

Message Class Options  Some of the message class names presented at the last conference have been modified to include a more user-friendly naming convention. OLD NAMENEW NAME CRAA05INNo change CRAR05OPCRAA05OP CRPA05IN CRPG05IN CRPA05OP CRPG05OP CRDA05IN CRDL05IN CRDA05OP CRDL05OP CRCB05IN No change CRCA05OP CRCB05OP OLD NAMENEW NAME COMRECIN No change COMRECOPNo change CRPAMYIN CRPGMYIN CRPRMYOP CRPGMYOP CRDAMYIN CRDLMYIN CRDRMYOP CRDLMYOP CRCAMYIN CRCBMYIN CRCRMYOP CRCBMYOP YEAR SPECIFICNON-YEAR SPECIFIC  See the COD Technical Reference November release for more information.

SAIG Transmission Header  SAIG has increased the variable BAT= field on the SAIG Transmission Header (N*05/N*95) from 26 to 50 characters.  Beginning in March 2004, COD will reserve the first 20 characters of this field for school use and populate the last 30 characters with the Batch/Document ID on response/acknowledgements for all award years.  If a school uses the last 30 characters for other data on the incoming record, COD will overwrite this data with the Document ID or the Batch ID.  EDConnect users must upgrade to EDConnect version 5.3 or higher in order for their records not to reject.

Agenda  COD School Testing  School Testing Documentation  School Testing Timeline  School Testing Process  Lessons Learned

COD School Testing  Purpose:  Provide schools, third-party servicers, and software vendors an opportunity to test business processes and system software in a low- volume, controlled test environment enabling simpler, faster, and less costly issue identification and resolution  Ease the transmission of production data  Reduce the risk of production problems  School Testing Documentation:  School Testing Guide  Test Cases for both Full and Phase-In Participants  COD Technical Reference available on IFAP and FSA Download

COD School Testing Timeline PhaseDates Sign-upDec. 1, 2003 – May 1, 2004 Phase I-Manual Verification Testing Jan. 1, 2004 – May 31,2004 Phase II-Structured Application Testing Mid-March June 30, 2004

School Testing Process 1.Sign-up  Sign-up document is included in Technical Reference Section VII and posted on COD web site  Submit sign-up document to COD School Relations Center via or fax

School Testing Process 2.Receive confirmation from COD School Relations Testing Team that contains:  Testing coordinator contact information,  Scheduled start date to submit files,  What you should expect during your testing experience.

School Testing Process 3.Submit test files  Phase I Manual Verification The COD team manually reviews Common Record document ed to the COD School Relations Center: 1.Verifies schema version, 2.Identifies any potential updates to the Common Record.

School Testing Process 3.Submit test files  Phase II Structured Application Testing by sending files via SAIG. Ensures schools can send, receive, and process batches of records using detailed input instructions. Assists in the identification of potential updates to your system before beginning actual processing

School Testing Process 3.Submit test files  Assistance provided by COD School Testing Team. Clarification of COD Technical Reference, Scheduling of test dates, Assist with issue identification and resolution, Process submitted data, Provide testing technical guidance.

School Testing Process 4. Receive assistance monitoring 1 st “live” batch  The School Testing team will watch for submission of the first batch into the COD Production environment.  After a batch has successfully processed, the School Testing team will turn you back to your primary representative.

School Testing Process 5. Solicit Feedback  During testing, school questions and recommendations are recorded.  After completion, an is sent to participants asking for feedback on School Testing process and experience.  COD School Relations School Testing team also provides feedback.

Lessons Learned RecommendationImplemented More communication to the community about School Testing and the signup process COD will communicate using IFAP, COD Processing Updates, Web Messages, and Conference Presentations Detailed explanation of the Routing ID for Full Participants Added to School Testing Guide Clarification of fields located on the Sign-up Document Added to School Testing Guide

Lessons Learned RecommendationImplemented Discontinue Bulletin Board due to lack of interest from School Testing community Bulletin Board was discontinued Enhanced explanation of ISIR filesAdded to School Testing Guide Speed up set-up process for testing after Sign- up Document is received COD School Relations is reviewing the set-up process for areas of improvement

Lessons Learned RecommendationImplemented Allow for additional testing after COD Testing Cycle is completed Being investigated to see if possible for School Testing Provide sample Pell and Direct Loan origination files and the corresponding Pell acknowledgement files Being investigated to see if possible for School Testing Provide testing environment that mimics the COD System and is available year round for testing with testing scenarios Being investigated to see if possible for School Testing

Contact Us!!  Presenters:Rosemary BeaversCheryl Markiewicz Jim McMahon Lori Clemmensen Mike Murray   Call the COD School Relations Center  PGRANT for Pell Grants  for Direct Loans  COD Web Site (