Student System Project

1
Student System Project

SSP Update January 19, 2006
2
What is our purpose? Whats the vision?

• To provide a state-of-the-art, enterprise-wide,
  student information system
• We envision a system that enables all
  student-related administrative processes (from
  recruitment and application to graduation and
  beyond) to be carried out electronically, with
  only value-added manual effort required by
  students, faculty, and/or staff.

3
Why are we doing this?

• To provide a system that satisfies the
  expectations and needs of todays students and
  fulfills the Universitys current and future
  requirements

4
When?

• Business
• Process Analysis January October
• Peer Study
• February - December
• Vendor Evaluation
• September March
• Define scope,
• timeline, budget January March
  
• Jan Feb Mar Apr May Jun Jul Aug Sep
  Oct Nov Dec Jan Feb Mar
• 2005

2006
5
How will we accomplish this?

• Respect Requirements
• Tap University-wide expertise
• Solicit peer institution input
• Prioritize Requirements
• Plan Strategically
• Develop governance structure
• Involve stakeholders

6
Tap University-wide expertise

• Identified and validated processes through
  University-wide participation in workshops
• Developed appreciation for and understanding of
  what we do across the Universitydiscovered
  similarities and differences, discussed pain
  points, identified requirements
• Community set the project agenda

7
Tap University-wide expertise

• DecisionDirector
• Community used software to evaluate and
  prioritize over 2,500 student system requirements
• Vendors assessed whether their product meets our
  high priority requirements
• Other universities assessed whether their student
  system software meets our high priority
  requirements

8
Solicit peer institution input

• Contacted 35 schools representing 4 software
  vendors visited 5
• Lessons learned regarding implementation,
  features, best practices
• Key takeaway we arent the first we can learn
  from the experiences of others
• Narrowed to two viable vendors PeopleSoft and
  Banner

9
Plan Strategically

• Develop governance structure and involve
  stakeholders
• Integrated System Executive Committee
• Student System Policy Review Group
• Core Advisors to the Student System (CASS)
• Faculty Advisors to the Student System (FASS)
• Student System Advisory Committee (SSAC)
• Technical Advisors to the Student System (TASS)
• Student Advisors to the Student System (SASS)

10
Next Steps

• Continue to examine business processes
• Refine scope
• Select software vendor
• Choose consulting partner

11
Who?

• You
• Contact us StuSys_at_virginia.edu
• Subscribe to our mailing list
• Follow the SSP website at
• www.virginia.edu/integratedsystem/studentSysProj/