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

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…