1. A Campus Portal It’s more than the technology… Presented by: Rick Bunt, Associate Vice President, Information & Communications Technology Sharon Scott, Manager of Communications, Student & Enrolment Services University of Saskatchewan Saskatoon, Saskatchewan

2. Evaluation Code 376 2 Acting boldly and seizing their chance With no promise of funds in advance A team of mere mortals Unacquainted with portals Put one in by the seats of their pants.

3. Evaluation Code 376 3 PAWS Background A Bold Approach Challenges Faced A Look at PAWS Lessons Learned Outline Personalized Access to Web Services

4. Evaluation Code 376 4 Background

5. Evaluation Code 376 5 The University of Saskatchewan  Located in Saskatoon  A “medical-doctoral” University  20,000 students  7,500 faculty and staff  14 colleges and schools with a full range of programs Background

6. Evaluation Code 376 6 Our Timeline 2001-02SIS replacement – needs & options investigation May 2002BOG approves Si! Project; selection process begins Nov 2002RFP issued May 2003SSCT Banner selected June 2003Contract signed; project planning begins Sept 2003PAWS launched quietly Mar 2004PAWS launched loudly April 2005Student goes live May 2005 Finance goes live Background

7. Evaluation Code 376 7 Some Characteristics of Portal Technology  Consolidation: multiple services via single sign on (SSO)  Channels: to deliver content and services  Community: service delivery to specific groups based on institutional role  Customization: user-tailorable, in both content and form  Content management: tools for managing/distributing content Background

8. Evaluation Code 376 8 The Case for a Portal  What we had in June 2003  Institutional readiness  Existing work  Lists of desired services to deliver  What we didn’t have  A process to implement  Support (read: budget)  uPortal chosen as way to break in  Then, along came Luminis… Background

9. Evaluation Code 376 9 The Luminis Decision  Serendipity  Luminis came as part of Si! project purchase  Not our first choice, but a good one  Leveraged existing uPortal work  Provided a vendor partner  Project credibility Background

10. Evaluation Code 376 10 A Bold Approach

11. Evaluation Code 376 11 Project Strategy  First tangible deliverable of our Si! project  We required a bold approach  Tight scope, focus on quick wins  Nimble governance—Just-in-time project mgmt  Evolutionary budgeting  Staged rollout A Bold Approach

12. Evaluation Code 376 12 Project Timeline June 03Sep 03Mar 04Sept 04 Adjustments Train Users Faculty Pilot Implement Tech training Plan Banner Prep 3.2 Upgrade 3.2 Beta 3.1 Upgrade New Server Sign Contract Loud Launch Soft Launch Email TaxForms Grades Files Calendar Courses Fees Groups A Bold Approach Exam Schedules

13. Evaluation Code 376 13 Functionality & Services  Just-in-time delivery: leverage existing work  Out-of-the-box functionality  E-mail, Calendar  Courses, Groups  Announcements  Grab the low-hanging fruit  RSS, XML, WebProxy, CPIP  Throw-away applications A Bold Approach

14. Evaluation Code 376 14 Sound like a lot of technology? There’s much more…  What will it look like?  What will we call it?  Content decisions  Branding decisions  Training  Communications guidelines  Engaging campus stakeholders  Managing roles, users, permissions A Bold Approach

15. Evaluation Code 376 15 Challenges Faced

16. Evaluation Code 376 16 Things don’t always go as planned Three days before the launch … Challenges Faced

17. Evaluation Code 376 17 Technical & Organizational Challenges  Existing issues exposed  Enterprise-wide coordination  Examples:  Authentication  E-mail  Instructor Data  Eligibility  Responsibilities  Staffing Challenges Faced

18. Evaluation Code 376 18 A quick look at our portal… PAWS

19. Evaluation Code 376 19 A Look at PAWS

20. Evaluation Code 376 20 A Look at PAWS

21. Evaluation Code 376 21 A Look at PAWS

22. Evaluation Code 376 22 Lessons Learned

23. Evaluation Code 376 23 In Retrospect  Test vs. production environment  Everything on one server (scaling)  SSO to Banner  E-mail not the carrot we thought  Open-source vs vendor  Changing processes takes time (and patience) Lessons Learned

24. Evaluation Code 376 24 In Retrospect  Our bold approach has paid off  Clear vision, build the plan as required  Leverage existing work  Staged rollout, to everyone  Collaboration is key  Portal enhances content, communications Lessons Learned

25. Evaluation Code 376 25 Next Steps…  Banner integration (Student and Finance)  WebCT integration  Integration – legacy middleware and role of LDIS  Enhancements to Luminis  More services  integration with legacy systems (eg. PS HR)  New channel development

26. Evaluation Code 376 26 Summary

27. Evaluation Code 376 27 With PAWS, we are…  Responding to user expectations  Communicating effectively  Facilitating faculty adoption of technology  Reducing e-mail clutter  Leveraging existing brand awareness  Enhancing U of S reputation Summary

28. Evaluation Code 376 28  Providing a common platform for service delivery  Building communities  Preparing the campus for on-line service delivery  Continuing to work with SSCT in feature development  Proving value through usage – the system sells itself Summary With PAWS, we are…

29. Evaluation Code 376 29 Usage Continues to Grow… Sept 03 Sept 04 Loud launch Tuition payments Mar 04 “out of box” functionality 19,000 users new “business” applications And the work continues… Banner Integration Christmas break Spring break End of term Christmas break Classes resume Mar 05 IDs distributed to newly admitted students Soft launch

30. Evaluation Code 376 30  Pay attention to governance  Take advantage of quick wins  Take opportunities to collaborate  Emphasize content and communications  Be ready  If you build it, they will come! Summary Famous last words…

31. Evaluation Code 376 31 Questions? rick.bunt@usask.ca sharon.scott@usask.ca Contact us: