Positioning against existing frameworks
This method retains its foundations, rules, models, hardware and use-case structure. PCRs specify assessment requirements for a defined boundary; D4B uses them to improve its framework and make its choices explicit, without claiming overall compliance.1
Framework map
Digital environmental assessment includes several complementary approaches2:
| Framework | Coverage | Strengths | Boundaries and limitations |
|---|---|---|---|
| ADEME / ARCEP product category rules | French digital services | Official framework, multiple indicators, three tiers | Limited granularity for some equipment; French context |
| Boavizta | Hardware components and equipment | Detailed decomposition, open source | Partial use-case coverage; service scope needs additional definition 3 |
| GreenIT | Awareness and practical use cases | Accessible explanations and digital sufficiency | Document types and methods vary by publication |
| Green Software Foundation SCI | Software carbon intensity | Explicit boundaries and functional unit | Carbon only; hardware manufacturing included through allocation |
| PAIA, MIT | Consumer electronics | Parametric product modeling | Product-centered rather than service-centered |
| imec NetZero | Semiconductors and components | Manufacturing process detail | Specialized; applicability depends on access and available inventories 4 |
| Cloud Carbon Footprint | Cloud infrastructure | Component energy coefficients, open source | Carbon-centered and cloud-focused 5 |
| UBA Green Cloud Computing | Cloud and datacenters | Virtual-resource allocation, multiple indicators | German and datacenter context |
This map describes complementary uses, not a precision ranking or certification of compliance. The dated source review identifies recent contributions including SCI for AI and component models.
What is adopted
| Framework | Contributions adopted in this methodology |
|---|---|
| ADEME / ARCEP | LCA framing based on ISO 14040/14044. A multicriteria perspective, with nine D4B indicators and an explicit mapping to the 2026 PCR. Three tiers: user devices, networks and computing centres. Equipment or system approaches according to control over the scope. |
| Boavizta | Materials → components → equipment decomposition and component-to-equipment modelling. Distinction between explanatory models and generic factors. Transparent data and open source. |
| UBA Green Cloud Computing | Virtual-resource allocation using vCPU, vDisk and vNIC. Supporting infrastructure, including cooling and PUE, accounted for through documented allocation. Multiple indicators: GWP, ADP, cumulative energy demand and water. |
| Green Software Foundation (SCI) | Explicit boundaries and a unit of analysis related to the function delivered. Connection between usage, infrastructure and impact. |
| GreenIT | Practical use cases and user journeys. Sufficiency as a reduction strategy. Explanations accessible beyond LCA specialists. |
What is adapted
| Topic | Relationship with the PCRs | D4B choice retained |
|---|---|---|
| Boundary | Whole application and explicit study period | Page, session or request calculations, to be aggregated |
| Indicators | Sixteen EF categories in the 2026 parent PCR | Nine indicators, with coverage and gaps stated |
| Network | Fixed and variable contributions in Internet access/application PCRs | Per-GB example; difference documented |
| Cloud | Service-unit factors and specific allocation rules | Resource estimates where appropriate, without automatic equivalence |
| Quality | Six criteria in the parent PCR | Separate D4B grid with an explicit mapping |
| AI | Application time boundary differs from model lifecycle | Training, media and limitations retained |
These differences are detailed on the relevant pages. Compatible documentation additions can be incorporated directly. Changes to formulas, factors or scores require a separate analysis of their effects on results.67
Distinctive organization
- A modular architecture for discovery, scoping and implementation.
- One central assumptions and defaults register.
- An explicit link to the versioned canonical
digital4better/datarepository.8 - A hardware chain from materials to components, equipment, infrastructure and services.
- Visible allocation, double-counting, robustness and time conventions.
Assumptions and limitations
- This is an editorial and methodological positioning, not an exhaustive normative comparison.
- Convergences and differences should be revisited as frameworks evolve.
- Specialized frameworks such as PAIA and imec are only partially reflected here.