> 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/substructure-csb/abutment-system-csb/integral-abutment-csb.md).

# Integral Abutment \[CSB]

## Integral Abutment

The Integral Abutment workflow item models a monolithic abutment in which the superstructure is rigidly connected to the abutment (no bearings). It supports both 3D visualization and optional finite-element meshing of the abutment, wing walls, and footing. Abutments can be positioned on any support line and referenced by approach slabs, piles, and stems.

### General

**Location:** Support line on which the abutment is located. A single support line must be picked.

**Front/Back \[Front/Back]:** Orientation of the abutment. Front (0) places the back wall facing upstation; Back (1) reverses that orientation so the back wall faces downstation. Choose the value that matches the bridge geometry at the picked support line.

**Longitudinal Offset:** Offset of the abutment centerline along the PGL. Negative values shift the abutment downstation; positive values shift it upstation.

**Transverse Offset:** Offset of the abutment centerline perpendicular to the PGL. Default matches the deck offset. Positive values place the abutment to the right of PGL when looking upstation; negative values place it to the left.

**Material:** Concrete material assigned to the abutment stem, seat, back wall, and wing walls. Pick a previously defined material from *Properties > Materials*.

### Stem

**Width (Perpendicular to pgl):** Width of the abutment stem in the transverse direction. Only required when Geometry Source is set to Parameters.

**Length:** Length of the abutment seat in the longitudinal direction (default 36 in).

**Override Top Elevation \[No/Yes]:** When Yes, the seat top elevation is taken from the user-specified table below instead of the auto-computed PGL-based value. Only visible when Geometry Source is Section and a section point is defined.

**Stem Top Elevation:** Table defining the top elevation of the stem across the abutment, row by row from the right end when looking upstation (Length, Elevation, Geometry Option \[Flat/Sloped], Elevation 1). Used when the top elevation is overridden or when the stem geometry is driven by parameters; the cell menu can fill it from the deck or the bearing elevations.

**Override Bottom Elevation \[No/Yes]:** When Yes, the seat bottom elevation is taken from the user table instead of the default derived from the seat length.

**Stem Bottom Elevation:** Table defining the bottom elevation of the stem, in the same form as Stem Top Elevation. Used when the bottom elevation is overridden or when the stem geometry is driven by parameters.

**Bottom Elevation:** (Read-only) Computed bottom elevation of the front wall, shown for reference.

**Left Plane Rotation:** In-plan rotation of the left face of the seat wall. Only enabled when the seat is on a curved/skewed support configuration.

**Right Plane Rotation:** In-plan rotation of the right face of the seat wall. Same usage as Left Plane Rotation.

**Geometry Source \[Parameters/Section]:** Selects how the seat cross-section is defined. Parameters (0) uses the Width and Length values above. Section (1) uses the picked Section below.

**Section:** Section library object used when Geometry Source is Section. The section must expose a `_seatSection` parameter set.

### Right Wing Wall

**Wing Wall \[No/Yes]:** Enables or disables the right-hand wing wall. When No, the remaining right-wall parameters are hidden.

**Section:** Section defining the right wing wall cross-section. The section must expose a `_wingwallSection` parameter set.

**Wall Length:** Length of the wing wall along its own axis (default 360 in).

**Longitudinal Offset:** Offset of the wing wall start from the abutment along the PGL direction.

**Transverse Offset:** Offset of the wing wall start transverse to the PGL.

**Angle of Start Face Plane:** Skew of the start face of the wing wall.

**Angle of End Face Plane:** Skew of the end face of the wing wall.

**Rotation Angle:** Rotation of the wing wall in plan around its start point.

**Override Bottom Elevation \[No/Yes]:** When Yes, the wing-wall bottom elevation is taken from the input below instead of the default computed elevation.

**Bottom Elevation:** User-specified bottom elevation of the right wing wall when override is enabled.

**Top Vertical Offset:** Vertical offset of the top of the wing wall from the PGL-derived top elevation.

**Bottom Elevation (readonly):** (Read-only) Auto-computed bottom elevation of the right wing wall shown for reference.

### Left Wing Wall

Parameters mirror the Right Wing Wall group and control the left-hand wing wall:

**Wing Wall \[No/Yes]:** Enables the left wing wall.

**Section:** Section definition for the left wing wall.

**Wall Length:** Length along the wing-wall axis.

**Longitudinal Offset:** Offset from the abutment along the PGL.

**Transverse Offset:** Offset transverse to the PGL.

**Angle of Start Face Plane:** Skew of the start face.

**Angle of End Face Plane:** Skew of the end face.

**Rotation Angle:** In-plan rotation.

**Override Bottom Elevation \[No/Yes]:** Toggle for user-input bottom elevation.

**Bottom Elevation:** User-specified bottom elevation when override is enabled.

**Top Vertical Offset:** Vertical offset of the wall top from the PGL-derived top elevation.

**Bottom Elevation (readonly):** (Read-only) Auto-computed bottom elevation of the left wing wall shown for reference.

### 3D Visualization

**Right Chamfer \[No/Yes]:** Enables a chamfer on the right end of the seat/back-wall interface. When No, the remaining right-chamfer parameters are hidden.

**Right Chamfer Width:** Chamfer width in the transverse direction.

**Right Chamfer Length:** Chamfer length in the longitudinal direction.

**Right Chamfer Depth:** Chamfer depth in the vertical direction.

**Right Chamfer Vertical Offset:** Vertical offset of the chamfer from the top of the abutment.

**Right Chamfer Transverse Offset:** Transverse offset of the chamfer from the wing-wall interior face.

**Left Chamfer \[No/Yes]:** Enables a chamfer on the left end of the seat/back-wall interface.

**Left Chamfer Width:** Chamfer width in the transverse direction.

**Left Chamfer Length:** Chamfer length in the longitudinal direction.

**Left Chamfer Depth:** Chamfer depth in the vertical direction.

**Left Chamfer Vertical Offset:** Vertical offset of the chamfer from the top of the abutment.

**Left Chamfer Transverse Offset:** Transverse offset of the chamfer from the wing-wall interior face.

### FEM

**Generate FEM \[No/Yes]:** When Yes (default), a shell-element FE mesh is generated for the abutment and wing walls. When No, only the 3D visualization is produced.

**Mesh Size:** Target element size used when meshing the abutment surfaces (default 120 in).

**Rigid Material:** Rigid material used for stiff FE link elements inside the abutment mesh (picks a Material library object).

**Rigid Section:** Rigid section used for the same FE link elements (picks a Section library object).

**Mesh Algorithm \[GridMesh/MeshAdapt/Automatic/Initial mesh only/Delaunay/Frontal Delaunay/Frontal Delaunay for Quads/Packing of Parallelograms/Quasi structured Quad]:** Meshing algorithm applied to the abutment and wing-wall surfaces. The default is MeshAdapt.

**Override Right Wing Wall Thickness \[No/Yes]:** When Yes, the right wing wall thickness used by FEM is taken from the input below instead of the section's minimum width.

**Override Left Wing Wall Thickness \[No/Yes]:** When Yes, the left wing wall thickness used by FEM is taken from the input below instead of the section's minimum width.

**Right Wing Wall Thickness:** User-specified FE thickness for the right wing wall. Only enabled when the corresponding override is Yes.

**Left Wing Wall Thickness:** User-specified FE thickness for the left wing wall. Only enabled when the corresponding override is Yes.

**Match Top Elevation with Deck \[No/Yes]:** Affects the analysis model only. When Yes, the top edge of the wall mesh is placed at the deck mid-surface: at each end of the wall, the roadway surface elevation (profile plus cross slope) less half the deck thickness, with a straight top edge between the two ends. The mesh then meets the deck regardless of what the top elevation table says, while the 3D solid keeps the authored top. The wing walls, bearing seats, construction joint and footing keep their own elevations. Default No.

**Girders:** The girders framing into the wall. For each picked girder, its support on this abutment's support line (the bearing top where there is a bearing, otherwise the girder's reference node) is projected along the PGL onto the wall, and the wall mesh gets a node exactly there. Where the girder point does not coincide with that node, a rigid link using the Rigid Section joins them. Leave empty to add no girder nodes.

**Cross Frames:** The cross frames at this abutment, typically the end cross frames embedded in the wall. The wall mesh gets nodes where the middle nodes of each picked cross frame land, joined to them by rigid links where they do not coincide; the cross frame nodes at the girders are covered by Girders. Leave empty to add no cross frame nodes.

**Decks:** The decks meeting the wall. The end of each deck mesh line nearest the abutment is projected along the PGL onto the wall, the wall mesh gets a node there, and a rigid link joins the two where they do not coincide. Leave empty to add no deck nodes.

### Bottom Fixity

These inputs set how the bottom of the abutment is supported in the analysis model. They are shown when Generate FEM is Yes.

**Bottom Connection \[Substructure/Stiffness Matrix/Fixed/Custom DOF]:** How the bottom edge of the abutment mesh is supported.

* **Substructure** (default): the bottom of the wall is tied by rigid links to the piles or pile layout that reference the abutment, and those piles generate their own analysis model below it.
* **Stiffness Matrix:** the pile links are removed. Every node of the bottom edge is tied by a rigid link to one support node at the middle of the bottom edge, and that node is supported to ground by the 6x6 Stiffness Matrix.
* **Fixed:** the same single support node, built in on all six degrees of freedom.
* **Custom DOF:** the same single support node, with each degree of freedom set on its own by Tx to Rz below.

With any option other than Substructure, piles and pile layouts that reference the abutment no longer generate their own analysis model, so the single support node is the only load path to the ground.

**6x6 Stiffness Matrix:** The foundation stiffness of the single support node when Bottom Connection is Stiffness Matrix: a 6x6 matrix coupling the three translations and the three rotations. Enter it with **6x6 Stiffness Matrix...** from the cell menu; the editor stores the upper triangle and the analysis mirrors it, so the matrix is always symmetric. It acts in the bottom fixity frame (see Bottom Fixity UCS Rotation). Shown only when Bottom Connection is Stiffness Matrix.

**Tx \[Free/Fixed]:** Restraint of the single support node in translation along its local X axis when Bottom Connection is Custom DOF: Fixed (-1), Free (0), or a positive value for a spring stiffness to ground in that direction, entered with **Edit Stiffness (Tx)...** from the cell menu. Default Fixed.

**Ty \[Free/Fixed]:** As Tx, for translation along the local Y axis.

**Tz \[Free/Fixed]:** As Tx, for translation along the local Z (vertical) axis.

**Rx \[Free/Fixed]:** As Tx, for rotation about the local X axis; a positive value is a rotational spring stiffness.

**Ry \[Free/Fixed]:** As Rx, for rotation about the local Y axis.

**Rz \[Free/Fixed]:** As Rx, for rotation about the local Z axis.

All six default to Fixed, so switching to Custom DOF starts from the same support as Fixed; release or soften one direction at a time from there.

**Bottom Fixity UCS Rotation:** Rotation, about the vertical axis, of the frame in which the single support node reads Tx to Rz and the 6x6 Stiffness Matrix. At the default 0 the frame is the abutment's own: local X perpendicular to the (skewed) wall, Y along the wall, Z up. A non-zero value turns the restraint axes, counterclockwise positive, for example to line them up with a pile group or a bearing layout that does not follow the wall. Shown when Bottom Connection is Stiffness Matrix, Fixed or Custom DOF.

### Construction Joint

A construction joint splits the abutment wall into two pours. The mesh gets nodes along the joint line, and the abutment's analysis elements are divided into the part below and the part above the joint, so that an **Abutment Construction** item can place each part in its own stage with its **Portion** input (Full, Below Joint, Above Joint). The 3D model and the quantities are split the same way.

**Construction Joint \[No/Yes]:** Adds a construction joint across the wall. Default No.

**Joint Elevation:** The elevation of the joint, as a table in the same form as Stem Top Elevation (Length, Elevation, Geometry Option \[Flat/Sloped], Elevation 1), with the first row starting at the right end of the wall when looking upstation. Rows can step or slope, so the joint can follow the wall profile. Every row must lie above the wall bottom and below the wall top (the read-only elevations below). Shown when Construction Joint is Yes.

**Wing Wall Joint \[No/Yes]:** With the construction joint on, the wing walls are split at the joint elevation at each end of the wall. Set this to Yes to give the wing walls their own joint elevation instead. Shown when Construction Joint is Yes. Default No.

**Wing Wall Joint Elevation:** The wing wall joint elevation, in the same table form: the first row sets the right wing wall and the last row the left wing wall. When left empty, the wing walls follow the main joint. Shown when Construction Joint and Wing Wall Joint are both Yes.

**Wall Bottom Elevation (readonly):** The bottom elevation of the abutment wall (the Bottom Elevation shown under Stem). Joint rows must lie above it. (Read-only)

**Wall Top Elevation (readonly):** The roadway surface elevation on the alignment at the abutment station. Joint rows must lie below it. (Read-only)

**Bearing Seat Top Elevation (readonly):** The highest bearing seat top elevation, computed from the bearings on the abutment's support line (the wall bottom when there are none), shown for reference. It is not a limit: the joint may sit below the bearing seats, as it does when the first pour stops under them. (Read-only)

### Quantities

All values in this group are derived from the generated geometry and are displayed for reference; they cannot be edited.

**Total Top Face Area:** (Read-only) Combined top-face area of the seat, back wall, and wing walls.

**Total Bottom Face Area:** (Read-only) Combined bottom-face area of the seat, back wall, and wing walls.

**Total Surface Area:** (Read-only) Total exterior surface area of the abutment.

**Max Height Left Wing Wall:** (Read-only) Maximum height of the left wing wall.

**Min Height Left Wing Wall:** (Read-only) Minimum height of the left wing wall.

**Length Left Wing Wall:** (Read-only) Length of the left wing wall.

**Thickness Left Wing Wall:** (Read-only) Thickness of the left wing wall.

**Max Height Right Wing Wall:** (Read-only) Maximum height of the right wing wall.

**Min Height Right Wing Wall:** (Read-only) Minimum height of the right wing wall.

**Length Right Wing Wall:** (Read-only) Length of the right wing wall.

**Thickness Right Wing Wall:** (Read-only) Thickness of the right wing wall.

**Seat Max Depth:** (Read-only) Maximum vertical depth of the seat.

**Seat Min Depth:** (Read-only) Minimum vertical depth of the seat.

**Seat Thickness:** (Read-only) Longitudinal thickness of the seat.

**Seat Width:** (Read-only) Transverse width of the seat.

**Volume:** (Read-only) Total concrete volume of the abutment.

**Rebar Density(per cubic foot):** Assumed rebar mass per unit volume used for quantity takeoff.

**Rebar Weight:** (Read-only) Total rebar weight derived from Rebar Density and the abutment volume.

**Weight:** (Read-only) Total concrete weight derived from the material unit weight and the abutment volume.

**Filled Bottom Area Volume:** Volume of the filled region at the bottom of the abutment, used when the seat extends below the default footprint. (Read-only)

**Material (Read-Only):** Name of the assigned concrete material, shown for verification. (Read-only)

### Referencing Objects

These rows list the objects that reference this abutment — useful for checking which piles, pile groups, and approach slabs are tied to it.

**Piles:** (Read-only) List of Pile workflow items that reference this abutment.

**Pile Groups:** (Read-only) List of Pile Group workflow items that reference this abutment.

**ApproachSlab:** (Read-only) List of Approach Slab workflow items that reference this abutment.

**Foundations:** (Read-only) The footings that reference this abutment.

**Supports Backfill Soil (readonly):** Yes on this abutment: its wall shells are marked as the soil face, so a **Backfill Soil** item can pick it and generate soil springs on that face. A Backfill Soil item refuses an abutment type without this flag. (Read-only)

**Supports Abutment Top loads (readonly):** Yes on this abutment: an **Abutment Surface Load**, or a **Point Load** placed on the abutment top, can be applied to it. Abutment types without this flag are refused. (Read-only)

**Backfill Soils:** The Backfill Soil items that picked this abutment. The mesh gets a row of nodes at each of their soil layer elevations, so the soil springs land on mesh nodes. (Read-only)

**Backfill Soil Lifts (legacy):** No longer used. It listed the Backfill Soil Construction items when backfill was placed in lifts with their own elevations; backfill is now placed in one piece and that item no longer picks an abutment. The row is kept only so that older projects still open. (Read-only)

### IFC

**Type \[IfcBridge/IfcBridgePart/IfcBeam/IfcColumn/IfcSlab/IfcFooting/IfcPile/IfcBearing/IfcReinforcingBar/IfcReinforcingMesh/IfcTendon/IfcMechanicalFastener/IfcAlignment/IfcPositioningElement/IfcKerb/IfcGuardrail/IfcSurfaceFeature/IfcElementAssembly/IfcCableSegment/IfcSensor/IfcDistributionElement/IfcPlate/IfcWall/IfcRail/IfcRoad/IfcDiscreteAccessory/IfcDistributionSystem/IfcMember/IfcBuildingElementProxy]:** The IFC entity the abutment is exported as. Default IfcWall.

**Predefined Type \[USERDEFINED.STEM\_WALL/ELEMENTEDWALL/MOVABLE/PARAPET/PARTITIONING/PLUMBINGWALL/RETAININGWALL/SHEAR/SOLIDWALL/STANDARD/WAVEWALL/USERDEFINED/NOTDEFINED]:** The IFC predefined type written with the entity. Default USERDEFINED.STEM\_WALL.

**Export to IFC? \[Yes/No]:** When No, the abutment is left out of the IFC export. Default Yes.

**Write Material to IFC? \[Yes/No]:** When Yes (default), the abutment is written with its material; No writes it without one.


---

# 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/substructure-csb/abutment-system-csb/integral-abutment-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.
