> For the complete documentation index, see [llms.txt](https://docs.cscale.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cscale.io/the-c.scale-tm-data-model/whole-life-carbon/refrigerant-emissions.md).

# Refrigerant Emissions

In C.Scale, fugitive emissions from refrigerant leakage are categorized as operational emissions. They are counted in life cycle stage B1.

For each year of operation, emissions from refrigerant leakage are calculated as:

$$
Emissions\_{\text{annual}} = (\text{ref charge}) \cdot (\text{ref leakage rate}\_{\text{annual}}) \cdot (\text{ref GWP})
$$

For each year where MEP systems are replaced/refurbished (denoted in C.Scale as the “refurbishment period”), emissions from refrigerant leakage are calculated as:

$$
Emissions\_{\text{EoL}} = (\text{ref charge}) \cdot (\text{ref leakage rate}*{\text{EoL}} + \text{leakage rate}*{\text{annual}}) \cdot (\text{ref GWP})
$$

### Estimating Total Refrigerant Charge

Estimates of total building refrigerant charge are based on data in Barbara Rodriguez’s dissertation entitled "Embodied Carbon of Heating, Ventilation, Air Conditioning and Refrigerants (HVAC+R) Systems." These data are collected from a sample of 20 LEED-certified buildings in the Pacific Northwest region of the United States.

### Refrigerant Leakage Rates

Annual and end-of-life refrigerant leakage rates are typically a model assumption, not a carbon reduction measures. In C.Scale, there are two options for leakage assumptions.

| Reporting Scheme    | Annual Leakage | End-of-Life Leakage |
| ------------------- | -------------- | ------------------- |
| LEED                | 2%             | 10%                 |
| CIBSE TM65 (Type 1) | 2              | 1                   |
| CIBSE TM65 (Type 2) | 4%             | 2%                  |
| CIBSE TM65 (Type 3) | 6%             | 3%                  |

### Refrigerant GWP

Throughout C.Scale, three options are given for specification-related options: High Carbon, Average, and Low Carbon. Typically, these refer to the 80th, 50th, and 20th percentile of GWP values for available materials. We were unable to replicate this methodology for refrigerants, though, as the overall distribution of refrigerants skews very high–and this highly skewed distribution doesn’t represent the choices designers are making on their projects. In the refrigerant model, these three choices are keyed to specific refrigerants as follows:

<table><thead><tr><th width="202">Specification Level</th><th width="406.3333333333333">Reference Refrigerant(s)</th><th>GWP Value</th></tr></thead><tbody><tr><td>High Carbon</td><td>HFC Refrigerant (e.g., 60% R-410a; 40% R-134)</td><td>2000</td></tr><tr><td>Average</td><td>Low-GWP Refrigerant (e.g., R-513)</td><td>700</td></tr><tr><td>Low Carbon</td><td>Next-Gen Natural Refrigerant (e.g., CO2)</td><td>5</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cscale.io/the-c.scale-tm-data-model/whole-life-carbon/refrigerant-emissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
