> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/precast-concrete/introduction.md).
# Introduction
Precast Concrete plugin for Revit helps you overcome the limitations of working in plain Revit when it comes to modeling precast projects and generating shop drawings for manufacturers.
The plugin lets you avoid manual modeling and repetitive, mind-numbing (not to mention error-inducing) drafting tasks. That way, you can focus on high-value tasks while Precast Concrete does the rest for you.
Our Precast Concrete design software for Autodesk Revit enables you to easily model prefabricated concrete walls, floor slabs, columns, and beams; batch-insert connection details (lifting anchors, bolts, cuts, couplers, corbels, etc.); place rebar in wall panels (solid, double, and sandwich) and beams (rectangular, L, and IT); and quickly generate shop tickets with proper element views, dimensions, and bills of materials.
Since it runs on Revit, you get full project updates in real time. All that ensures quality production and accurate assembly on site.
---
# 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.besmart.software/3d-modeling-and-design/precast-concrete/introduction.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.
