> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-user-manual/calculation-modules/earth-retention/soldier-pile-2/general-tab.md).

# General Tab

How to set up soldier pile section, retained height, tie-backs, embedment, and bracing on the General tab.

![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-7ee5e151b130bb7357778532c4d16410da7c2776%2FClip67.jpg?alt=media)

**Steel Design Method:** Select ASD or LRFD methods for design of steel pile

**Pile Section:** Opens the Steel Section Database, allowing the selection of common pile sections.

**Retained Height, ft:** Distance between the final excavated grade and the retained height at the top grade.

**Tie Usage:** Select none, one, two, or three. If any tie-backs are used, they are located by their distance from the top of the pile.

**Bottom of pile is assumed to be:** This is a conditional input. It is only available when tie-backs **are** used, which triggers a stiffness analysis using ENERCALC SEL's 2D Frame program in the background. The pile is modeled in segments from spanning between tie-backs. The bottom segment spans from the lowest tie-back to the bottom of the embedment depth. This setting controls whether that lowest support is considered fixed or pinned with regard to rotation.

**Pile Spacing, ft:** Center to center spacing of piles, typically 6 ft to 10 ft.

**Pile is encased in concrete:** Select whether the steel pile is driven into the soil or placed into a drilled hole and encased in lean concrete.

**Pile Flange Width / Diameter of Encasement, in:** If the pile is driven, enter the flange width. If the pile is set in lean concrete in a drilled hole, enter the hole diameter.

**Total Pile Embedment, ft:** Actual embedment, usually rounded from the required embedment reported below.

**Multiplier to Passive Wedge:** This is an arching factor. It takes the form of a multiplier from 1.0 to 3.0 to be applied to the pile flange width or drilled hole diameter due to wedging action and is usually provided by the geotechnical engineer.

**Pile Yield Stress, Fy:** Yield stress of the selected pile section.

**Unbraced Length for Soldier Pile:** Allows the user to specify the unbraced length for steel design purposes. This is a conditional input.

**If the pile is** **not** **tied back, the user can select:**

* Consider pile unbraced for lateral torsional buckling
* Consider pile fully-braced for lateral torsional buckling

**If the pile** **is** **tied back, the user can select:**

* Consider pile unbraced for lateral torsional buckling
* Consider pile to be braced at tieback locations
* Consider pile fully-braced for lateral torsional buckling


---

# 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://enercalc.com/docs/sel-user-manual/calculation-modules/earth-retention/soldier-pile-2/general-tab.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.
