Your fridge has an energy label. Why not your software?
Software is bought on features, price and support. The electricity it draws arrives later as hosting bills and hardware refreshes, and nobody attributes it to the product.
The W3C suggests checking suppliers against green criteria before you buy. GreenCode rates software before and after it works on it.
GreenCode helps tackle this by rating a system before and after optimisation, against the Software Carbon Efficiency Rating or an ISO/IEC 21031-aligned equivalent. The grade travels with the evidence behind it. More on this.
Your fridge has an energy label. Why not your software? Software is bought on features, price and support. The electricity it uses turns up later. It arrives as hosting bills and new hardware. And nobody links that cost back to the product. Here is the fix you can use today. Ask suppliers how they measure their software's energy, and on what workload. Prefer a rating from a repeatable method that someone else can check. Add an energy requirement to your tenders, next to security. A rating buyers can ask for changes what suppliers build. The W3C suggests checking suppliers against green criteria before you buy. In tenders, point to the Software Carbon Intensity method, now an ISO standard. Or to Germany's Blue Angel criteria for energy-efficient software. GreenCode helps tackle this by rating software before and after it works on it. The grade travels with the evidence behind it. That was GreenCode Tech Tip number twenty-nine. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this
