Skip to main content

Workshop on Research Opportunities

This week will see the annual conference for UK e-Science, which for historical reasons is called the e-Science All-Hands Meeting. I have organised a knowledge transfer workshop for the Tuesday afternoon, with the aims of presenting research opportunities for e-Science in the UK commercial and public sectors. We have four excellent speakers lined up.

Mark Ferrar is the Director of Infrastructure Architecture for NHS Connecting for Health in England. Mark is interested in opportunities for using the processing power available to the NHS to improve clinical outcomes, for example by running HPC models and diagnosis applications.

Liam Newcombe is tackling the question of "Green IT" in data centres. This is a big topic in the industry, because energy prices are rising and carbon accounting is being deployed. Liam has developed an open-source integrated model of data centres for the BCS and the Carbon Trust. He is looking for collaborators to further improve this model.

Alexander Efimov will give us a presentation about the exploitation of e-science technologies. Alex is from the CERN and ESA UK Technology Transfer Office. He is working with Constellation Technologies to build a business around the provision of services using the open-source gLite software.

Finally, Chris Greenwell of Durham University will present a new collaborative R&D project. The NIMES project is using e-science to directly improve the performance and reduce the environmental damage of the oil drilling industry, via a combination of computational modelling, visualisation and computation steering. This shows the opportunities that arise from the continuing improvement of e-science technologies.

The workshop will conclude with a panel discussion. Full details can be found here.

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…