Skip to main content

BBC Horizon programme on FireGrid

Next Tuesday, April 24th, the BBC will be showing an episode of Horizon all about the FireGrid project. The vision behind FireGrid is that we can use the grid and HPC computing to model the spread of fire in buildings, to improve building design, firefighters' training and actual response in emergencies.

This is one of a number of grid projects looking at the use of real-time modelling to improve emergency response. Others are focussing on floods, earthquakes or the release of noxious substances into the atmosphere. In each case, the idea is to use lots of sensors to provide input to complex HPC models, which in turn provide forecasts to an emergency response control room.

There are many technical issues that need to be solved before such systems can be deployed live. We don't yet know the best way to guide simulations as new sensor input becomes available. We need better ways of allocating priority jobs to grid resources - it's clear that a traditional queue system won't give the response we need. The models themselves need to be adapted to work in this new computational environment. And of course there are security issues to consider. But this is interesting research with great potential benefit.

You can find more details about the BBC programme at http://www.bbc.co.uk/sn/tvradio/programmes/horizon/broadband/tx/firegrid/.

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…