Download
1 / 18
180 likes | 193 Views
This paper explores the development and implementation of a staff portal at the University of Paisley. It discusses the portal's strategy, tactics employed, technical and people-related issues, as well as practical steps taken. The portal aims to provide a common platform for staff communication, access to key information, and integration of faculty sites.
E N D
Paisley’s portal production process Tony Shaw, Anne Strachan Network and Information Systems Management University of Paisley
1996 1998 2000 2001 2002 2002 (sept) 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 History/plan
Preparatory activities • Tracking commercial sector products, prices and projects • Anticipating some possible problems • hype surrounding VLE/MLE • faculty developments • significant organisational changes taking place
Lessons from elsewhere • focus on business benefits • importance of executive sponsorship • invest in planning • invest in education/awareness • focus on process not technology • take care with integration and expectations
The portal strategy • separate services for staff and students • common technology for above • remote access as part of model • gateway concept not ambitious integration • sub projects to drive initial content and ownership
Some tactics employed • involvement of VC • confirms strategic nature of project, gets into plans • content contributor clarity continued • partner with others • e.g. faculty web site connector • broaden ‘ownership’ • e.g. manager channel • restrict involvement
objectives • portal as framework for information architecture • emphasis as strategic project for the institution • provide flexible approach able to accommodate other developments
some technical issues • ensuring a consistent technical framework • anticipating integration requirements • design relates to organisational structure • incorporating information strategy and planning issues
some people issues • anticipating risks/reasons for failure • establishing appropriate management and project structures • complexity of overall project • how to raise awareness in context of business
practical aims • emphasis on business benefits from outset • making appropriate and cost effective use of what exists/will exist • caution and pragmatism on integration
practical steps • ensuring ‘group’ membership reflects business requirements • early communication of portal strategy • rapid production of prototype to aid process • reference to other sources/experience • careful initial involvement at various levels • VC involvement
initial focus • you as a member of the University community (Corporate Comms) • you as an employee of the University (HR) • access to key information services/resources • you as a member of a faculty/dept/etc
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
