> 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/concrete-box-girder-bridge-workflow/cadd-cbg/abutment-plan-cadd-cbg.md).

# Abutment Plan CADD \[CBG]

The Abutment Plan CADD workflow item generates a CAD plan drawing of a selected abutment, including the abutment footprint, footing, piles, dimension lines, and bearings when enabled. The drawing respects the abutment skew and transverse offset relative to the alignment and can be exported to DGN/DWG.

## General

**Abutment:** Pick the abutment to be drawn in plan. The abutment alignment, station, skew, and orientation are pulled from this object.

## Settings

**Show Bearing \[No/Yes]:** When Yes, the bearings seated on the selected abutment are included in the abutment plan drawing. When No, bearings are omitted.

**Start/end PGL #ft from before/after bridge \[Use Alignment Start and End Station]:** Distance in front of and behind the abutment at which the plotted PGL segment starts/ends (default 240). Use -1 to plot the full alignment start/end stations rather than a fixed offset.

**Front Wall Dimension Line Direction \[Along Supportline/Perpendicular to the pgl]:** Choose whether the front-wall dimension line in the abutment plan is drawn along the support line (0) or perpendicular to the profile grade line (1, default). Select Perpendicular to the pgl when a dimension aligned with the roadway is preferred over one aligned with the skewed support.


---

# 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/concrete-box-girder-bridge-workflow/cadd-cbg/abutment-plan-cadd-cbg.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.