> 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/faq/analysis-and-design/faq-rigid-material-and-section-definition.md).

# Rigid Material and Section Definition

Many substructure objects ask for a **Rigid Section** or a **Rigid Material** in their **FEM** group, for example the pier cap, pier stem and pier column (Rigid Section) and the abutments (Rigid Material). They define the stiff elements OpenBrIM generates to connect parts of the analysis model, such as the links from a bearing to the pier cap when the bearing is offset from the support line, or the rigid surfaces of an abutment seat. They do not change the 3D shape of the object.

OpenBrIM has no built-in rigid material or rigid section, and a new project from a workflow template contains none. Create them yourself, the material in **Properties > Materials** and the section in **Properties > Sections**, then pick them from the list in the object's field. If the field is left empty, or a name is typed that does not match an existing material or section, the field reads NULL. The analysis then stops with a message such as `BridgeSeatMidRigidSurf.S1 is not assigned a material`, naming the generated element that has no material.

To establish a proper definition of a rigid material, users must exercise caution regarding two key parameters:

* Ensuring that the **unit weight** of the rigid material is **set to 0** is absolutely critical. Failure to do so could lead to the generation of excessive forces due to the self-weight of the rigid section.
* To prevent the creation of an **ill-conditioned matrix**, users must exercise caution when assigning stiffness values, particularly when using high values such as >10000 times E\*I or E\*A. It is advisable to define stiffness values that are only **100 or 1000 times** greater than those of the connected elements.

The below example serves, as an illustration, to grasp the logic behind defining rigid sections by comparing them with other sections within the project:

As seen below, the properties of "Rigid\_Section1" are 100 times greater than those of "Column1," which happens to be the largest section in the project. Hence, it is duplicated, and its sectional properties are multiplied by 100. Moreover, "RigidMaterial1" has a specified modulus of elasticity of 29000ksi, approximately 6.54 times higher than the modulus of elasticity of “FC\_5\_1/2ksi” concrete, which is 4428ksi. Consequently, the EI and EA values of the rigid section are 650 times larger than the largest section in the project. Additionally, the “**unit weight”** and **“Thermal Coeff.”** of "Rigid\_Material1" are explicitly set to 0.

{% hint style="info" %}
Duplicating a section might not be a good idea because it duplicates along with its shapes, and graphically, you will see a section in the FEA view at rigid section locations. Therefore, make sure that the section you use does not include any shapes.
{% endhint %}

![](https://openbrim.atlassian.net/wiki/download/attachments/2244214785/image-20230724-171701.png?api=v2)

![image-20240320-142753.png](https://openbrim.atlassian.net/wiki/download/attachments/2244214785/image-20240320-142753.png?api=v2)


---

# 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/faq/analysis-and-design/faq-rigid-material-and-section-definition.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.
