Skip to main content

A holistic use of thin clients

Yesterday saw a workshop on Sustainable IT at the new Queen Margaret University campus in Musselburgh. The workshop was ostensibly about "new ways of working" but another major focus was on how the adoption of thin clients allowed the architects to design an more environmentally friendly campus. Thin clients use less power on the desktop than PCs, which means less heat is generated in the classrooms, labs and open working areas. For QMU, this meant that the building can use natural cooling and ventilation, saving considerably more energy in addition to the saving from the terminals themselves.

The switch to thin clients was also used to introduce the use of virtual desktops. These let staff and students access their work from anywhere on the campus and from home. Staff are encouraged to work from home when it suits them. On campus, staff now work in open plan areas rather than offices; overall, the extra freedom seems to outweigh any disadvantage from the change.

The energy saving aspect of the QMU deployment contrasts with the experience of Merrill Lynch, who found that the servers and associated equipment used at least as much extra energy as was saved on the desktop. QMU's holistic approach means that the reduction on the desktop is leveraged to gain further savings overall. This is a very sensible and productive use of thin clients.

This workshop was led by the SusteIT project, which is running a series of such workshops. I have been helping them by finding speakers and providing material on data centres, grid and virtualisation. Back in June, we ran a workshop on data centre cooling and power supplies, and this is one area where QMU could improve. Their server room is fairly small by industry standards but even so they could almost certainly cut their power bills further by adopting the latest technology. It seems the quest for energy efficiency can always find further improvements.

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…

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…