{"id":440693,"date":"2026-05-19T14:00:00","date_gmt":"2026-05-19T13:00:00","guid":{"rendered":"https:\/\/www.glpi-project.org\/?p=440693"},"modified":"2026-05-19T08:25:08","modified_gmt":"2026-05-19T07:25:08","slug":"understand-and-measure-your-carbon-footprint-with-glpi-carbon","status":"publish","type":"post","link":"https:\/\/www.glpi-project.org\/en\/understand-and-measure-your-carbon-footprint-with-glpi-carbon\/","title":{"rendered":"Understand and Measure Your Carbon Footprint with GLPI Carbon"},"content":{"rendered":"\n

In October 2025, we released a new tool to help you understand the environmental impact of operating digital services \u2014 computers, servers, monitors, mobile devices, and network devices. The plugin Carbon, available to everyone via the GLPI Marketplace and our project's GitHub, will outline the carbon footprint of your company's digital assets.<\/p>\n\n\n\n

Everybody has an important role to play in reducing carbon impact and reversing climate change. This project, coordinated by IRT SystemX in partnership with Teclib', and other organizations within the IEN initiative, started with a fundamental question: how do you actually measure the impact digital services have on climate change?<\/a><\/p>\n\n\n\n

The impact of running digital services and assets<\/strong><\/h2>\n\n\n\n

At a high level, powering hardware uses energy. Producing that energy involve emitting carbon into the atmosphere \u2014 contributing to climate change.<\/p>\n\n\n\n

When you use digital services, whether on cloud infrastructure or on-premises, energy is consumed to deliver the tools you rely on daily. And energy is not the only resource consumed to deliver digital services worldwide.<\/p>\n\n\n\n

Understanding the impact of digital tools involves measuring indirect emissions, primarily from Scope 2 (energy consumed during operation) and Scope 3 (everything else \u2014 from manufacturing to logistics). Did you know that Scope 3 alone accounts for more than 70% of total carbon footprint for most organizations?<\/p>\n\n\n\n

But here's the problem most teams run into: where does that data actually come from?<\/a><\/p>\n\n\n\n

Two data sources working together<\/strong><\/h2>\n\n\n\n

Measuring carbon emissions from digital assets requires two distinct types of external data.<\/p>\n\n\n\n

The first is the carbon intensity of the electricity grid. The carbon cost of powering a device in S\u00e3o Paulo is different from powering the same device in Tokyo or Paris \u2014 because the energy mix varies. In Brazil, hydroelectric power makes up a large share of the grid; in Germany, coal still plays a role. The Carbon plugin integrates with Electricity Maps, a real-time platform that tracks where the world's electricity comes from and how much CO2 is emitted to produce it, per region, per hour.<\/p>\n\n\n\n

The second is the environmental cost of manufacturing those assets. A server doesn't become a server for free \u2014 extracting the raw materials, assembling the components, and transporting the finished product all emit carbon before the device ever gets plugged in. For this, the plugin uses Boavizta API, maintained by a French non-profit dedicated to Green IT. Boavizta provides carbon footprint data from asset fabrication and transport, and goes beyond greenhouse gas emissions to also account for abiotic resource depletion and primary energy consumption.<\/p>\n\n\n\n

GLPI already holds the asset data, so Carbon can connect those assets to these two external sources to produce meaningful, localized estimates.<\/p>\n\n\n\n

Calculating the carbon emissions of your fleet<\/strong><\/h2>\n\n\n\n

Most of the carbon associated with digital assets doesn't come from running them \u2014 it comes from making them. This is what the plugin calls embodied carbon, and it will likely be the dominant figure you see when you first configure Carbon for your fleet.<\/p>\n\n\n\n

To generate accurate estimates, each asset needs a few pieces of information set correctly in GLPI:<\/p>\n\n\n\n