Strategic Issue Issue: Whether consideration of the relationship between portal functionality for the new Student Information System (SIS) and other extant University portals is within the scope of the implementation of a new SIS. PRISM #: 102 Student System Project Contact (PRISM Issue Owner): Charles Grisham Scope Type: Issue Priority: General | Critical | School/Unit Issue | High | Medium | Coordinating Project| New Functionality Low Impact Statement: Best practice among colleges and universities is to deliver 24x7 self-service capabilities to students through an integrated portal. With an integrated portal, the University can provide efficient access to secured student system functionality using technologies that also provide single sign-on for administrative applications. Systems that support administrative processes for students currently range from third-party solutions to locally designed Excel files and Access databases. These systems support all phases of the student cycle including recruitment, admission, registration and records, student finance, degree audit, and advising. From a service model perspective, students currently must contact many different points to solve a problem or get information, and faculty advisors contact many different points to serve and advise students or to get information. Portal functionality will deliver effective self-service to students, and this interface should be the primary point of access for students to administrative systems. Implementation of a new SIS affords an opportunity for the University to consider likewise a single point of access to all administrative systems by connecting the SIS to the Integrated System or to create an Enterprise portal that delivers comprehensive access to information and for most users to the majority of the University’s automated capabilities. Although the University is making progress toward building single sign-on through the implementation of NetBadge for webbased applications, continued and visible improvement in integrating many applications such as email, the Integrated System, ISIS, faculty advising, and calendar access through single sign-on is highly desirable in the context of portal functionality. Currently, the MyUVa Portal, used by all new, incoming undergraduate students, employs both true single sign-on with NetBadge and “virtual” single sign-on in which users can store application-specific IDs and passwords on MyUVa so that MyUVa can provide the illusion of single sign-on. Sign-on capability of this sort will be necessary for as long as we have systems whose authentication we cannot modify or control. Many of the student system vendors under consideration by the University deliver integrated portal software that enables selfservice and supports single sign-on within their delivered applications. The vendors deliver and maintain the integration of the application with the portal. Options and Implications: 1. Consideration of the relationship between portal functionality for the new SIS and other extant University portals is outside the scope of the implementation of a new SIS. In this option, the University will forego the opportunity to integrate delivered SIS functionality with other University applications such as the Integrated System and perpetuate a multi-point-of-access situation. 2. Consideration of the relationship between portal functionality for the new SIS and other extant University portals is within the scope of the implementation of a new SIS. Provision of single sign-on should be a consideration. In this option, the University might choose to: a. consider portal functionality solely to provide access to the functionality of the new SIS and student-related activities; b. implement a delivered SIS portal and connect it to the Integrated System, or c. create an Enterprise portal that delivers information and access to most of the University’s capabilities Recommendation: Option 2: Consideration of the relationship between portal functionality for the new SIS and other extant University portals, including a provision for single sign-on, is within the scope of the implementation of a new SIS. Dependencies: The University’s desire to consider the overall strategic approach to portal functionality The functionality of a vendor-supplied portal within the new SIS Consultation from several areas of ITC Consultation from ISDS Consultation from system and hardware vendors Information from peer institutions that have done single-sign-on implementations Involvement of the offices of Development, Alumni, Arts and Sciences Communications, the Libraries, and other offices that manage and require sign-on and authentication Next Steps (if in scope): The consideration of portal functionality that supports self-service activities of students, faculty and staff and that considers University-wide single-sign-on and central authentication and authorization will be considered by an appropriate working group that includes broad representation from ITC and high-level decision makers. The University should review the charge, composition, and leadership of the My UVa Portal Advisory Committee to determine whether/how this committee and its membership may be leveraged to comprise an appropriate working group to consider portal functionality for the new SIS. Deadline for Executive Committee: Decision by Executive Committee: Option 2: Consideration of the relationship between portal functionality for the new SIS and other extant University portals, including a provision for single sign-on, is within the scope of the implementation of a new SIS. Executive Committee Reviewer/Approver: Full IS Executive Committee Signature of Reviewer: Gene Block Date: 3/1/06