Skip to main content
This year's e-Science All-Hands Meeting has had a really good buzz going on. The conference is the same size as last week's OGF/GridWorld meeting in Washington, in a friendlier venue and with lots going on. This year's talks & demos seem more about applications than technology, which suggests that e-Science is maturing and becoming viable for more widespread use.

I'm here mainly wearing my Grid Computing Now! hat. We have a booth in which we present the DTI-funded R&D projects alongside our industry case studies. We've had quite a good interest from the delegates. From my point of view it's been good to see what the R&D projects are doing now that they are up and running. We had excellent demos from BROADEN, DEWS and Healthcare@Home.

Healthcare@Home is developing a system whereby diabetes patients can monitor key indicators (such as glucose level in the blood) at home, with readings transmitted to a server via mobile phone. This enables clinicians to track their progress and risk analysis software to detect problems.

DEWS is linking weather forecast data with health data and coastguard services. One application is to give better assistance to search and rescure operations, allowing for the effect of wind and tide. Another is to forecast weather-related health problems. The key idea here is to make better use of available data - a theme I;ll return to in a later posting.

BROADEN is looking at the analysis of vibration data from aircraft engines in order to detect problems before they become critical. This is a development of the earlier DAME e-Science project. The same technology can be used for other types of data - there's another possible health link here as heartbeats are a possible application.

Far more happened than I can summarise in one blog entry. The hard thing has been finding time to follow up all the discussions I've had during the week - whenever I've sat down to make notes there's always been someone else interesting to talk to.

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…