> 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/construction-cbg/superstructure-construction-cbg/rail-construction-cbg.md).

# Rail Construction \[CBG]

Construct one or more rail (railroad track) objects as part of a construction stage. Use this when rails are placed on the structure as the construction sequence advances.

## General

**Stage:** Construction stage in which the selected rails are activated.

**Rail:** List of rail objects constructed in this stage. At least one rail must be selected.

**Self Weight Factor:** Multiplier applied to the rail's self weight when the rails become active in this stage.

**Stiffness \[NO/YES]:** When YES, the rail's stiffness is added to the analysis model during and after this stage.


---

# 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/construction-cbg/superstructure-construction-cbg/rail-construction-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.
