Search eceee proceedings

Ecodesign requirements for software: another possible horizontal approach?

Panel: 2. Future and innovative policies

This is a non-peer reviewed extended abstract. No paper available.

Author:
Mathieu Rama, ECOS (Environmental Coalition on Standards), Belgium

Abstract

Software, as opposed to hardware, can be defined as the instructions, programs and data that power computers and execute tasks. Initially mainly installed on computers, software is now used on a wide variety of products. Smartphones, of course, but also a significant and growing quantity of IoT (Internet of Things) devices. Even though seemingly immaterial, software can have an important impact on the energy and material efficiency of a product.

Firstly, concerning energy efficiency, software practices have been identified as increasing the energy use of a product, leading batteries to empty earlier than anticipated. Secondly, concerning material efficiency, part-pairing has been identified as a major barrier to repair activities and software updates can also make certain products obsolete, resulting in being discarded even though technically functioning. The absence of software updates, also, can make certain products unsafe to use.

The issue of software sustainability is not flying under the radar of EU institutions. A few legislative texts, most of them having recently been through the co-legislative process, contain provisions about the design of software. Historically, this has started with ecodesign regulation. The first product category that has been subject to ecodesign requirements on software is 'servers and data storage products' where both data deletion and firmware updates are tackled. Smartphones and tablets have followed with rules on software updates availability and part-pairing. These rules will be in force starting June 2025. Computers will be tackled too once the current rules are finally revised.

However, the most promising legislative efforts to tackle the sustainability of software do not come from product specific ecodesign regulations. As software are now used by many different types of products, some of them not being in scope of ecodesign and energy labelling regulations, a horizontal approach makes a lot of sense. As opposed to a product-by-product approach, a horizontal approach applies to many types of products at once and potentially allows for more energy and material savings.

At EU level, this strategy has, for example, been implemented on off mode, standby mode, and networked standby through ecodesign requirements, as well as on batteries through a new regulation. This approach is also supposed to be favoured in the framework of the forthcoming Ecodesign for Sustainable Products Regulation.

Horizontal regulation on software actually already exist in the context of the new battery regulation: batteries have to have a reset function and part-pairing of batteries is unlawful under this regulation. Part-pairing has also recently been discussed by the European parliament who, in its amendments to the directive on common rules promoting the repair of goods, has suggested that Member States “[prohibit] any contractual, hardware or software technique that could prevent or limit repair”. The Cyber Resilience Act as well, focusing on making products with digital elements more secure, will eventually make products more durable and reliable through better resistance to cyber attacks.

This paper aims at investigating the opportunity for horizontal ecodesign requirements on software. After going through a series of examples of material efficiency and energy efficiency issues related to the design of software, existing European Union's regulations and standards aiming at solving these issues will be analysed. Whether these standards and regulations are going far enough to regulate this sector will also be discussed. Finally, recommendations will be made on what ecodesign requirements on software should contain if tackled horizontally.

Downloads

Download this presentation as pdf: 2-234-24_Rama_pres.pdf