> 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/cable-stayed-bridge-workflow/cadd-csb/abutment-plan-cadd-csb.md).

# Abutment Plan CADD \[CSB]

The Abutment Plan CADD workflow item generates a 2D plan drawing of a selected abutment, including the abutment wall, wing walls, footing, bearings, and associated dimensions. The drawing is exported to the CADD container for visualization and further processing.

## General

**Abutment:** Select the abutment for which the plan drawing will be generated.

## Settings

**Show Bearing \[NO/YES]:** Toggle the display of bearings on the abutment plan drawing.

**Start/end PGL #ft from before/after bridge \[Use Alignment Start and End Station]:** Specify the distance before and after the support line station to include in the plan. Selecting "Use Alignment Start and End Station" will use the full alignment extents.

**Front Wall Dimension Line Direction \[Along Supportline/Perpendicular to the pgl]:** Specify the direction of the front wall dimension line. "Along Supportline" orients the dimension along the support line, while "Perpendicular to the pgl" orients it perpendicular to the Proposed Grade Line.


---

# 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/cable-stayed-bridge-workflow/cadd-csb/abutment-plan-cadd-csb.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.