> 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/steel-tub-girder-bridge-workflow/properties-stg.md).

# Properties \[STG]

The properties of bridge elements can be defined using this section of the workflow. The Properties section includes material definitions, rebar definitions, section definitions, strand definitions, bolt properties, and definitions related to pushover analysis.

Generally, the properties defined in this section are used in the following stages. For instance, a concrete type such as Fc\_4ksi can initially be defined in the Properties -> Materials section and later assigned to the Concrete Deck by using the related parameter on Superstructure -> Deck -> Concrete Deck.

There is no rule that definitions for this stage must be done after the Bridge Geometry. However, property definitions for related elements must be done prior to the modeling/definition stage of those elements.

For further explanations of each OpenBrIM object, please refer to the relevant section of the documentation.


---

# 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/steel-tub-girder-bridge-workflow/properties-stg.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.
