Skip to main content

AHM 2008

I was pleased by our workshop on research opportunities this week. Our speakers met several people who were interested in their work and might contribute to taking it further. It's hard to measure the outcomes of these events, because the collaborations that we are aiming to catalyse may take months to firm up and then may take much longer to produce actual results, but the first impressions are positive.

Some of the networking happened outside the workshop itself, of course. That is the advantage of face-to-face meetings; sometimes all you need is to bring the right people together for the first few minutes. Also, you can follow serendipitous links, such as when a colleague pointed me at the workshop on declarative data centres that Microsoft Research Cambridge and HP Labs organised earlier this year. I think the UK is building a critical mass in data centre management and I hope this can be encouraged to the point where it becomes a viable industry.

Beyond our workshop, there was plenty of interest in the wider AHM conference. I chaired one "regular" session in which most of the papers were about the use of social networking tools and similar systems for supporting science teams and similar projects. There is a lot of potential here and several people are taking advantage of it.

One limitation of this year's event was simply the large number of parallel sessions, which meant that individual sessions were quite small and that you couldn't follow even half of what was going on. But I think this was offset by he bringing together of several different communities, which should bear fruit in later years.

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…