Skip to main content

The Business Case and Methods for the Green Data Centre

"Green IT" is a hot topic at the moment. In the UK, data centres contribute nearly 2% of the country's CO2 emissions, a figure which is similar to that of the much-vilified airline sector. We recently broadcast a webinar on this subject which went very well - several people have said that it was our best webinar yet.

We were fortunate to have two excellent speakers. The first was Zahl Limbuwala of the BCS Specialist Group on Data Centres. This SG has developed an open source model for measuring server room efficiency, which will be published in January; Zahl presented the case for why energy efficiency is relevant and talked a little about this model.

The second speaker was Kate Craig-Wood, who runs a carbon-neutral hosting company. Kate gave a lot of low-level practical suggestions for improving the energy efficiency, which her company has used in their new data centre. There are obvious advantages in making such improvements, both economic and environmental.

The "Green IT" label covers many more issues, including the disposal of old equipment and power management within the office. Even when considering data centres, there are many avenues to approach, from building design, via power systems, to virtualisation software. We covered many of these topics.

The full title of the webinar was, "The Business Case and Methods for the Green Data Centre". You can see a Windows Media Player recording of the webinar here - just register and login to see it. A flash version will be provided in due course.

Comments

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 …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

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…