Skip to main content

A Research Strategy for the Century of Information

"This is the Century of Information" - G. Brown, November 2007.

This week, I attended a think-a-thon about a strategy document that the e-Science community in the UK is developing. The goal is to put in place the right mechanisms for ensuring that UK research can make the most of new computing technologies and methods. We have many success stories from the e-science programme; the question is, how do we build on those successes and make the techniques available to everyone?

One point that arose from the workshop is that we need different types of successes. Most of the examples put forward were of good research enabled in a range of domains (GeoSciences, BioScience, Chemistry, Physics, Social Science, etc.). We also found examples of advances in Computer Science itself, rather than just using CS to support other fields; this is essential if we are to engage CS academics.

Beyond academia, we need examples of knowledge transfer to industry. This is where the Grid Computing Now! KTN can help and I will be working on this strategy document in the next couple of weeks to flesh out this story. We also need to engage the public and the schools, so that students coming into university or industry know about the existence of our techniques.

When we looked at the barriers between us and this vision, we were perhaps less imaginative; the usual social and technical issues were listed. I would have liked to seen more about technology transfer in both directions between academia and industry; if nothing else, the academics should be interested in this because it will ensure support for their research from the politicians and funding agencies.

We also had an interesting discussion about Green IT. Although some of us felt very strongly about the need to tackle the problem (Greenhouse gas emissions from university IT is doubling every four years), it became apparent that this won't be seen as a barrier until it impinges on day-to-day behaviour. The research funding structure means that researchers often don't see the full cost of the facilities they use, because they are funded centrally. It's not clear whether it would be practical to change that structure. Perhaps when politicians come under pressure to cut CO2 emissions, perhaps academic computing will seem an easy target, which would make the researchers take notice. Until then, energy efficiency seems more relevant to the infrastructure providers rather than the end users.

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…