> 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/properties-ex1-cug/materials-ex1-cug.md).
# Materials
This section defines material properties for concrete, reinforcement steel, structural steel, and prestressing steel.
{% hint style="info" %}
**Navigation:** Properties > Materials
For detailed parameter explanations, see the [Materials Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/properties-cug/materials-cug).
{% endhint %}
## Steps
### Step 1: Navigate to Materials
Navigate to **Properties > Materials** in the tree view.
### Step 2: Import Steel Materials
Click the **three-dots icon** on the first cell of Name and select **Import Material**.
Import the following steel materials from OpenBrIM Library:
| Material Path | Material Name |
| ---------------------------------------------------------------------------- | ------------- |
| OpenBrIM Bridge Objects > Steel Material Database (US) > Reinforcement Steel | A615\_60 |
| OpenBrIM Bridge Objects > Steel Material Database (US) > Structural Steel | A709\_50W |
### Step 3: Import Concrete Materials
Import the following concrete materials:
| Material Path | Material Name |
| --------------------------------------------------------------------- | ------------- |
| OpenBrIM Bridge Objects > Concrete Material Database (US) > US AASHTO | Fc\_3\_1/2ksi |
| OpenBrIM Bridge Objects > Concrete Material Database (US) > US AASHTO | Fc\_4ksi |
| OpenBrIM Bridge Objects > Concrete Material Database (US) > US AASHTO | Fc\_5ksi |
| OpenBrIM Bridge Objects > Concrete Material Database (US) > US AASHTO | Fc\_6ksi |
### Step 4: Import Prestressing Steel
Import the prestressing steel material:
| Material Path | Material Name |
| --------------------------------------------------------------------------- | ----------------------- |
| OpenBrIM Bridge Objects > Steel Material Database (US) > Prestressing Steel | Grade270\_lowrelaxation |
Quick Tip: Stress-Strain Curves
Each material type comes with a default stress-strain curve for section capacity calculations. To view or customize:
1. Click the **three-dots icon** on **A615\_60** and select **Edit**
2. Click on **Stress/Strain Model** dropdown to modify parameters
3. The **Stress/Strain Curve** updates automatically based on the selected model
### Step 5: Create Rigid Material
Add a new row and enter **RigidMaterial** as the name.
{% hint style="warning" %}
Set the **unit weight** of rigid materials to **0** as a general practice.
{% endhint %}
## Verification
{% hint style="success" %}
After completing these steps, the material definitions should appear as shown below.
{% 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.openbrim.org/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/properties-ex1-cug/materials-ex1-cug.md?ask=&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.