Articulation and Transfer Clearinghouse (ATC)

1. Articulation and Transfer Clearinghouse (ATC) Articulation and Transfer Advisory Committee December 8, 2005 Ohio Board of Regents Articulation and Transfer Clearinghouse

2. What Does the ATC Need to Provide? • A secure connection between campus student information systems (SIS) and the central ATC • Software that can consistently implement the Council’s policies • Flexibility to respond to changes in policies and changes in technology Ohio Board of Regents Articulation and Transfer Clearinghouse

3. What Are Our Options for Creating the ATC? • Option 1 - Purchase a fully-developed electronic transcript exchange from a vendor that includes interfaces to campuses’ SIS and add policy implementation software • Option 2 – Integrate off-the-shelf software - including policy implementation software - to create the central ATC and make a number of SIS to ATC communication tools available to the campuses • All options require some integration by Board of Regents staff because transcript exchanges do not include policy implementation software Ohio Board of Regents Articulation and Transfer Clearinghouse

4. Recommendation • Option 2 – Integrate off-the-shelf software - including policy implementation software - to create the central ATC and make a number of SIS to ATC communication tools available to the campuses • What does this mean? • Establish standards for the SIS to ATC interface • Identify a number of potential vendors that can provide software conforming to this standard • Support campuses implementing the SIS interface • Create the central ATC by integrating the SIS interfaces with the policy implementation software Ohio Board of Regents Articulation and Transfer Clearinghouse

5. Why is This the Best Option? • Most cost-effective solution overall • Can be implemented in a reasonable timeframe (Q1 prototype) • Flexible • Can support multiple means of connecting SIS to the ATC • Can support and manage policies that change over time • Provides the best means of meeting future requirements: new types of documents or bilateral agreements • Makes use of tools and standards widely used by industry Ohio Board of Regents Articulation and Transfer Clearinghouse

6. Due Diligence: Meetings with Campuses • Franklin University Direction – Fall, 2004 • Pilot Group Discussions – February, 2005 • Joint Requirements Planning – July, 2005 • OACRAO Presentations – November, 2005 • Requirements Reviews • Ohio State University – October, 2005 • University of Cincinnati – November, 2005 • XML Pilot Group – November, 2005 • Northeast Institutions – November, 2005 • Southeast Institutions – December, 2005 Ohio Board of Regents Articulation and Transfer Clearinghouse

7. Due Diligence:Vendor Analysis • Conducted Vendor Interviews – Fall 2005 • XAP, IMS, Pegasystems, Credentials Inc, etc … • Created a Test Bed – November, 2005 • Also • Gartner documents and analysts consulted • Similar activities in other states investigated • Similar activities in other industries investigated Ohio Board of Regents Articulation and Transfer Clearinghouse

8. Next Steps • Central ATC at Regents • Develop detailed project plan • Make final vendor selections • Develop prototype solution • SIS Interfaces at Campuses • Continue to gather SIS information • Finalize specifications for the SIS interface • Identify vendor options for SIS to ATC connections • Develop a campus by campus deployment strategy • Continue to work with CAS on interoperability • Communicate with Campuses through the Leadership Teams Ohio Board of Regents Articulation and Transfer Clearinghouse