> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/openbrimfea/model-fea/properties-fea.md).

# Properties \[FEA]

Properties holds the material and section definitions that turn geometry into stiffness.

* [Materials](https://docs.openbrim.org/templates/openbrimfea/model-fea/properties-fea/materials-fea.md) supply modulus, Poisson's ratio, density and thermal expansion - the properties that drive the analysis - plus the strength values and time-dependent behaviour used by design and staged construction.
* [Sections](https://docs.openbrim.org/templates/openbrimfea/model-fea/properties-fea/sections-fea.md) supply the cross-sectional properties: area, moments of inertia, torsion constant and shear areas.
* [Reinforcing Bars](https://docs.openbrim.org/templates/openbrimfea/model-fea/properties-fea/reinforcing-bars-fea.md) and [Strands](https://docs.openbrim.org/templates/openbrimfea/model-fea/properties-fea/strands-fea.md) are property library entries describing bar and strand sizes. They are used by design and section analysis; they do not create elements of their own.

These objects are referenced by name from elements, so one definition serves many members - and a change to a material or section propagates to every element that uses it.


---

# 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.openbrim.org/templates/openbrimfea/model-fea/properties-fea.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.
