> 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/truss-bridge-workflow/superstructure-tb/deck-tb/moveable-deck-tb.md).

# Moveable Deck \[TB]

The Moveable Deck models the deck slab of a moveable (bascule) leaf. It is laid out like the Concrete Deck, from deck cross-sections placed at support lines, and connects to the girders and Frame Members that carry it. The deck, together with the girders and floor beams of the leaf, turns rigidly about a horizontal axis along the **Rotation Support Line** by the **Opening Angle**, so the leaf can be analysed closed or at any opening position.

![A bascule leaf in elevation: the rotation axis along the Rotation Support Line at the Rotation Axis Elevation, the closed leaf (Opening Angle 0) and the leaf opened by the Opening Angle](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-e71e8c0948edf92d0493d67ff76fc17deee4b84f%2Fmoveable-leaf-rotation.png?alt=media)

{% hint style="info" %}
Give the deck and every girder and floor beam of the leaf the same **Rotation Support Line**, **Opening Angle** and **Rotation Axis Elevation**: this deck in its **Moveable Bridge** category, and each girder and floor beam with **Moveable Bridge** set to **Yes** in theirs. Frame Members and truss members do not turn by these inputs: they stand where their insertion points are, so place those at the leaf's opening position, for example with a global parameter for the angle.
{% endhint %}

The closed position (**Opening Angle** 0) is the one used for the live load: the deck's nodes are then placed along the alignment, as a Concrete Deck's are, so the live load and every other load that finds the deck by station and offset reaches it. An opened leaf is analysed for its self weight and the other loads that do not find the deck by station and offset. The deck also gives the Roadway its edges in the closed position.

Not covered: live load on an opened leaf, the Deck Casting sequence, and the Concrete Deck's 3D settings (cantilevers, chamfers, drip notch). A **Parabola** variation between two cross-sections is taken as **Linear**. On a curved alignment the deck is placed exactly, and the rotation axis follows the straight chord of the Rotation Support Line.

## General

**Cross-Sections:** The deck cross-sections and where they apply. Two rows are needed at least; the deck runs from the first row's station to the last row's.

* **Cross Section Location:** The support line the row is measured from.
* **Offset From Support Line:** A distance along the alignment from that support line. Use it to start or end the deck away from a support line, or to change the cross-section between two support lines.
* **Cross Section:** The deck cross-section defined under **Deck > Cross-Section**, which gives the deck widths to the left and right of the alignment and the slab thicknesses.
* **Variation w/Next Segment \[None/Linear/Parabola]:** How the cross-section changes to the next row. **None** holds the row's cross-section up to the next row; **Linear** and **Parabola** vary it linearly to the next row.

**Supporting Members:** The Frame Members the deck rests on. The deck connects to a Frame Member at each of its joints that falls inside the deck outline, where the joint stands; the nodes inside a Frame Member's length are not connected. On an opened leaf the joints are turned back by the Opening Angle to check whether they fall inside the outline.

**Supporting Girders (Moveable Bridge = Yes):** The custom shape girders the deck rests on. Each must have **Moveable Bridge** set to **Yes**, otherwise an issue is reported. The deck connects to every finite element node of a selected girder that falls inside the deck outline, and the girder lists this deck in its decks, so its effective width and haunch are read from this deck as from a Concrete Deck.

**Additional Connection Points:** Insertion points where the deck is also connected, for example truss joints that carry the slab directly.

**Material:** The concrete material of the deck, used for the finite element model and the quantities. The user must provide a value.

**Material Zones:** Optional bands of the deck in another material, one row per band as \[Material, Left Offset, Right Offset]. A shell whose centre lies between the left offset (measured to the left of the alignment) and the right offset (measured to the right) takes the band's material, for example an open steel grid over part of the width.

**Top of Deck above Profile Grade:** Vertical distance from the profile grade line to the top of the deck. Positive raises the deck.

**Deck Reinforcement Data:** The longitudinal deck reinforcement, as on the Concrete Deck: start and end stations, rebar material, top and bottom rebars with their spacings, and clear covers. The rows feed the By Length rebar quantities.

## Moveable Bridge

**Rotation Support Line:** The support line the leaf turns about. The rotation axis is horizontal, along this support line, at the **Rotation Axis Elevation**. With no support line selected, the deck stays in the closed position.

**Opening Angle (+ lifts the deck away from the support line):** The angle the leaf is turned by about the rotation axis. **0** is the closed position. A positive angle lifts the deck away from the support line, which opens the leaf.

**Rotation Axis Elevation:** The elevation of the rotation axis (the trunnion), in the same elevation system as the alignment profile.

## FEA

**Long. Mesh Size:** The largest shell length along the alignment. Rows of shells are also placed at every cross-section row and at every connection point, so the mesh meets the members it connects to. At least 1 in.

**Trans. Mesh Size:** The largest shell width across the deck. Columns of shells are also placed at the deck edges, at every connection point and midway between neighbouring connection columns, so each girder takes a whole strip of shells to the midlines with its neighbours. At least 1 in.

**Connection Point Tolerance:** The distance within which a connection point counts as inside the deck outline, and within which two rows or columns of the mesh are taken as one. Must be positive.

**Construction Stage:** The construction stage in which the deck is added to the analysis model.

**Deck Self Weight Factor:** Multiplies the self weight of the deck (1 applies the full weight).

## Quantities

The quantities are computed from the deck in the closed position and presented as read-only values.

**Min Cross Section Area:** Minimum cross-section area along the deck (Read-only).

**Max Cross Section Area:** Maximum cross-section area along the deck (Read-only).

**Min Perimeter:** Minimum cross-section perimeter along the deck (Read-only).

**Max Perimeter:** Maximum cross-section perimeter along the deck (Read-only).

**Length Min Path:** Minimum path length along the deck (Read-only).

**Length @COG:** Path length along the deck's center of gravity (Read-only).

**Length Max Path:** Maximum path length along the deck (Read-only).

**Top Surface Area:** Total top surface area of the deck (Read-only).

**Min Width:** Minimum deck width along the deck (Read-only).

**Max Width:** Maximum deck width along the deck (Read-only).

**Rebar Calculation Method \[By Density/By Length]:** How the deck reinforcement weight is computed. **By Density** multiplies the deck volume by **Rebar Density**; **By Length** sums the rebar lengths from the Deck Reinforcement Data rows.

**Rebar Density(per cubic yard):** Rebar mass per unit concrete volume, used only when **Rebar Calculation Method** is **By Density**.

**Rebar Weight (By Density):** Deck volume multiplied by **Rebar Density** (Read-only).

**Longitudinal Reinforcement Length (Bot Layer):** Total length of the bottom-layer longitudinal rebars (Read-only).

**Longitudinal Reinforcement Length (Top Layer):** Total length of the top-layer longitudinal rebars (Read-only).

**Longitudinal Reinforcement Weight (Bot Layer):** Weight of the bottom-layer longitudinal rebars (Read-only).

**Longitudinal Reinforcement Weight (Top Layer):** Weight of the top-layer longitudinal rebars (Read-only).

**Total Rebar Weight (By Length):** Combined weight of the top- and bottom-layer longitudinal rebars (Read-only).

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

**Weight:** Total weight of the deck; each material zone weighs with its own material (Read-only).

**Material (Read-Only):** Name of the material assigned in the General category (Read-only).

## IFC

**Type:** IFC entity of the deck. Default **IfcSlab**.

**Predefined Type \[Approach\_Slab/Baseslab/Floor/Landing/Paving/Roof/Sidewalk/Trackslab/Wearing/Userdefined/Notdefined]:** IFC predefined type of the deck. Default **FLOOR**.

**Export to IFC? \[Yes/No]:** Whether the deck is written to the exported IFC file. Default **Yes**.

**IFC Place \[Deck Segment/Deck]:** Where the deck slab goes in the exported IFC: a deck segment of its own under the bridge deck (**Deck Segment**, the default) or directly in the bridge deck (**Deck**).

## Referencing Objects

**Construction States:** Construction states referencing this deck (Read-only).

**Barriers:** Barrier objects placed on this deck (Read-only).

**Rails:** Rail objects placed on this deck (Read-only).

**Bicycle Railings:** Bicycle-railing objects placed on this deck (Read-only).

**Cables:** Cable objects referencing this deck (Read-only).

**Link Slabs (Start):** Link slabs referencing this deck (Read-only).

**Link Slabs (End):** Link slabs referencing this deck (Read-only).

**Transverse Beams Under Deck:** Transverse beams placed under this deck (Read-only).

**Superstructure Continuity:** Superstructure continuity objects that name this deck as their host deck (Read-only).


---

# 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/truss-bridge-workflow/superstructure-tb/deck-tb/moveable-deck-tb.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.
