> 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/sw-segmental-walls/loads-tab.md).

# Loads Tab

How to enter dead and live load surcharges and seismic parameters for a segmental retaining wall.

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

**Surcharge DL, psf**: Enter the dead load surcharge.

**Surcharge LL, psf**: Enter the live load surcharge – it will not be used to resist overturning or sliding.

**Seismic A factor**: Specified horizontal peak ground acceleration expressed as a fraction of the gravitational constant, g. The site-specific values of A represent a 90% probability of that value not being exceeded in 50 years. See NCMA 3rd Edition, Section 9.4.

**d\*\*\*\*seismic**: The lateral deflection that the retaining wall can withstand during a seismic event, in units of inches. See NCMA 3rd Edition, Section 9.4. Note that this input is optional. If a non-zero value is entered, the program will apply the formulas that consider the maximum permissible deformation. If the value is left zero (blank), the program will apply the formulas that are independent of the deformation.


---

# 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/sw-segmental-walls/loads-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.
