Critical Strategic (Scope) Issues

Once the strategic issues below have been considered and resolved by the Integrated System Executive Committee, a hyperlink will take you to the detail of the issue.


Issue
Resolution
Resolution Date
Removing the social security number (SSN) as the key identifier for students is within the scope of the Student System Project. University ID will be held in PS Campus ID field and used as key identifier for most systems. Provision of SSN to auxiliary systems will be limited to systems that require SSN or that cannot accommodate University ID. For those that do not require SSN, SSN will be masked.

1/24/06 (in scope)
1/24/08(resolved)

Establishment of an “@mail.virginia.edu” email address as the University’s official and primary mode of communication with enrolled students is within the scope of the Student System Project. In light of University policy IRM-016, Use of Email for Official Communication with Students, and with guidance from the Office of General Counsel, ITC will modify security training, required for all new students, to incorporate the new policy and raise awareness around it.  Security training will be modified for students entering the University in fall 2009; in the interim ITC will coordinate with Student Affairs to communicate the policy to enrolled students.
1/24/06 (in scope)
9/16/08(resolved)
All schools and key participants of the University are within the scope of the Student System Project. Any schools or key participants that do not want to use elements of the student system or that wish additional functionality outside of PeopleSoft according to the project’s guiding principles will submit requests for exceptions that will be evaluated and decided by the IS Executive Committee.
1/24/06 (in scope)
1/24/08(resolved)
Consideration of an automated, University-wide degree audit solution is within the scope of the implementation of a new student information system. The University will implement delivered degree audit functionality, “Academic Advisement,” within PeopleSoft.

3/1/06 (in scope)
7/5/07 (resolved)

Consideration of a University-wide solution for the allocation of instructional space and the reservation of non-instructional space is within the scope of the implementation of a new student information system. The commercially available Resource 25 interface will be installed and used with PeopleSoft for instructional space allocation.
3/1/06 (in scope)
1/24/08(resolved)
Consideration of the relationship between portal functionality for the new student information system and other extant University portals is within the scope of the implementation of a new student information system. SSP has included portal functionality in its project plan and has created a project team for the implementation of PeopleSoft Enterprise Portal, which will be implemented and integrated with PeopleSoft Campus Solutions.
3/1/06 (in scope)
1/24/08(resolved)
Consideration of course management functionality (including functionality already in use or developed within the University, a commercial, off-the-shelf solution, or functionality delivered by a new student information system) is within the scope of the implementation of a new student information system. The University has selected Sakai, an open-source online collaboration and learning tool, to replace Instructional Toolkit as its course management system. ITC and SSP are developing a project plan to coordinate the implementation of “UVa Collab” and PeopleSoft respectively.
4/18/06 (in scope)
1/24/08(resolved)
Consideration of an interface with course evaluation functionality is within the scope of the implementation of a new student information system. The University will implement a course evaluation system compatible with Sakai. This implementation will be coordinated with the PeopleSoft implementation.
3/1/06 (in scope)
1/24/08(resolved)
Expansion of document management functionality or implementation of a University-wide document management solution is within the scope of the implementation of a new student information system. As negotiated between ITC and SSP, the student system group is responsible for managing the University’s ImageNow contract where ImageNow has been defined to be within the scope of the student system – used for the purpose of storing or reviewing applicants’ or students’ records
3/22/06 (in scope)
10/7/08 (resolved)
An interface with the Advance system is within the scope of the implementation of a new student information system.
In accordance with recommendations provided by the executive University leadership, SSP is developing a view of limited applicant and student data to Advance, the fundraising and donor relations solution utilized by the Office of Development and Public Affairs.  The view is scheduled to be available by April 2009.
4/18/06 (in scope)
9/16/08 (resolved)
The acceptance and issuance of electronic transcripts is not within the scope of the implementation of a new student information system. Not in scope.
7/24/06 (not in scope)
Consideration of the conversion of ISIS, departmental, and legacy data from other systems is within the scope of the implementation of a new student information system. Create a shadow Oracle database of the ISIS database and supporting files that will serve as an intermediate data base for data conversions
3/22/06 (in scope)
8/3/07 (resolved)

Implementing a comprehensive e-Commerce solution for student-related charges is within the scope of the implementation of a new student information system. The University will implement an e-Commerce solution using Infinet.
4/18/06 (in scope)
8/3/07 (resolved)

BACK TO TOP