Planning the Portal Project Overview of the Plan Presentation to ALL-IT-Managers April 3, 2002 Gould Auditorium

Points of Contact for the Portal Project ACS Portal Project Coordinators ACS Portal Project Coordinators Rick Bloyer Abel Thompson Rick Bloyer Abel Thompson Portal Content Administration Portal Content Administration Office of IT and Office of the Web Master Office of IT and Office of the Web Master

Portals at Other Universities Fresno State: UCLA: Central Michigan University: Arizona State University West: Yale University: California State University at Northridge: The University of Tennessee: Virginia Tech: Indiana University:

Portal Project Objectives Make Enterprise Portal Available to Campus in October 2002 Make Enterprise Portal Available to Campus in October 2002 Manage the Integration of Campus Content Manage the Integration of Campus Content Integrate Campus Administrative Computing Applications into the Portal Integrate Campus Administrative Computing Applications into the Portal

Planned Characteristics of Portal Candidate as Front Door for UofU Web Services – aka (“My UofU Home”) ??? Candidate as Front Door for UofU Web Services – aka (“My UofU Home”) ??? Role-Centric Home Pages Role-Centric Home Pages Personalization of Content and Layout Personalization of Content and Layout Pagelet / Channel Navigation Pagelet / Channel Navigation Links to Campus and Other Content Links to Campus and Other Content Content Management Content Management Gradual Elimination of Heavy Clients for Administrative Computing Applications Gradual Elimination of Heavy Clients for Administrative Computing Applications Eventual Integration of Authentication System Eventual Integration of Authentication System Search Engine Search Engine

Portal Project Phases Phase 1: Project Formulation and Introduction Phase 1: Project Formulation and Introduction Phase 2: Develop and Rollout the Prototype Phase 2: Develop and Rollout the Prototype Phase 3: Integrate HE Upgrade into Portal Phase 3: Integrate HE Upgrade into Portal Phase 4: Delivery and Administration Phase 4: Delivery and Administration

Phase 1: Project Formulation and Introduction Security Model Development Security Model Development LDAP Attributes and Populations, Sign-On Sequence, Roles, Password Mgt, Access Control Lists LDAP Attributes and Populations, Sign-On Sequence, Roles, Password Mgt, Access Control Lists Apply User ID and Password Guidance from the ITEC/ITAC Apply User ID and Password Guidance from the ITEC/ITAC Evaluate and Develop Administration Model Evaluate and Develop Administration Model Upgrade the Portal to 8.4 (Production Version) Upgrade the Portal to 8.4 (Production Version) Introduce the Project to the Campus Introduce the Project to the Campus Address Portal Growth Address Portal Growth

How are Roles Defined in the Current Prototype Central Directory Applicant Student ~3,300 Full Time Student18,809 Grad Student 6,203 Noncredit Student 6,821 Part Time Student23,166 Undergrad Student28,707 Faculty 4,671 Full Time Employee12,079 Part Time Employee 8,598 Alumni ~60,000 Retiree 1,631 The number of roles will grow and grow and ….

Phase 2: Develop and Rollout the Prototype Further Develop and Test the Security Model LDAP Attributes and Populations, Sign-On Sequence, Roles, Password Mgt, Access Control Lists Further Develop and Test the Security Model LDAP Attributes and Populations, Sign-On Sequence, Roles, Password Mgt, Access Control Lists Further Integration of Authentication Further Integration of Authentication Support Campus Content Manager Support Campus Content Manager Integrate PeopleSoft HE 7.5 and Fin 7.0 Integrate PeopleSoft HE 7.5 and Fin 7.0 Integrate other Campus Admin Computing Applications Kronos, Brass Integrate other Campus Admin Computing Applications Kronos, Brass Plan Portal Growth Plan Portal Growth

Phase 3: Integrate HE Upgrade into the Portal Requirements Drafting for the Upgrade Requirements Drafting for the Upgrade Integrate HE 8.16 into the Portal Integrate HE 8.16 into the Portal Test the Upgrade Test the Upgrade (Beta) Test the Portal (Beta) Test the Portal Plan Portal Growth Plan Portal Growth

Phase 4: Delivery and Administration Deliver the Portal to the Campus in October 2002 Deliver the Portal to the Campus in October 2002 Administration of Live Portal Administration of Live Portal Plan Portal Growth Plan Plan Portal Growth Plan

Q&A 1. How Does a Department or User Suggest Content? Answer: Through the existing processes, by suggesting new portal content through the Campus Web Master. Portal technology allows users to recommend sites while on line. 2. Will a UofU Working Portal Be Available for View Before the Project Goes Live? Answer: Yes, the portal may be beta tested on campus Answer: Yes, the portal may be beta tested on campus before its release and shown to groups interested in before its release and shown to groups interested in seeing it / accessing it. seeing it / accessing it.

Q&A 3. Can the Portal LDAP be used as the central authentication service for other applications on campus? 3. Can the Portal LDAP be used as the central authentication service for other applications on campus? Answer: It could be. A needs assessment should be performed to highlight these issues and answers. Answer: It could be. A needs assessment should be performed to highlight these issues and answers.

Q&A 4. Why was October 2002 chosen as the Portal release date? 4. Why was October 2002 chosen as the Portal release date? Answer: October is one of the best windows of opportunity for not interfering with the academic year, with accounting or budget cycles or the legislative process. Answer: October is one of the best windows of opportunity for not interfering with the academic year, with accounting or budget cycles or the legislative process. 5. Will the portal be available 24X7? 5. Will the portal be available 24X7? Answer: Under evaluation -- The portal may be available but some of the linked applications will be dependent on whether those who support those services provide them 24X7.