> 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-faq/using-the-software/calculation-modules/retaining-walls/segmental-retaining-walls/factors-of-safety-in-geogrid-d.md).

# Factors of Safety in Geogrid Design

How the Segmental Retaining Wall module handles factors of safety in geogrid connection and reinforcement design.

## How does the program handle the calculation of Factors of Safety in Geogrid Design?

First, it calculates a "Peak Connection Value" and divides it by the factor of safety to reduce it to what we might think of as an allowable value, or something that should be compared on par with the applied load.

Second, it calculates a "Service Level Connection Value", which is already an allowable value, or something that should be compared on par with the applied load.

Third, it determines the LTDAS = LTDS divided by the factor of safety. This is now an allowable value, or something that should be compared on par with the applied load.

It then finds the least of these three capacity values.

Finally the tabular value of "S.F." in the Wall Analysis Table is calculated at each reinforcing layer by dividing the lowest of the three capacity values by the sum of static and seismic tensions. Since the capacities have all been normalized by the appropriate factor of safety, the designer is looking for a value of 1.0 or greater in the "S.F." column.


---

# 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-faq/using-the-software/calculation-modules/retaining-walls/segmental-retaining-walls/factors-of-safety-in-geogrid-d.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.
