> 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/openbrim/getting-started.md).

# Getting Started

Welcome to the OpenBrIM Platform Application, Parametric Modeling, and Library Concept fundamentals. If you're an experienced bridge or structural engineer familiar with analysis and design processes, this guide will help you understand how the OpenBrIM Platform can streamline your workflows, making them faster and more reliable. Along the way, you'll develop new parametric thinking skills that complement your engineering expertise.

After completing this guide, you'll be able to:

* Navigate the OpenBrIM Platform Application
* Understand the Parametric Markup Language and Parametric Object Development
* Create parametric 3D models
* Build parametric finite element models
* Use cloud-based features for model revision history
* Share models with colleagues
* Run Finite Element Analysis
* Review Staged Construction Analysis results
* Review Influence Surface Based Live Load Analysis results
* Design superstructure and substructure elements per AASHTO 9th Edition and DOT Amendments
* Load rate superstructure elements
* Use parametric customized summary reports

{% hint style="info" %}
**Key Concept**

OpenBrIM is a parametric environment—bridge components, code checks, analysis calculations, and workflows are all defined as reusable library objects. Understanding this will help you get the most out of the platform.
{% endhint %}


---

# 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/openbrim/getting-started.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.
