> 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-u-girder-bridge-workflow/substructure-cug/pier-cug/steel-i-girder-bent-cap-cug/plate-cug.md).

# Plate \[CUG]

The Plate object serves as a connection element between the Steel I-Girder Bent Cap and the superstructure. Both the FEM and 3D models are generated based on the parameter definitions listed below.

## Plate

**Girders:** Specify the girders to define the location of the Plate object.

**Location \[Top/Bottom]:** The plate can be generated at either the top or bottom of the chosen girders. This parameter specifies the exact location of the plates.

**Station on Girders (from Right End):** This parameter allows you to adjust the location of the plate according to the bridge's transverse direction.

**Thickness:** For visual representation, refer to the figure below.

**Width of the Plate:** For visual representation, refer to the figure below.

**Material:** Assign a material to the plate. Materials can be selected from previously defined options or imported as needed

![image-20240913-143001.png](https://openbrim.atlassian.net/wiki/download/attachments/2575400996/image-20240913-143001.png?api=v2)

![image-20240913-141906.png](https://openbrim.atlassian.net/wiki/download/attachments/2575400996/image-20240913-141906.png?api=v2)


---

# 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-u-girder-bridge-workflow/substructure-cug/pier-cug/steel-i-girder-bent-cap-cug/plate-cug.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.