## Sustainability
- [ ] **Career Essentials in Sustainable Tech by Microsoft and LinkedIn.** About 3.5 hours. A good overall introduction to the topic of sustainability. Covers areas such as Net Zero, carbon accounting, the circular economy, LCAs, procurement as well as some light-touch information on why digital services must also transition to being sustainable. The digital part of the course makes some fairly exaggerated claims that should be questioned or challenged.
https://www.linkedin.com/learning/paths/career-essentials-in-sustainable-tech-by-microsoft-and-linkedin

## Online training courses
- [ ] **Sustainable software engineering overview**
https://learn.microsoft.com/en-us/training/modules/sustainable-software-engineering-overview/
Great into video series by Asim Hussain (GSF). Very digestible, only takes about 30 minutes to complete.

- [ ] **Green Software Practitioner**
https://learn.greensoftware.foundation/
Slightly more in-depth online course. Takes 2-3 hours to complete. Recommended.

- [ ] **Sustainable Software Engineering**
https://open.hpi.de/courses/sustainablesoftware2022
Fairly in-depth course with some Python coding examples. Takes 6-8 hours to complete, but the videos are blocked by DWP security (they are on Vimeo). Note that the graded coding exercises are not available in self-paced mode. The pace can be a little slow at times, but there are some very good arguments and examples made. Part 1 is focussed on the problem of digital emissions and higher-level thinking, while Part 2 is more focussed on technical approaches. Part 1 is strongly recommended for all, while Part 2 is a little weaker.

## Books
- [ ] **Building Green Software**.
https://learning.oreilly.com/library/view/building-green-software/9781098150617/
Good and very broad introduction to Green Software. Aimed more at those new to Green Software, it covers all the main topics. Would have been strengthened by more practical examples or how-to advice.

- [ ] **Decarbonise Digital: Facts. Methods. Action.**
https://www.amazon.co.uk/dp/B0CNQNNQL2/
Probably the most complete book on the topic to date. Lots of detailed examples for engineers and designers.

- [ ] **How can engineers make IT more sustainable?**
https://www.scaleway.com/en/blog/how-can-engineers-make-it-more-sustainable-part-1/
Free whitepaper (44 pages). Good and easy-to-read summary of the issues and some approaches to addressing them.

## Podcasts
- [ ] **Green io**. Recommended. https://greenio.gaelduez.com/
- [ ] **Environment variables**. Podcast by the Green Software Foundation. Recommended. https://podcast.greensoftware.foundation/
- [ ] https://www.youtube.com/watch?v=0CX9J3oAipM

## Websites to explore
https://greensoftware.foundation/

National Grid

Electricity Maps

https://dataviz.boavizta.org/manufacturerdata

## Articles to read

https://www.wired.com/story/amazon-google-microsoft-green-clouds-and-hyperscale-data-centers/

https://www.nature.com/articles/s42256-020-0219-9 (AI)

https://www.bbc.com/future/article/20161017-your-old-phone-is-full-of-precious-metals

https://www.swctn.org.uk/2021/03/23/data-is-the-new-plastic-part-1/

https://www.economist.com/graphic-detail/2022/07/22/do-men-and-women-think-about-climate-change-differently

## Groups to join

- [ ] https://www.civilserviceenvironmentnetwork.org/
- [ ] DWP Slack
- [ ] X-Gov Slack

## Website reporting extensions

- [ ] **Beacon** (https://digitalbeacon.co/). Developer tool to evaluate the environmental impact of a web page.
- [ ] **Globemallow** (https://globemallow.io/#home). Grades a web page on its environmental impact.

## Further guidance

* **The Technology Code of Practice**. Point 12 outlines the GOV.UK position on sustainability in ICT. See https://www.gov.uk/guidance/make-your-technology-sustainable
* **W3C Web Sustainability Guidelines, 1.0.** A brand new initiative, covers business, design and technology aspects of digital services. See https://w3c.github.io/sustyweb/. Condensed version: https://w3c.github.io/sustyweb/glance.html and quick reference: https://w3c.github.io/sustyweb/quickref.html
* **Green Software Maturity Matrix**. A new initiative by the Green Software Foundation. A self-evaluation tool to help organisations and teams understand their level of maturity in this area. See https://github.com/Green-Software-Foundation/green-software-maturity-matrix and https://docs.google.com/document/d/1wa2lliXQeH6HE1JHqwjTFuVndRUXzxGlbYXRtTQxF5o/edit
* * **Green Software Maturity Matrix**. A new initiative by the Green Software Foundation. A self-evaluation tool to help organisations and teams understand their level of maturity in this area. See https://maturity-matrix.greensoftware.foundation/

## Glossary

**Carbon forecasting and timeshifting**: in countries such as the UK with a distinctly mixed energy grid, the emissions generated by using electricity can vary dramatically throughout the day or week, based on environmental and market conditions. A bright and windy day will typically mean that emissions can be very low, while a dull and windless day will mean that the same kWh produce far higher amounts of CO2. Carbon forecasting uses the predicted weather to look for ‘green windows’ of time. The https://github.com/bbc/carbon-minimiser is a good way to get started with this in the UK, and the Green Software Foundation has also produced the https://github.com/Green-Software-Foundation/carbon-aware-sdk which works at country level.

**Carbon intensity**: the carbon cost or producing electricity, based on the local energy mix. In the UK, this is typically a mixture of gas, nuclear, wind and solar. In western Europe, countries with high intensities (over 400g per kWh) include Poland, Czechia and Germany, all of which rely on coal for much of all of their power generation. Countries with very low carbon intensity include Iceland, Norway and Sweden, which use energy sources such as hydro, geothermal or nuclear. See https://app.electricitymaps.com/map for an interactive map/tool for a global view and https://www.carbonintensity.org.uk/ for a UK regional view. Both services have very useful APIs to support activities such as demand shifting.

**Demand shifting**: in Green Software development and GreenOps, there is the opportunity to locate servers or activities in regions where the carbon intensity is lower. This could mean moving some or all of your activity in a country or region with a cleaner grid, such as Sweden or Scotland. It could also mean using carbon forecasting (for example using https://github.com/bbc/carbon-minimiser) to schedule some activities when your local grid is greener.

**Embodied carbon**: the carbon emitted when creating a physical object. For the purposes of this exercise, we look closely at the carbon that is emitted when creating a device such as a smartphone, monitor, laptop or server. For consumer devices, the embodied carbon makes up the vast majority of the overall emissions, as much as 80% in most cases. For servers, the usage can make up a far bigger percentage of the emissions, but this depends on how the server is utilised. As embodied carbon is such an important number, this is why devices must be kept in operation for as long as possible. Getting a new phone every year or a new laptop every three years is not acceptable. See https://dataviz.boavizta.org/ and https://github.com/rarecoil/laptop-co2e for detailed breakdowns of different device types and manufacturer data. Understanding embodied carbon is critical for measuring your Scope 3 Emissions.

**Energy scopes**: the internationally recognised Greenhouse Gas Protocol uses the term ‘emission scopes’ to be used for reporting purposes. Broadly speaking, Scope 1 includes the burning of fossil fuels within an organisation’s operations. This would include operating a vehicle fleet or heating a building with gas-powered radiators. Scope 2 is the direct use of purchased electricity within an organisation’s operations. For a typical government department, this would include lighting, air conditioning and the power to run laptops and printers. Scopes 1 and 2 are generally easy to measure, just check your utility bills. Scope 3, on the other hand, is much, much bigger and more complex. For most organisations, Scope 3 makes up about 80% of emissions. In the broad definition, Scope 3 includes all the other activities needed to run a business or organisations, such as employee commuting, cloud hosting, purchased goods and the like. Scope 3 emissions fall into 15 subcategories, which can be found at: https://www.compareyourfootprint.com/difference-scope-1-2-3-emissions/. Government departments are obliged to report on Scope 3 emissions to Defra quarterly in the STAR report. The reporting of Scope 3 will become mandatory in the EU (see https://www.thomsonreuters.com/en-us/posts/esg/csrd-esg-regulations/) and was recently passed into law in California (see https://www.theguardian.com/us-news/2023/oct/09/california-carbon-emissions-law). It would seem likely that similar legislation will follow in the UK.

**ESG reporting**: Environmental, social and corporate governance. Our home planet is not in a healthy state. ESG reporting includes all legislation aimed at holding governments, institutions and corporations to account with regards to environmental and social issues. This now includes a wide array of things, such as the United Nations Sustainable Development Goals, Net Zero targets, Greening of Government Commitment, the Social Value Model and recent Corporate sustainability reporting legislation passed by the EU. DWP is committed to Net Zero by 2050 at the latest, and for all government departments abd ALBs, the Defra STAR report is the primary ESG reporting mechanism.

**GHG**: Green House Gas. CO2 is obviously the most well-known, but other GHGs include methane, nitrous oxide and sulphur dioxide, to name just a few. To make things easier, the abbreviation CO2e is often used, which stands for CO2 equivalent, where the warming potential of the various GHGs can be compared in a way which all can agree upon.

**GreenOps**: building on the job titles ‘DevOps’ and ‘FinOps’, ‘GreenOps’ is the role within a software team that looks at optimising the deployment and running of software (typically in the cloud) based on GreenSoftware principles. GreenOps is well aligned to FinOps, in that both typically look at reducing cloud usage, but GreenOps takes this one step further by including carbon as a cost.

**Location vs. market-based reporting**: carbon intensity can be reported on in two ways. With location-based reporting, the emissions are calculated by using the carbon intensity for the local or national grid. In this way, emissions can be calculated quite accurately. Market-based reporting allows companies to buy renewable energy certificates, for example from countries such as Norway. In essence, this is a form of offsetting, and the accuracy of this approach is a topic of debate. The Sustain.Life website recently published an article on this: https://www.sustain.life/blog/purchased-electricity-emissions-accounting-market-and-location-based. Most cloud providers use market-based calculations, which is why they can claim to be powered on ‘100% green energy’. The UK Government and Defra’s STAR report use a location-based approach, as the reliability and accuracy of market-based approaches can be difficult to verify. See https://www.gov.uk/government/publications/greenhouse-gas-reporting-conversion-factors-2023 for the conversion factors used by GOV.UK. The SCI also uses location-based reporting for their calculations.

**Net Zero**: the internationally agreed and legally binding term used to describe how organisations and countries will reduce their emissions by 2050 in order to keep as close to the 1.5C of global warming, the agreed ‘safe’ limit to sustain human and much of plant and animal life. For many organisations, this must mean producing zero or near zero emissions. See https://netzeroclimate.org/what-is-net-zero-2/ and https://energysavingtrust.org.uk/what-is-net-zero-and-how-can-we-get-there/ for further information.

**Offsetting, carbon-neutral**: although popular up until recently, these terms have fallen out of favour due to their vulnerability to ‘greenwashing’. Recent EU legislation has in fact banned the use of terms such as ‘carbon neutral’ (see https://carbonmarketwatch.org/2023/09/20/carbon-market-watch-welcomes-eu-ban-on-carbon-neutrality-greenwashing/). Instead, organisations must explain how they will reach Net Zero. For certain hard-to-decarbonise industries such as the manufacture of steel and cement, offsetting can be used as a last resort.

**Rebound effect**: the tendency for gains in efficiency to be outpaced by increases in demand. This can be observed in areas such as transport, where widening roads typically increases traffic, or in digital where, improving efficiency only increases demand, quickly cancelling out the efficiency gains. Sufficiency can be seen as a strong counterpoint to efficiency. Also see Wirth’s Law.

**Social Value Model**: this act was passed into UK legislation in 2020, and is composed of 5 themes which should be taken into account when awarding government contracts. Theme 3, Fighting climate change: Effective stewardship of the environment, is now 10% of the decision-making process when awarding large ICT contracts.

**Software Carbon Intensity specification (SCI)**: a new ISO standard for measuring the environmental impact of software produced by the Green Software Foundation. The SCI uses location-based reporting combined with embodied carbon to calculate the impact of a piece of software. See https://github.com/Green-Software-Foundation/sci/blob/main/Software_Carbon_Intensity/Software_Carbon_Intensity_Specification.md for details.

**UN SDGs**: the United Nations Sustainable Development Goals. These are the 17 internationally agreed goals which were adopted globally in 2017. They include many goals related to sustainability, and are often referred to within ESG reports.

**Wirth’s Law**: we are all probably familiar with Moore’s Law on computer performance. Wirth’s Law observes that software is getting slower more rapidly than hardware is becoming faster. It’s a good argument for sufficiency.