> 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/truss-bridge-workflow/substructure-tb/temporary-shoring-tb.md).

# Temporary Shoring \[TB]

## Temporary Shoring

Temporary shoring is modeled as a box-shaped structure placed along the bridge alignment, for example to support the structure or retain soil during construction. Its position, plan dimensions and height are defined by the parameters below.

### General

**Alignment:** The alignment the temporary shoring is placed on.

**Station:** The station of the temporary shoring along the alignment. The temporary shoring is generated relative to this station on the Proposed Grade Line (PGL).

**Transverse Offset:** Offsets the temporary shoring in the transverse direction. A value of zero places the temporary shoring on the PGL. Positive values offset it to the right when looking upstation along the PGL, and negative values offset it to the left.

**Elevation:** The elevation of the temporary shoring.

**Skew:** Rotates the temporary shoring in plan. The temporary shoring is first positioned at the specified station along a line perpendicular to the PGL, which is then rotated by the skew angle: a positive value rotates it clockwise and a negative value counterclockwise.

**Width:** The width of the temporary shoring in the transverse direction.

**Length:** The length of the temporary shoring in the longitudinal direction.

**Height:** The height of the temporary shoring.

**Thickness:** The wall thickness of the temporary shoring.

### Piles

The pile inputs below describe an optional pile layout under the temporary shoring. They are currently hidden in the interface and are kept for future use.

**Pile Section:** The section profile of the temporary shoring piles, imported from a section database or defined under Properties > Sections.

**Pile Length:** The length of the temporary shoring piles, which sets their embedment depth.

**Pile Space Longitudinal:** The spacing between piles in the longitudinal direction, along the bridge alignment.

**Pile Space Transverse:** The spacing between piles in the transverse direction, perpendicular to the bridge alignment.

**Pile Offset From Bottom:** The vertical offset of the piles from the bottom of the temporary shoring.

### IFC

**Type:** The IFC entity type used when the temporary shoring is exported to IFC. The default is IfcBuildingElementProxy; other standard IFC element types can be selected.

**Predefined Type:** The IFC predefined type of the exported element. Available options:

* USERDEFINED.TEMPORARY\_SHORING (default)
* USERDEFINED
* NOTDEFINED

**Export to IFC? \[Yes/No]:** Controls whether the temporary shoring is written to the IFC file. Select No to leave it out of the export.


---

# 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/truss-bridge-workflow/substructure-tb/temporary-shoring-tb.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.
