220 likes | 664 Views
ATLAS. Articulated Transfer Linked Audit System. ATLAS Presentation Overview. Introduction Planning Campus Participation & Funding Campus ATLAS Plan Elements Software and Hardware Installation Training Communication Teams Survey Analysis MOU’s Future Meetings. ATLAS Introduction.
E N D
ATLAS Articulated Transfer Linked Audit System
ATLAS Presentation Overview • Introduction • Planning Campus Participation & Funding • Campus ATLAS Plan Elements • Software and Hardware Installation • Training • Communication • Teams • Survey Analysis • MOU’s • Future Meetings
ATLAS Introduction • Assists students & counselors consider transferring credits between: • Schools • Academic Programs • Gateway to campus’ • Automated transfer articulation processes • Automated degree audit processes • Campus sites that assist planning transfers • Web based with lots of optional features • Each campus charts own timing and path
Planning Campus Participation • Campus ATLAS Plan • Prepared by campus ATLAS team • Current Status • Planned End-of-Phase 1 Status • Timeline with milestones • Audit and articulation accuracy is more important than initial implementation • Interdependence of all campuses in the system
Campus ATLAS Plan Elements -Areas to cover in Timeline • Automate Articulation Rules using your SIS • Automate Degree Audit Rules using your SIS • CAS Startup • Implement each CAS Feature selected for your campus • Other campus-specific, ATLAS-related • On-Campus promotion(s)
Campus ATLAS Plan Elements -CAS Implementation • For each selected CAS Feature • In test mode • Appropriate disclaimers • Adjust configuration and web aspects • Install interface (if applicable) • Add feature to training & user manuals • Train & Test • Cutover to production • Get the word out at your campus
CAS Server • Determine logistics for server(s) • Negotiate licensing agreements with vendors • Software/Hardware Installation (Centrally Coordinated) • Install CAS • Test • Ready for campus use – projected date: 5/31/06
Implementation Considerations • DARS/CAPP • Which interfaces? • Web • Currency of information • Disclaimers • Common access, statewide front-page for all users • Campus CAS introductory page • Consistent course numbers • All Receiving campuses use same as Sending campus
Funding - Statewide • Chancellor’s office funding covers: • CAS License (OUS only) • Planning Guide Interface License (OUS only) • Import Transcript Interface License (OUS & CC) • CAPP Interface/contingency • Project Coordination & some training & promotion
Funding - For Campuses • Chancellor’s office also provides: • Vendor installation-related fees • Both interfaces for OUS Campuses • Import Transcript interface for 2 or 3 CC Campuses • Assistance automating articulation & degree audits (OUS Campuses only) Notes: • Funding is contingent upon campus plans • June 30, 2007 Funding deadline(promotion expected in fall 2007)
Funding - Recurring Costs • Chancellor’s office funding supports initial development and implementation, only • Campuses will have to immediately support recurring costs for: • Articulation agreement maintenance • Automated transfer articulations maintenance • Automated degree audit maintenance • ATLAS related IT labor, software & hardware
Training • Determine Training Needs • To use CAPP (or DARS) • To Configure CAS • 1 or 2 people per campus (web-based) • To use CAS (later in the process) • Advisors • Students • Possible Approaches • Train trainer & travel to campuses • Web based • Attend outside classes
Communication • Communication with Vendors • Our IT and Functional spokespersons • Project Communications • What are your preferences? What works? • Publicity (to occur later): • Local or statewide (or both)? • Who are the audiences? • Which methods? • What exists now that could be used? • What else must be developed? • Who is responsible and who pays?
Team Structures • Campuses should determine local teams, likely to include: • Administration • Degree audit/certification • Transfer articulation • Advising • IT support • Student(s)? • Campuses select one ATLAS delegate for Steering Committee (along with another for IDTS) • Working groups (up to 6 campus reps per group) • Articulation • IT • Others needed?
Survey Analysis & Discussion • Review the synthesized results • What patterns do you notice in the responses to each question? • What clarifications are needed to determine the “real answers” to unclear or incomplete responses? • What issues need further discussion? • What additional questions emerge from the survey responses? • Implications (drawn from group discussion):
MOU Discussion • To stay friends by developing common expectations, especially about exchanging money • Primary transactions to make clear: • Distribution of CO funds • Financial point person • Payment for recurring software fees • Payment for centrally provided, on-going services • Other? • Timeframe for meeting with each campus
Future Meetings and Q&A • Steering Committee Meetings • March 29th in Portland • April 26th in Eugene • May 24th in Portland • Last week of July • Last week of October • Last week of January • Articulation Working Group • When? • IT Working Group • When?