> 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/e3d-user-manual/model-entities/toc175916832/toc161394046.md).

# Surface Springs

How to assign surface springs to shells for modeling flexible restraints and Winkler mat foundations.

Springs are flexible restraints. Springs applied to shells are referred to as surface springs. You may assign a surface spring to a shell with one or more global DOFs (Dx, Dy and Dz) restrained. To qualify as a valid flexible restraint, the corresponding spring constant must be specified. A restraint may be designated as linear, compression-only or tension-only. A compression-only restraint is active only when the nodal displacement in the restrained direction is negative. A tension-only restraint is active only when the nodal displacement in the restrained direction is positive. If a model contains one or more compression-only or tension-only springs, the whole problem becomes nonlinear and the solution becomes iterative for each load combination.

The forces or moments required to enforce flexible restraints are called spring reactions. They are computed by the program. Surface springs may be used to model Winkler mat foundations. It may be worthwhile to note that in modeling a mat foundation, surface spring constants are the soil subgrade moduli while surface spring reactions are the soil pressures.


---

# 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/e3d-user-manual/model-entities/toc175916832/toc161394046.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.
