> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/combinations-stg.md). # Combinations \[STG] To effectively conduct the design of bridge structures, it is essential to establish several key definitions related to limit states and loads. These definitions are critical for ensuring that the design meets safety and performance criteria. Crucial definitions include non-composite dead loads, which represent the weight of structural elements that do not contribute to the composite action of the bridge, and composite dead loads, which account for the combined weight of structural elements that act together to enhance the overall load-bearing capacity. Additionally, wearing surface loads pertain to the surface finish of the bridge deck, influencing both dead load and live load calculations and several more. Given that various construction stages may involve specific loads associated with these definitions, it is necessary to integrate these stages into the design process. This involves analyzing the interactions between different loads during each construction phase and utilizing this section of the workflow to systematically combine loads from different stages. By clearly defining these load categories and effectively combining them, engineers can perform comprehensive design evaluations that adhere to limit state criteria, ensuring the safety and performance of the bridge throughout its lifespan. This section can be used for this purpose. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/combinations-stg.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.