> 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/general/asce-seismic-wall-anchorage-2.md). # ASCE 7-22 Seismic Wall Anchorage How to compute out-of-plane wall design forces and wall anchorage forces per ASCE 7-22 Section 12.11. This module calculates the seismic out-of-plane forces on structural walls and the anchorage forces required to connect walls to the roof or floor diaphragm, in accordance with ASCE 7-22 Section 12.11. Input parameters are taken directly from the nomenclature presented in ASCE 7. Two results are produced: 1. **Out-of-Plane Force for Structural Wall Design:** The distributed force (psf) used to design the wall itself for out-of-plane bending (ASCE 7-22 Section 12.11.1) 2. **Out-of-Plane Wall Anchorage Force:** The total anchorage force (lbs) at a single anchor point connecting the wall to the diaphragm (ASCE 7-22 Section 12.11.2) ![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-972e1befa79136d8ebd6f448b7bd689f1d7afc96%2FASCE%207-22%20Seismic%20Wall%20Anchorage.png?alt=media) **Sds:** Design spectral response acceleration at short periods. **Ie : Importance Factor:** Seismic importance factor, based on Risk Category. **Wp : Wall Weight:** Weight of the wall per unit area. **Wall Height:** Total height of the wall above and below the anchor level. Half of this value is used to compute tributary height. **Parapet Height:** Height of parapet above this level, if applicable. Added to half the wall height to get tributary height. **Horizontal spacing between anchors:** Center-to-center distance between wall anchors along the wall length. **Tributary Height:** Total height tributary to the anchor, taken as Wall Height / 2 + Parapet Height **A\_trib:** Total wall area tributary per anchor is, taken as Tributary Height \* Horizontal spacing between anchors ## Out-of-Plane Force for Structural Wall Design (12.11.1) Determines the minimum distributed force (psf) for wall panel design. Applies to all Seismic Design Categories. The force is the greater of: * **Fp =** 0.4 \* Sds \* Ie \* Wp * **Fp,min =** 0.10 \* Wp ## Out-of-Plane Wall Anchorage Force (12.11.2) Calculates the total anchorage force (lbs) at a single anchor connecting the wall to the diaphragm. **h : Height of the roof above base:** The height of the roof above the base of the building. **z : Height of the anchor above the base:** The height of the anchor above the base. For a roof-level anchor, z = h. **Lf : Span of flexible diaphragm:** Span of the flexible diaphragm providing lateral support. Enter zero for a rigid diaphragm. **Connection is not at a flexible diaphragm:** Check this box when the anchorage is not at a flexible diaphragm level. This affects the height adjustment factor and the upper limit on Ka. **Anchorage Height Adjustment Factor:** When the connection is not at a flexible diaphragm, the force is multiplied by a factor of (1 + 2z/h) / 3. When the connection is at a flexible diaphragm, the adjustment factor is 1.0. **Ka:** Amplification factor for diaphragm flexibility, taken as Ka = 1.0 + Lf / 100, but not less than 1.0 and not greater than 2.0. If the connection is not at a flexible diaphragm, Ka = 1.0 The anchorage force is the greater of: * Fp = 0.4 \* Sds \* Ka \* Ie \* Wp \* A\_trib \* \[Anchorage Height Adjustment Factor (if applicable)] * Fp,min = MAX( 0.2 \* Ka \* Ie \* Wp , 5 psf ) \* A\_trib --- # 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/general/asce-seismic-wall-anchorage-2.md?ask=&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.