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.


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

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…