> 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/truss-bridge-workflow/reports-tb.md).

# Reports \[TB]

Generates project-level reports for the truss bridge. Static Pushover Graph compares the pushover capacity of the substructure with the response spectrum demand. Elastomeric Bearing Stiffness reports the stiffness calculations of the steel-reinforced elastomeric bearings. Center of Gravity reports the center of gravity, weight and mass moments of inertia of selected bridge objects. Project Inputs collects the project's inputs into one report. Quantity Takeoff Report prices the quantities defined by the items under Pay Item Table, such as truss member weight or deck concrete volume, and groups the cost by category. The Steel Bent Cap Camber Diagram produces a camber report for steel bent caps supporting the truss. Defined reports can be accessed through the DOCS button in the left-hand sidebar of the application.


---

# 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://docs.openbrim.org/templates/truss-bridge-workflow/reports-tb.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.
