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

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation. Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers). It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs. I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh. Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

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...

Distributed Thinking

Search This Blog