Skip to main content

Reboot: three years on

I've decided to revive this blog, after a three-year hiatus, to post news and thoughts about my current role as Head of Development Services, in the IS Applications Division, at the University of Edinburgh.  My aim is to give some visibility to what goes on "behind the scenes" (or should that be "behind the screens"?) and to reveal the sort of issues that face IT in a Russell Group university.

My current job is quite different from my previous role at the National e-Science Centre, which was the topic of the previous incarnation of this blog.  Some issues, such as virtualisation and cloud, are common to all IT jobs these days, but the emphasis of my current job is on support and administration systems rather than research.  One important difference is that I must stress that all the posts here will not represent the official position of the University of Edinburgh in any way.

To start off, let me point you at an interesting comparison of the "student experience" at three European universities.  This posting doesn't mention IT at all - which is a little humbling.  On the other hand, perhaps this is how it should be.  People come to university to learn, not to use the IT.  People tend to notice IT most when something goes wrong, so no news can be good news.   Thanks for Guillermo Rein for noting this via LinkedIn.
http://nickybartlett.blogspot.com/2012/01/per-usual-i-must-give-recap-of-my.html .

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…