Skip to main content

Moving on....

I started a new job at the beginning of the month. I'm no longer working at the National e-Science Centre and that means that I won't be involved with Grid Computing Now!. I was granted a day from my new job to host the webinar on cloud computing with Ross Cooney, but that was my last commitment for GCN!.

It's been almost 6 years since I joined NeSC and it was about this time 4 years ago that we were writing the proposal for the Knowledge Transfer Network that became GCN!. Looking back, I the experience has taught me a lot as we evolved the KTN to be most effective. It took a lot of effort to get ourselves recognised - to "build the brand" in marketing speak - and I think the work paid off.

Now I have the chance to actually practice some of what I preached. My new position is Head of Development Services in the Information Systems Group of the University of Edinburgh, and one of our goals for the next year or so is to roll out a service-oriented architecture for the university. Other part of the ISG are deploying virtualised servers and my erstwhile colleagues at NeSC are working towards a campus grid. With good planning, we might even get these initiatives to work together.

I will post here when I have progress to report, but I will be blogging even less often than I have been until now. In the meantime, I wish everyone involved with Grid Computing Now! all the best for the future.


Ross Cooney said…
Hi Dave,

It was great to work with you over the past few months. Enjoy the new job, Talk soon,

Ross Cooney

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…