Skip to main content

Webinar: The business case for next generation IT architecture

Last week we recorded and broadcast another Grid Computing Now! webinar. This featured Steve Wallage of The 451 Group and Shahid Mohammed of Marsh talking about the business case for Grid. Steve presented a distillation of the 451 Group's findings from talking to Grid users across a wide range of sectors. Shahid then gave us the benefit of his experience applying Grid in an e-commerce business. Both are good presenters and I recommend their talks.

You can see the webinar at http://brighttalk.com/comm/gridcomputingnow/3b03d97eee-2473-632-2319. This uses Flash and so should be compatible with most browsers.

Viewers submitted a good range of questions. A couple of people asked about the type of businesses - small, medium or large; finance, pharma or other - that can benefit from Grid. Shahid's talk demonstrated that reasonably small firms in a general commercial sector can benefit. Another question focussed on security. Both Steve and Shahid explained that Grid can be deployed within the enterprise, which can greatly reduce concerns about security.

We didn't discuss the definition of Grid - there are people who would maintain that an infrastructure deployed entirely within one organisation "isn't really Grid". As always at Grid Computing Now!, we are less interested in what the technology should be called than in what it can do for UK businesses. It is clear from these talks that the combination of virtualisation, dynamic resource allocation and service-oriented deployment can achieve significant business gains - and that is what matters most.

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…