> 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/construction-cug/changes-cug.md).

# Changes \[CUG]

An analysis may require parameters to be redefined across several stages to ensure the stability of the bridge. To achieve this, changes to various elements can be defined based on a specific sequence and stage.

-A common scenario is that girders without cross-frames and bracings can sometimes be in an unstable condition, which may cause the Finite Element Analysis (FEA) to fail or remain incomplete.

If the bracings are constructed after the erection of the girders, the **Bearing Fixity Change** section can be utilized to successfully complete the analysis.

-Another use case arises during seismic analysis, where factors such as **cracked inertia** are essential. These factors can be assigned to pier columns based on the defined construction stage. In such cases, **Pier Section Property Overrides** object is employed to accurately reflect the structural behavior during different phases of construction.

For the objects that can be defined in this section, please refer to the related page for detailed explanations of the parameters.


---

# 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/construction-cug/changes-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.
