UF Web Portal

1
UF Web Portal

• Mike Conlon
• Director of Data Infrastructure

2
Strategic Objectives

• Provide a single point of entry for internal
  communications at UF regardless of role
  student, faculty, staff
• Provide single sign-on for enterprise
  applications
• Provide early visible service from UF Bridges

3
Methods

• Use PeopleSoft Enterprise Portal 8.4
• Leverage the UF Directory
• Leverage GatorLink
• Engage existing content providers
• Engage existing training resources

4
Team Members

• Dave Gruber, Project Manager
• Jadhu Nadarajah, Portal Admin
• Diane Craig, Communications and Training
• Warren Curry, Integration
• Allen Rout, Integration
• Lee Stevens, Integration
• Scooter Willis, IT
• Christine Schoaff, Processes and Standards
• Mark Trammell, UF Web Admin
• Al Kirby, UF Web Admin
• Mike Conlon, IT

5
Communications AUC

• Weekly Meetings
• Three workgroups
• Usability
• Communications
• User Support Docs, Training, Help Desk

6
Portal Graphic Design

• Brand it as my.UFL
• Keep it simple
• Reduce support requirements by design
• Use muted colors to support extended use

7
my.UFL

• Screen shot

8
(No Transcript)
9
Links
PageTabs
Edit
Pagelet
Navigation
News
10
Access

• Portal will provide pass-through access to
• Admin Menu
• GatorLink Account Services
• ISIS (post roll-out)

11
(No Transcript)
12
(No Transcript)
13
Content

• Create an organization of information that is
  natural for the reader
• Distribute content production
• Role-based tabs
• Require just one pagelet for each role
• Reader has control of all other content and layout

14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
Roll-out Tactics

• Execute quiet launch
• Assist with sign-on changes
• Train the trainers
• Administer in-house to start
• Nurture content providers
• Prepare the support community
• Plan for future services

18
User Support

• Provide on-line help
• Provide Users Guide
• Provide Authors Guide
• Provide training for content providers
• Let units train users as needed
• Develop Help Desk support and processes

19
IT Activity

• Create team
• Create system infrastructure
• Create network infrastructure
• Create data infrastructure (instances)
• Create development environment
• Create sandbox, alpha, beta, production
  environments

20
Timeline Nov 02 Mar 03

• Nov Portal Sandbox
• Dec Assemble AIX environments
• Jan Certified Install and patches
• Feb Portal instances and structure
• Mar 5 Portal Beta go-live
• Mar 31 Portal Production go-live

21
Project Status

• Alpha test ended Mar 4
• Beta test began Mar 5 AUC members and team
  members
• DDD memo week of Mar 3
• Concluding work on Admin Menu, GatorLink service
  tie-ins
• Load testing week of Mar 17
• Go-live on-schedule for Mar 31

22
Documents

• UF Web Portal Statement of Direction
• Web Portals in Higher Education
• my.UFL Users Guide
• my.UFL Site Structure
• Project Status reports
• Project web site www.bridges.ufl.edu/portal

23
(No Transcript)