Skip to main content

UCAS - The Cloud Journey

The first session this morning was from James Munson and Andy Gillett from UCAS. James described UCAS’s migration from a locally-hosted service in 2012 to a cloud-based service in 2014.  On results day, UCAS gets 235 logins/second.  They had unhappy experiences in 2011 & 2012 and so needed to change.  UCAS needed scalability, security and control of costs, so they chose a public cloud supplier rather than a private cloud.  Their "Track" application was written in .Net so was a natural fit for Microsoft Azure.  Amazon provided the best service for databases.  UCAS already used Rackspace for their web presence, so they went with a mixed set of suppliers.  If they had had more time, they might have preferred a single supplier.

Their architecture handles DDOS suppression, load balancing, monitoring et al. It is built for horizontal scalability with stateless applications etc.  They use Puppet for automatically managing environments.  The UCAS technology team now has sub-teams for customer engagement, IT strategy and architecture, solution delivery, and service assurance.


Andy Gillett described the UCAS's IT engagement strategy.  He outlined the need to apply ITIL service management to UCAS services.  They have established a technical forum, 1:1 meetings, use of social media, user groups, relationships with student system vendors, and relationships with UCISA, HESA and ITSMF.

James noted that putting software into the cloud isn’t a panacea.  You may still have old wine in new bottles – code that needs to be refactored or replaced.  But the gains in flexibility and cost control is worthwhile.


Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…