> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/support-and-training/other-support/platform-generic-material-data.md).

# Platform Generic Material Data

The platform's generic material data comprises a default collection of materials with associated thermal, moisture, and carbon attributes.&#x20;

All thermal and moisture data are a collation from various industry sources. All embodied energy,  greenhouse gas and water data default to environmental flows associated with construction material type, as per the Environmental Performance in Construction (EPiC) Database (Published 2024).&#x20;

This collection includes 78 materials organised into the following categories:

* External Siding
* Concrete Masonry
* Metals
* Plastics
* Timber
* Bracing
* Building Membranes
* Insulation
* Internal Finishes
* Miscellaneous

Detailed descriptions for each material in this collection are provided in the following pages.

{% hint style="info" %}
**Important:** These materials are generic in nature and should be reviewed for consistency and alignment with your project assumptions. You may update individual materials as needed to match your specific requirements.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.betterbuilding.io/support-and-training/other-support/platform-generic-material-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
