❌

Vue normale

How IT can get more sustainable quicker: notes from Green IO

2 octobre 2026 à 02:00

At Green IO this week, I heard about offshore wind, sustainability data, and cloud certification. This post has some notes I took. They all in some way relate to what can get us to more sustainable IT quicker.

Better sustainability data

It's really hard to reason about your organisation's impacts without data. Hannah Smith (virtual) and Oliver Cronk (in-person) talked us through a new Green Web Foundation community project that helps with better data: Digital Impacts Schema and Taxonomy (“DIST”).

DIST has three parts:

  • a taxonomy (ensures you can compare “apples to apples” by categorising impacts in upstream impacts like software and hardware, operational impacts like employee devices and cloud services, and downstream impacts like end-user devices),
  • methodologies to measure, calculate, and estimate impacts, tagged with DIST categories,
  • a structured data format to exchange the collected data in a standardised and machine-readable manner.

So it answers what data to collect, how to collect it, and how to describe it once you've got it, all in one system.

Offshore wind

In "Can offshore wind power the AI boom?", professor Susan Gourvenec of the University of Southhampton talked to us about offshore wind. She debunked some myths, like how much space they use: only a very small proportion compared to other bits. Do they kill birds? Yes, but cats are their main killer by a long mile. Is it expensive? The cost of delaying decarbonisation is much higher, both in terms of economic (productivity) and social costs. Aren't the materials environment unfriendly? Yes, but greener steel is in the works. My main takeaways: offshore wind takes relatively little space (in relation to other offshore activities), there is a lot of it possible, and it could be enough to power the AI boom.

Measuring internal AI emissions

Mark Buss of OVO Energy shared how they ended up measuring their internal AI usage. OVO give everyone who works there “enterprise level productivity tooling” and engineers access to Claude, i.e. they use a lot of it. Some of the staff started asking about the impact of that usage, people wanted to know for a myriad of reasons. So OVO ran a series of in person workshops, focused on environmenral impacts of AI, making space for both positives and negatives. There's many ways to look at it, Mark explained, saying that “you can't decarbonise a cow but you can lower emissions from data centres”. He emphasised context: when calculated all their AI use, and compared it to emissions associated with other processes at OVO, and saw it was only marginal compared to cloud cost (a bit more), business travel (much more), and the fossil part of the energy they sell (magnitudes more).

Standardising energy use of streaming

Marisol Palmero of IEEE got us up to speed with the standardisation of energy-aware streaming. She explained that only in 2025, AI energy usage overtook that of streaming services like Netflix and Disney+. But they are quite different: most energy use of streaming associated with the user's devices (battery needed to power graphics on screens etc), whereas most energy use of AI is associated with data centres. Marisol explained measuring emissions associated with streaming is increasingly less voluntary: there's more preasure from regulation (CSRD, SEC Climate Disclosure Rule, UK SDR) and Omnibus 1 means evidence will be required. It's tricky as standards around this aren't interoperable yet. IEEE works on Trustworthy Energy Attribution & Measurement (TEAM) to help solve for this. And such efforts can have an impact: “standards are how we move individuals to collective action”, Marisol said.

A pipeline GreenOps observability

Diana Todea of VictoriaMetrix and Julien Nioche of DigitalPebble discussed how we already have the data we need for GreenOps. We all know that cloud providers give data that isn't very useful or actionable, Julien explained. Open Source projects can help, including SPRUCE, which can come third-party data, is actively maintained, and available free. Diana showed how she used SPRUCE and a number of other tools to build a pipeline for observability of GreenOps including a cool dashboard, and in general, the importance of observability. What's promising in that regard is that the Green Software Foundation (GSF) are taking their Software Carbon Intensity (SCI) to OpenTelemetry through semantic conventions.

Certification for data centres

“Please raise your hand if you fully understand the environmental and social impact of your cloud usage and were aware at the time of procurement”… tricky questions were asked during the session by Emily Watson-Breeze and Barton Finn of TCO Certified, who built a certification for “cloud resources” over the last few years to answer questions like that. So not data centres per se, but the cloud services that run in them. It looks at requirements for physical layer (data centre facility), IT hardware layer (servers, storage, network equipment), and operations & management (certified cloud resource). And it even looks at the very common case where cloud resources are offered as a service: you're not buying a server, but paying to use it for a specific time. It's really hard because there is hidden structure, a complex value chain, and data that is hard to compare due to lack of standards and incomplete datasets. This kind of certification can help both procurers and suppliers. I cannot wait for hyperscalers to get on this, and until they are, I guess we should all be pushing for that when procuring cloud products.

Wrapping up

It wasn't because before lunch started, the host announced “the afternoon will be all about AI at scale” that I missed taking notes for a lot of the afternoon sessions: I ended up having some great hallway chats and left a little earlier to get on my train back.

I enjoyed meeting folks at Green IO and learning about a wide variety of topics. I even got to hang out a little bit with people from the ClimateAction.Tech community, which unites tech workers that try to change the system to face the climate crisis (there's a very active Slack instance you can join if you're interested!).


Originally posted as How IT can get more sustainable quicker: notes from Green IO on Hidde's blog.

Reply via email

AI and greener choices

26 juin 2026 à 02:00

The earth is heating up and AI isn't helping. It drives major increases in electricity use, water use and CO2 emissions. Yet, industry and governments alike seem keen to leverage the latest tech. Can we make greener choices?

Yesterday, I spoke at a conference on AI in government about sustainable choices. The presentation and slides were in Dutch, this post is a high level summary of what I covered.

As the presentation took place during a record-breaking heatwave, which meteorologists attribute to climate change, and there were some airconditioning-related issues, very little irony was lost on us.

Words matter

I started out talking about if AI is good or bad for sustainability and called it the wrong question. It's the wrong question, because both AI and sustainability are concepts that have many meanings.

AI can be understood in different ways:

  • as a technology, there are many kinds; Microsoft alone has 78 products named Copilot, but also, there are many types of AI, like computer vision, natural language processing, generative AI and agentic architectures. Traditional vs generative can be a useful distinction in sustainability, because of the difference in energy impact.
  • as an economic phenomenon (it isn't profitable yet, so it may get more expensive or introduce ads, and there are lots of financial stakes that explain why it's sometimes forced on consumers)
  • as an infrastructure (behind the cloud metaphore, there are very real data centres that warrant closer inspection)

Sustainability is multi-faceted too. In the Web Sustainability Guidelines, we center our definition around three pillars that ultimately need balance between them: Planet, People, and Profit:

  • Planet: its surface temperature rises due to emission of greenhouse gases that trap heat, and it has a finite amount of water of which only a small portion is suitable to drink.
  • People: think of people, including children as young as 11 years old, who are working in cobalt mines in Congo for the batteries that power our devices, or of people (and hospitals) who had no electricity during last year's Spain heatwave, while data centres continued uninterruptedly.
  • Profit: within our capitalist system, the needs of planet and people need to be balanced with profit, in order for anyone to successfully make the case for change.

So, there's some nuance about what the words mean, but despite that, it's worthwhile to try and reduce climate impact of our services. The pope said so, and in government, it's an increasingly a priority (like in the UK, where the Digital Service expanded their design guidance last year with principle 11: Minimise environmental impact) .

It's ok not to use AI

I shared five tips to make greener choices around AI, but couldn't help myself to add a bonus tip as tip zero: in many cases, not using AI for your project makes the most sense. Which is fine.

Many of us will have sat in meetings around a new idea or project, where someone put up their finger and said ”oh, maybe we can use AI for this”. The AI vendors primed us for this with hype.

Often, using AI, and especially generative AI, is like going to your local corner shop using a helicopter. What if you could solve the same problem with a couple of lines of Python, and Excel-sheet, people, or manually summarising?

I wanted to mention this specifically, because nobody wants to be the downer in the group and suggest not doing the thing that everyone is hyped about. But to be sustainable, we need to pick out just the cases where AI is absolutely necessary, and go without it for anything else.

Five tips to make greener choices

When using a specific type of AI actually solves your problem best, here's five tips to make greener choices.

Smaller models

When using generative AI, model size differs wildly. An example of a large model is DeepSeek v4 Pro, which has 1.6 trillion parameters (12 zeroes), while there are small models like Hugging Face's SmollLM that has 135 million parameters (6 zeroes).

A smaller model could save 30⨉ emissions of CO2 (and equivalent greenhouse gases), explain Luccioni, Jernite, & Strubell in their paper “Power Hungry Processing: Watts Driving the Cost of AI Deployment?”.

More specific models

A lot of generative AI uses so-called general purpose models, which are systems that know pretty much everything about the world. When hiring humans, we usually list a specific area of expertise. That's partially because there are no humans that know it all (just ones that think they do).

We should try to do the same with language models. If we're building a system that answers questions about taxes, we don't need to tell it what the capital of France is.

In “Power Hungry Processing”, Luccioni, Jernite, & Strubell explains this: “multi-purpose generative architectures are orders of magnitude more expensive than task-specific systems for a variety of tasks, even when controlling for the number of model parameters” (emphasis mine).

Be smart about data centre usage

In many applications of AI, the relevant software needs lots of computing: GPUs, CPUs, memory, and storage. This computing is often done in the “cloud”, or: data centres. The climate impact of data centres is widely seen as three components: electricity, CO2 emissions (and equivalent greenhouse gases), and water usage.

The International Energy Agency predicts the amount of data centres to double or triple over the next few years. The electricity used for this will be green, partially. But it won't all be green : gas and coal will continue to be a share of what powers data centres.

On an operational level, we could reduce the load on data centres by reducing how many tokens we use, via smarter prompting (shorter, more specific, more explicit, less repetition through variables). The paper Smarter, smaller, stronger by Perez Ortiz and Drobnjak details tests that show reducing a response from 400 to 200 words reduced energy consumption by 54%.

On a policy level, one tip I learned at the AI reporting event I attended, is to question how many 9's you really need. Data centres are convenient because they offer compute for rent and make it easy to scale. And they offer uptime, guaranteeing sometimes up to 99,99999 availability: five nines. More nines could mean less sustainability: some data centres will use diesel power or other unsustainable sources when they have a power cut. So to get to a higher uptime guarantee, they need to make such choices. What if we required less nines? What if we decided it's ok to have the AI thing not work for a couple of days a year?

Recognise greenwashing

Greenwashing is everywhere, and to make sustainable choices, we'll need to develop our skills to recognise it from afar. Sometimes it's easy to recognise, like an airline that said with them, you can “fly responsibly” (a Dutch court said this is misleading). EU Directive 2024/825 effectively forbids greenwashing, but companies still tend to do it.

Examples from The AI Climate Hoax include:

  • “bait and switch”: often “traditional” AI has a much smaller footprint than generative AI; when companies point at how clean their traditional AI is while ignoring the effect of their generative AI, this is misleading
  • use of (own) research with little evidence
  • hidden emissions through clever bookkeeping (often leaving out Scope 3 or ‘embodied’ emissions)
  • empty promises, like pointing at technologies that don't exist yet
  • downplaying via selective shopping in data or data without context
  • fatalism: “we'll reach those sustainability goals anyway, why bother trying”

Measuring matters

My last tip is around data collection. It's tricky to know how much energy data centres use, not the least because Big Tech successfully lobbied the EU to treat energy usage data as company secrets.

When you do get data, it often does not include Scope 3 emissions, which are estimated to be a very large part (I've seen percentages from 30 to 89%, and I am not sure what's right, other than that it is large).

There can also be a major difference in reporting: some companies do location-based reporting, others market-based reporting. Location-based means that you get information about how much a specific data centre is actually using, whereas with market-based, factors outside are taken into account, including certificates for carbon.

Location-based data is the most helpful if your team is trying to make optimisations, because it allows them to see the numbers go down (or up),where they would appear constant with market-based reports.

Lastly, I mentioned grid intensity: because there are many different power sources, and they deliver different amounts of energy depending on the time and location, grid intensity vary. For instance, if it's sunny and windy today at noon, the grid intensity will be low because there is lots of green energy available. At other times there's less.

Your application can use this difference, that constantly changes, by moving your computing to the right place at the right time. This is also called “carbon aware computing” and companies like Google already do it, to save emissions and costs at the same time.

Summing up

AI-related electricity usage, water use, and carbon emissions can be huge. That's a problem, but it's also an opportunity (cheesy but it's true). There is lots of low-hanging fruit that we can start addressing. As there's still so much to reduce, our efforts really can make a dent.

I really enjoyed giving this talk and hearing the audience comments afterwards. The main worry seems to be: how do I sell this within my organisation, and an answer emerged in the group: cost-savings and carbon-savings often go hand in hand.


Originally posted as AI and greener choices on Hidde's blog.

Reply via email

❌