Skip to main content

Greening the desktop

I attended an interesting workshop this week. It was one of the series that Peter James has put together for his SusteIT project; this one focussed on desktop PCs. The talks and panels looked at measurement procurement of energy use, procurement options, desktop grids, power management and thin clients. In any sizeable organistion, Desktop PCs use a large amount of electricity and there are many options available for reducing this consumption - and saving money too. This is the second time that I've seen a British university do the sums and expect to save £250,000 a year.

The panel on power management tools was interesting. These seem to be coming of age at last. Operating systems have had support for managing individual computers but a large organisation needs a system for managing thousands of PCs, with different policies for different groups, and of course the important facility to wake up in time for the distribution of updates.

James Osborne gave an interesting analysis of the FLOPS/Watt providing by Cardiff University's Condor pool, as compared to their old cluster (inefficient) and the one they installed last year using modern cooling systems. The new cluster is much more efficient, so it seems that if you have the funds to install modern dedicated technology for high-throughput computing, that may be the way to go. Of course, if you don't have that sort of money, a desktop grid will make good use of your existing infrastructure.

Unless, of course, you go for the thin client option. As Queen Margaret University have shown, a thin client approach can dovetail very neatly with energy-efficient buildings. Conversely, Merrill Lynch found that they used more energy in the server room than they saved on the desktop. The moral, I believe, is that you have to measure carefully the gains and losses for your particular installation. Case studies from elsewhere can give hints about what to look for and approaches to consider, but they are no substitute for performing your own analysis.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…