> 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-7-10-16-wind-forces-chapt.md). # ASCE 7-10/16 Wind Forces Chapter 28 and 30 How to compute ASCE 7-10 and 7-16 Chapter 28 and 30 wind forces for MWFRS and components and cladding. This module is a presentation of the Wind Forces provisions of Chapter 28, Part 2 and Chapter 30, Part 2 of ASCE 7-10 and ASCE 7-16. Limited documentation is provided here, because all of the references to ASCE 7 are given on the module screens. ## **General** The General tab provides an input field for a general description of the project and/or the wind calculations that are being performed. ## **Applicability Checklists** The Applicability Checklists tab provides a quick listing of the requirements in order to be able to apply Chapter 28, Part 2 (MWFRS) and Chapter 30, Part 2 (Components & Cladding). ## **Analysis Values** The Analysis Values tab collects the input (on the top of the screen) and displays the results (on the bottom of the screen). --- # 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-7-10-16-wind-forces-chapt.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.