1. 1 Portals – an institutional imperative Paisleys portal production process Tony Shaw, Anne Strachan Network and Information Systems Management University of Paisley

2. 2 Portals – an institutional imperative History/plan 199 6 199 8 200 0 200 1 200 2 (se pt) emphasis on intranet Staff Intranet Co-ordinator post created Portal strategy document published (continued to be revised/published) Portal purchased/prototyped produced VC directly involved/briefed period of deployment and limited development replaces existing intranet site

3. 3 Portals – an institutional imperative Staff intranet

4. 4 Portals – an institutional imperative Preparatory activities u Tracking commercial sector products, prices and projects u Anticipating some possible problems hype surrounding VLE/MLE faculty developments significant organisational changes taking place

5. 5 Portals – an institutional imperative Lessons from elsewhere u focus on business benefits u importance of executive sponsorship u invest in planning u invest in education/awareness u focus on process not technology u take care with integration and expectations

6. 6 Portals – an institutional imperative The portal strategy u separate services for staff and students u common technology for above u remote access as part of model u gateway concept not ambitious integration u sub projects to drive initial content and ownership

7. 7 Portals – an institutional imperative Some tactics employed u involvement of VC confirms strategic nature of project, gets into plans u content contributor clarity continued u partner with others e.g. faculty web site connector u broaden ownership e.g. manager channel u restrict involvement

8. 8 Portals – an institutional imperative objectives u portal as framework for information architecture u emphasis as strategic project for the institution u provide flexible approach able to accommodate other developments

9. 9 Portals – an institutional imperative some technical issues u ensuring a consistent technical framework u anticipating integration requirements u design relates to organisational structure u incorporating information strategy and planning issues

10. 10 Portals – an institutional imperative some people issues u anticipating risks/reasons for failure u establishing appropriate management and project structures u complexity of overall project u how to raise awareness in context of business

11. 11 Portals – an institutional imperative practical aims u emphasis on business benefits from outset u making appropriate and cost effective use of what exists/will exist u caution and pragmatism on integration

12. 12 Portals – an institutional imperative practical steps u ensuring group membership reflects business requirements u early communication of portal strategy u rapid production of prototype to aid process u reference to other sources/experience u careful initial involvement at various levels u VC involvement

13. 13 Portals – an institutional imperative initial focus u you as a member of the University community (Corporate Comms) u you as an employee of the University (HR) u access to key information services/resources u you as a member of a faculty/dept/etc

14. 14 Portals – an institutional imperative Portal

15. 15 Portals – an institutional imperative initial components and channels basics - sign-on, email, University calendar, phone directory, bookmarks University news and information employee news and information information resources faculty/local management communication user defined bookmarks research funding news

16. 16 Portals – an institutional imperative gateway to resources

17. 17 Portals – an institutional imperative faculty site integration

18. 18 Portals – an institutional imperative ownership for managers