Wednesday, 17 April 2013

Replacing MUSE, but not necessarily with a portal...

The Replacement MUSE project is significantly not called the new portal project. This is because although we are replacing MUSE with something or somethings that provide the same functionality as MUSE we did not want to restrict ourselves into saying the replacement had to be a portal. 

Instead the project board looked at the functionality that MUSE provided and considered how best to deliver and improve on that functionality with new technologies. For next month's email newsletter we will provide more information about replacement MUSE including what it might look like and service launch timescales. For now we can share the following vision for replacement MUSE:

The vision for the future replacement MUSE is;

  • To provide a personalised point of access for IT services, with only those services specific and accessible to the individual being displayed.
  • To provide secure access ideally using single sign on, but not to become a barrier through requiring users to provide their credentials too often.
  • To provide a communication channel for targeted messages and a University wide channel for incident communications.
  • To offer dynamic content targeted to distinct groups including applicants, enquirers, alumni, associates, staff, students etc. 
  • To structure information around function rather than organisational hierarchy. 
  • To offer dynamic content to staff and students on key information (timetable, PC availability etc)
  • To allow controlled access to test and beta services for individuals and groups of staff

User experience
  • To provide a consistent experience as users access IT services on multiple devices.
  • To deliver a simple and modern user interface available on desktops, portable and mobile devices.
  • To be easy and obvious to find and sign in.
  • To be so intuitive that no user training is required to use it
  • To be fast and not to add drag to user experience in accessing services

  • To be resilient and reliable as the point of entry for critical IT services (alternate entry points may also be required).
  • To be available 24/7 (need to put some thought into availability but also amount of planned maintenance etc)
  • To be capable of providing services at peaks of demand