SAVES first academic year ends with students saving 1.5 million kWh of electricity

No ratings yet. Log in to rate.

The first year of the SAVES project has come to an end and with it the Student Switch Off campaigns for the academic year 2014/2015. The SAVES project encourages 25,000 students living in dormitories in five partner countries (UK, Sweden, Greece, Cyprus and Lithuania) to save energy by means of simple everyday actions. The students participate in energy saving competitions throughout the academic year and win prizes. This year 17% of all students signed up to the campaign (over 4,000 students), with hundreds submitting photos to our competitions, and thousands taking part in our climate quizzes.


So how much electricity was saved over the 2014-15 academic year at all the participating dormitories? Overall the students saved an impressive 1.5 million kWh of electricity and over 600 tCO2, which equates to an average of 4,44% savings. Congratulations to all the students that made this happen! The result was calculated by comparing the electricity usage at each dormitory in 2014-15 to the electricity usage prior to the Student Switch Off campaign starting. The dormitory at each of the 17 participating universities that saved the most energy was rewarded with a celebration.   

At the national level, the following dormitories have saved the most energy and therefore have been crowned national winners: 

United Kingdom Teme (University of Worcester)

Cyprus Building 8 (University of Cyprus)

Greece Building D (University of Athens) 

Lithuania Dorm no.3  (Gulbiu g.8) (Klaipeda State College)

Sweden Olofshöjd 22 (Gothenburg)

The overall SAVES winner for 2014-15 that saved the most energy throughout the five countries is Teme student dormitory from the University of Worcester, United Kingdom.  Katy Boom, Director of Sustainability at University of Worcester, commented ‘This is fantastic news for our students living in Teme Hall, we are very proud of their achievement.  Through their efforts of small changes in behaviours such as not over filling the kettle each time they made a hot drink, and cooking with the lids on saucepans they have saved the most energy.  This is not just in the UK, but across our partners in Europe.  We are all thrilled.  The Students’ Union and University do work together on a many behaviour change campaigns and this result really does help everyone see their efforts and enthusiasm have been worthwhile.  A fantastic result.’


Joanna Romanowicz, Project Manager of the SAVES project said: ‘It’s so exciting to see the project successfully adapted in all our participating countries. Students across Europe have been taking lots of initiative, getting their friends involved and learning more about energy saving actions. For next year we want to build up on this, and continue to make our students feel part of a Europe-wide international Student Switch Off community. Well done to all our students, and in particular students living in Teme dormitory, for all their efforts!’.


For more SAVES news, please visit the project website or one of the many Student Switch Off Facebook pages.



Rboutlet1 Rboutlet1
03:24 on 17 Mar 16 <a href=""><b>Oakley Sunglasses</b></a> <a href=""><b>Oakley Outlet</b></a> <a href=""><b>Toms Outlet</b></a> <a href=""><b>Yeezy Boost 350</b></a> <a href=""><b>Kate Spade Outlet</b></a> <a href=""><b>Nike Air Max 2015</b></a> <a href=""><b>Longchamp Outlet</b></a> <a href=""><b>Kate Spade Outlet</b></a> <a href=""><b>Nike Outlet Store</b></a> <a href=""><b>Yeezy Boost 350</b></a> <a href=""><b>Ralph Lauren Outlet</b></a> <a href=""><b>Adidas Outlet</b></a> <a href=""><b>NFL Jerseys Wholesale</b></a> <a href=""><b>Ray-Ban Sunglasses</b></a> <a href=""><b>Nike Air Max 2016</b></a> <a href=""><b>Nike Flyknit</b></a> <a href=""><b>Longchamp Outlet</b></a> <a href=""><b>Ray Ban Sunglasses Outlet</b></a> <a href=""><b>Nike Outlet Factory </b></a> <a href=""><b>Burberry Outlet</b></a> <a href=""><b>Yeezy Boost 350</b></a>
Wq123 Wq123
02:58 on 26 Oct 15 In short, the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. To start explaining the microservice style it's useful to compare it to the monolithic style: a monolithic application built as a single unit. Enterprise Applications are often built in three main parts: a client-side user interface (consisting of HTML pages and javascript running in a browser on the user's machine) a database (consisting of many tables inserted into a common, and usually relational, database management system), and a server-side application. The server-side application will handle HTTP requests, execute domain logic, retrieve and update data from the database, and select and populate HTML views to be sent to the browser. This server-side application is a monolith - a single logical executable[2]. Any changes to the system involve building and deploying a new version of the server-side application. Such a monolithic server is a natural way to approach building such a system. All your logic for handling a request runs in a single process, allowing you to use the basic features of your language to divide up the application into classes, functions, and namespaces. With some care, you can run and test the application on a developer's laptop, and use a deployment pipeline to ensure that changes are properly tested and deployed into production. You can horizontally scale the monolith by running many instances behind a load-balancer. Monolithic applications can be successful, but increasingly people are feeling frustrations with them - especially as more applications are being deployed to the cloud . Change cycles are tied together - a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed. Over time it's often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resource.
Please log in to comment.