Software Sustainability in a Regulated Landscape
summary
A case study of Autostrade describes a sustainability workflow that scans a software portfolio using static analysis against ISO-derived rules (ISO 21031 / ISO 5055), pulling code and DDL from GitLab and combining that with runtime telemetry and amperometric validation. The commercial tooling integrates into CI/CD as “Green Gates” and provides ISO 5055 rules for developers; measured results include ~15% CO2 reduction for a targeted subset, ~14% savings for one live traffic app, ~20% (~2300 kg/yr) for a 10-asset pilot, and amperometry showing 36.5% lower energy use and 38% faster throughput.
AI-written summary · about
chapters (10)
- 0:00Digital sustainability matters
- 3:12Software's IT emissions
- 7:25EU regulations CSRD
- 12:46Sustainable software standards
- 17:41Autostrade case study
- 21:37Digital transformation sustainability
- 27:48Immediate savings side effects
- 30:22Managing embodied carbon
- 33:40Tools for digital footprint
- 35:26Q&A
related talks
30mPractical approaches to measuring software sustainability via tooling [...]
31mBridging Product and Engineering for a Greener Future: Embedding Sustainability into Software Teams
45mLaying the Foundation on OSS Environmental Sustainability
17mBuilding a Transport Emission Management Application: A Story of Idealism and ISO...
07mInterview
39mApplying refactoring techniques ...
38mGreen software: How can tech contribute to worldwide sustainability effort?
35mGreen Software Principles and Embedding Carbon Awareness in Your Applications