Skip to main content

e-Science and Industry

AHM2007 saw several examples of the industrial exploitation of e-Science technologies. I organised a session on this theme for Grid Computing Now! (GCN), which was attended by some 300 people. Jim Austin and Yike Guo gave talks about their contrasting approaches to commercialising their research.

Jim has built his company, Cybula, from income, opting for the advantage of control and accepting slower growth. Yike has chosen an investment-based approach for Inforsense, achieving the fast growth required by his funders. Both explained how they found markets for their technologies. They also reflected on how to maintain both academic and commercial careers, using each to benefit the other while balancing their sometimes contrasting demands.

I followed with a short talk that gave a high-level outline of the state of advanced IT infrastructure in industry, drawing on some of the presentations given our Grids Mean Business track at OGF20. Of course, IT infrastructure is only one aspect of e-Science; there are also application-level advances that are suitable for take-up by industry.

Later in the week, Thomas Hartkens of Ixico presented their experience of exploiting e-Science infrastructure. Derek Hill had given an excellent contribution to a GCN webinar about their business case earlier back in March. In contrast, Thomas focussed more on the management details, particularly the quality management required to meet regulatory approval in medical informatics. This level of project management is new to many academics, so this talk was very informative for anyone considering taking the plunge into the commercial world.

AHM2007 also had many demonstrations of e-science projects that involve industrial partners. On our stand, which was one out of many, we hosted demos from 6 of the collaborative R&D projects on inter-enterprise computing funded by the Technology Strategy Board.

In summary, there are many good links between parts of the e-Science community and some companies. One of our tasks at GCN is to encourage more of these successes.

Comments

Popular posts from this blog

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-depth discussions abo

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 iterat