> 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/concrete-u-girder-bridge-workflow/substructure-cug/pile-cug/pile-layout-cug.md).

# Pile Layout \[CUG]

## Pile Layout

The Pile Group workflow item enables the definition of multiple piles under the same substructure within a single set of inputs, offering a more efficient method for defining the substructure components.

### General

**Substructure:** Choose the substructure element associated with the pile group, such as end or interior bents, columns, or pile caps.

**Pile Data\[Grid (Rectangular)/Custom]:** Specify the method of inputing pile group data. Selecting **Grid (Rectangular)** activates the number and spacing cells in the X and Y directions. If the pile grid is not rectangular, select the **Custom** and specify the piles individually.

**Custom:**

* **Longitudinal Offset:** Employed to determine the position of the pile. Longitudinal offset along the Projected Grade Line (PGL), where 0 refers to the center point of the substructure above.
* **Transverse Offset:** This parameter can be used to determine the offset value for the pile in the transverse direction, where a value of 0 places the pile at the center of the chosen substructure elements. A negative value will offset the pile to the left, and a positive value will offset it to the right when looking up-station along the PGL.\
  ![image-20240627-113141.png](https://openbrim.atlassian.net/wiki/download/attachments/2541748245/image-20240627-113141.png?api=v2)

**Number of Piles X (Along Station):** Specify the number of piles along the station axis.

**Spacing of Piles X (Along Station):** Specify the spacing of piles (from one center to another) along the station axis.

**Number of Piles Y (Transverse Direction):** Specify the number of piles in the transverse direction.

**Spacing of Piles Y (Transverse Direction):** Specify the spacing of piles (from one center to another) in the transverse direction.

![image-20241126-115507.png](https://openbrim.atlassian.net/wiki/download/attachments/2541748245/image-20241126-115507.png?api=v2)

**Pile Length/Section:**

* **Section Length(Starts at the bottom of footing):** The top of the pile, which begins at the bottom of the footing, serves as the starting point for section definition. Users can define multiple rows to create sections with varying characteristics. The total length of the pile is calculated by summing the lengths of each row.
* **Start Section:** The starting location of a section is determined by adding the lengths of all previously defined rows. If it is the first row, then the starting point is at the top of the pile.
* **End Section:** The position of the end section is determined by adding the distance defined in this row to the sum of all previously specified rows.

**Section Orientation:** Rotates the pile section; when set to the default value of 0, the X direction in the section editor aligns with the longitudinal direction, while the Y direction represents the transverse direction.

![Pile section orientation diagram](https://openbrim.atlassian.net/wiki/download/attachments/2541748245/image-20230317-162310.png?api=v2)

**Batter Angle (Longitudinal):** Batter (tilt) angle of the piles in the longitudinal direction (along the station). It applies to every pile of the layout. Default is 0 (vertical piles).

**Batter Angle (Transverse):** Batter (tilt) angle of the piles in the transverse direction. It applies to every pile of the layout. Default is 0 (vertical piles).

**Embed. Length into Substructure (Top pile portion):** This value represents embedment length of pile into the substructure it is connected to. This value affects only 3D model and generated CADD drawings.

**Pile Group Longitudinal Offset:** Shifts the entire pile layout in the longitudinal direction (along the station). The offset is applied uniformly to all piles and is added to the footing's own offset. Positive values shift the layout up station.

**Pile Group Transverse Offset:** Shifts the entire pile layout in the transverse direction. The offset is applied uniformly to all piles and is added to the footing's own offset. A positive value shifts the layout to the right when looking up-station along the PGL.

### Design Settings

**Pile Capacity:** This value represents the compression capacity, and the axial force in the pile will be evaluated in comparison to it.

**Pile Category \[Drilled Shaft/Driven Pile/Micropile]:** Classifies the piles in the layout for design-code resistance calculations. Pile Interaction code checks use this category (or an override) to select the appropriate AASHTO axial-resistance formulation.

### FEA

{% hint style="info" %}
Depth of Fixity Method: To model pile behavior **linearly** for pile foundations where **soil-structure interaction is not a governing factor**, the depth of fixity method can be used for simplified analysis. The effective length of the pile should be identified. This effective length represents the depth of fixity where the pile's bottom node is located with a fully fixed support. Depending on the goal of the analysis, the depth of fixity can be selected to either provide the correct peak pile moments or correct substructure stiffness. These options are beneficial for designing the piles and generating the correct force effects in the rest of the bridge structure, respectively. The pile FEA model is created as beam-columns with no support provided along the length. In OpenBrIM, this is achieved by selecting the **Soil Spring Type** as **Linear or Nonlinear Spring**. Then, the engineer needs to identify the node locations and set all of them free except for the bottom one.
{% endhint %}

**Soil Spring Type\[Linear or Nonlinear Spring/ Nonlinear Spring from the Soil Set]:** This property allows the user to define the types of springs that are desired to be employed between the soil and the pile. For more details please refer to the [Soil Structure Interaction](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/substructure-sig/soil-structure-interaction-sig) page.

**Soil Springs (Linear/Nonlinear):** If the **Soil Spring Type** is selected as **Linear or Nonlinear Spring**, this tab should be activated. Then the user can define the soil characteristics per depth using fixities, linear stiffness values, or nonlinear springs: right-click a stiffness cell and choose **Edit Stiffness** to set Free, Fixed, a linear Stiffness, Compression Only, Tension Only, or a Nonlinear Curve (force–displacement points).

* **Offset from the bottom of the footing/bent:** The offset from the bottom of the footing or bent parameter is used to determine the location of springs representing soil properties. For each row, the total distance to the top position should be entered. A node will be introduced at each location, and this length can also serve as a means to modify the pile's mesh.
* **Tx\[Fixed/Free/Stiffness Value]:** Translational stiffness along the longitudinal direction of the alignment. A nonzero or fixed value is generally employed to represent lateral soil resistance.
* **Ty\[Fixed/Free/Stiffness Value]:** Translational stiffness along the transverse direction of the alignment. A nonzero or fixed value is generally employed to represent lateral soil resistance.
* **Tz\[Fixed/Free/Stiffness Value]:** Translational vertical stiffness is employed to define axial soil resistance. A nonzero stiffness value or fixed is commonly applied at the bottom of the pile to represent the soil's tip resistance. If the user wishes to disregard soil side friction, a free condition can be applied at other locations; alternatively, if side friction should be considered, a nonzero stiffness value can be used.
* **Rx\[Fixed/Free/Stiffness Value]:** Rotational torsional stiffness is employed to define torsional soil resistance.
* **Ry\[Fixed/Free/Stiffness Value]:** Usually set to free, but users may input small values to address stability concerns in finite element analysis
* **Rz\[Fixed/Free/Stiffness Value]:** Usually set to free, but users may input small values to address stability concerns in finite element analysis

If the **Soil Spring Type** is selected as **Nonlinear Spring from the Soil Set,** OpenBrIM library will assign the appropriate spring properties to the pile. To generate these springs, following inputs are necessary, **Section Type**, **Soil Springs from the Soil Set (Nonlinear)**, and **Mesh Size**.

**Section Type\[Circular, Rectangular, H-Shaped]:** Specify the type of the section. This input will affect the effective diameter calculations that are needed by soil material models, unless the section is circular.

**Soil Springs from the Soil Set (Nonlinear):** Assign the Soil Set. Soil Sets are defined under the Soil Structure Interaction tab. For more information, please refer to the [Soil Set](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/substructure-sig/soil-structure-interaction-sig/soil-set-sig) page.

**Mesh Size:** Specify the length of the finite elements of the pile.

**Top Connection\[Fixed/Pinned]:** Use this parameter to specify the connection type between pile and cap/bent.

**Generate FEM? \[Yes/No]:** Setting the "Generate FEM" parameter to "No" can disable the analytical representation of the pile.

**# of Result Extraction St.:** The result extraction segment settings are solely for viewing FEA composite results in either the spreadsheet or FEA view, and do not impact standard finite element analysis results like member end forces, node displacement, and node reactions.

### FEA - Group Effect

The effects of group interaction can be evaluated in OpenBrIM. P-Multiplier values should be assigned according to lead and trail row in X (Along Station) and Y (Transverse Direction).

**Assign P-Multipliers\[All Equal to 1/Custom]:** By default, all P-Multipliers are set to 1. If the engineer needs to assign specific values, the **Custom** option must be selected.

**P-Multipliers for Each Row Lead to Trail X (Along Station):** Specify the P-Multiplier values in the X direction for each row from the leading row to the trail row. This list must include values for every row in the X direction.

**P-Multipliers for Each Row Lead to Trail Y (Transverse Direction):** Specify the P-Multiplier values in the Y direction for each row from the leading row to the trail row. This list must include values for every row in the Y direction.

**Axial Factor (Skin):** Multiplier on the skin friction (t-z) springs: it scales the resistance of every t-z curve along each pile. Default 1.0; values below 1.0 model reduced friction due to pile-group overlap. Shown only when Soil Spring Type is Nonlinear Spring from the Soil Set.

{% hint style="info" %}
Note that pile contributions depend on the row position, and Lead and Trail row definitions vary based on the loading direction. Therefore, determining the correct row positions according to pile movement is essential. OpenBrIM.FEA can dynamically assign the appropriate P-Multiplier during the analysis. This is determined for each pile based on the displacement of the pile head.
{% endhint %}

![image-20250121-075637.png](https://openbrim.atlassian.net/wiki/download/attachments/2541748245/image-20250121-075637.png?api=v2)

### Quantities

The rows marked (Single) are the values of one pile of the layout; the rows marked (Total) are those values times the Pile Count, since every pile of a layout has the same sections and length. Lengths and volumes include the length embedded in the substructure, which the footing's own volume does not subtract.

**Bottom Surface Area(Single):** Area of the bottom face of a single pile. (Read-only)

**Top Surface Area(Single):** Area of the top face of a single pile in the group. (Read-only)

**Side Surface Area(Single):** Lateral (side) surface area of a single pile. (Read-only)

**Top Surface Perimeter(Single):** Perimeter of the top face of a single pile. (Read-only)

**Bottom Surface Perimeter(Single):** Perimeter of the bottom face of a single pile. (Read-only)

**Height:** The length of a single pile. (Read-only)

**Max Width:** The largest section width along a single pile. (Read-only)

**Rebar Density(per cubic yard):** Rebar density used to compute the rebar weight of each pile. Enter the expected weight of reinforcement per cubic yard. Shown only when the pile's material is not steel.

**Rebar Weight(Single):** The rebar weight of one pile: its volume times the Rebar Density. Shown only when the pile's material is not steel. (Read-only; may be slow on recompute)

**Volume(Single):** Volume of a single pile. (Read-only)

**Weight(Single):** The weight of one pile, each segment weighed with its own section's material, so a pile of several materials weighs right. (Read-only; may be slow on recompute)

**Material:** The material of the pile's top section. (Read-only)

**Pile Count:** The number of piles in the layout: the grid's piles in X times those in Y for a Grid layout, or the number of rows for a Custom layout. (Read-only; may be slow on recompute)

**Pile Length(Total):** Height times Pile Count. (Read-only; may be slow on recompute)

**Volume(Total):** Volume(Single) times Pile Count. (Read-only; may be slow on recompute)

**Weight(Total):** Weight(Single) times Pile Count. (Read-only; may be slow on recompute)

**Rebar Weight(Total):** Rebar Weight(Single) times Pile Count; shown only when the pile's material is not steel. (Read-only; may be slow on recompute)

**Pile Category (Design Settings):** The pile kind the layout is priced by, read from the Pile Category input (Drilled Shaft, Driven Pile or Micropile) that design reads. (Read-only)

**Pile Section:** The name of the piles' top section, the first row of Pile Length/Section. (Read-only)

**Battered Piles:** The number of battered piles: the Pile Count when either batter angle is not zero, otherwise 0. The batter is the layout's, so every pile is battered or none is. (Read-only; may be slow on recompute)

On the IFC export, each pile of a layout carries the layout's Quantities, so there these rows are the layout's totals, not the pile's.


---

# 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/concrete-u-girder-bridge-workflow/substructure-cug/pile-cug/pile-layout-cug.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.
