Readmissions Automation Project


General Overview of Readmissions Process6.jpg
Quick View
Summary: 

Design and implement automated processes to support evaluation of Readmit applicants. On average it takes 45 minutes to manually process a readmit application.

 Historical Volumes:

Fall '06 - Sprg '07:  7410

Fall '07 - Sprg '08:  7049

Fall '08:                2217 (as of 6/23/08)

Total:                16,676

 

Start Date: 
April 16, 2008
Go Live: 
June 15, 2009
End Date: 
June 30, 2009
Current Milestone: 
6/30/09- Follow-up and Close
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
James Rund, Vice President of University Student Initiatives
Project Manager: 
Marilyn Shipp/Kelley Brundage
Contact for more information: 
Marilyn.Shipp@asu.edu
Associate VP University Technology: 
Max Davis-Johnson
University Technology Director: 
Leah Lommel
More Info
Source: 
Executive
Priority: 
Medium
Scope: 

• Define document tracking needs
• Define rules and outcomes
• Define setups and process needs for auto decision
• Define rptg needs
• Development
• Implementation

Model after UGA existing processes. Explore utilizing same underlying architecture.
May be influenced by "ASU On-Line" Project.

All Milestones and Schedule: 

• Define scope 5/30/2008 - complete
• Gather requirements 8/1/2008 - complete
• Develop implentation project plan 8/1/2008
(Development and implemention will be in value-added phases)
• Checkpoint
• V1.0 Develop, Test, Implement assign eval group & initial ratings 9/15/2008 - complete
• V2.0 Develop, Test, Implement acquire & eval documents 2/15/2009 - complete
• V3.0
Develop, Test, Implement assign addtn'l ratings 5/30/2009 - complete
(note: 4/22/09 additonal rating value needed due to change in Cronkite admission requirements)
Develop, Test, Implement auto admit 6/15/2009 - complete
Develop, Test, Implement dept rptg 6/25/2009 - complete
• Follow-up and close project 6/30/2009

.

Deliverables: 

• Process Flow - complete
• Rules Documents - complete
• Use Cases - complete
• Implementation Project Plan - complete
• Business Process Guide/Job Aide - complete
• Value added components (implement in groups)
V 1.0 - complete
V 2.0 - complete
V 3.0 - complete
Note: Using committees is not in scope. This will be its own project if areas determine it adds value.

Risk & Threats: 

developer schedule
bundles and fixes testing
21'st day cleanup/rptg
end of semester processing
changes in admissions requirements

Syndicate content