> 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/openbrimfea/loads-fea/dynamic-excitation-fea.md).

# Dynamic Excitation \[FEA]

Dynamic Excitation holds the input records for seismic and transient analysis.

* [Response Spectrum Curves](https://docs.openbrim.org/templates/openbrimfea/loads-fea/dynamic-excitation-fea/response-spectrum-curves-fea.md) define the design spectrum that [Eigenvalue & Response Spectrum Cases](https://docs.openbrim.org/templates/openbrimfea/analysis-fea/eigenvalue-response-spectrum-cases-fea.md) look modes up on, to combine the modal responses into peak seismic demand.
* [Time History Functions](https://docs.openbrim.org/templates/openbrimfea/loads-fea/dynamic-excitation-fea/time-history-functions-fea.md) hold a tabulated excitation record, which [Time History Cases](https://docs.openbrim.org/templates/openbrimfea/analysis-fea/time-history-cases-fea.md) integrate step by step - what you need when the timing of the response matters or when nonlinear links dissipate energy.
* [Support Motions](https://docs.openbrim.org/templates/openbrimfea/loads-fea/dynamic-excitation-fea/support-motions-fea.md) prescribe a displacement record at an individual support joint. Several of them on one Time History Case give multi-support (spatially varying) excitation - different ground motion at different supports, which is what a bridge long enough for wave passage, incoherence or differing site conditions actually sees. Uniform excitation cannot produce differential-support demand at all, since moving every support together is rigid-body translation.

Mass is the thing to get right first in dynamic analysis: every period scales with it, and every dynamic result follows from the periods. Concentrated mass for inertia that no modelled element carries - barriers, utilities, equipment - is added on [Node Mass](https://docs.openbrim.org/templates/openbrimfea/model-fea/node-mass-fea.md). Note that node mass values are entered as **weights**, which the solver divides by gravity.


---

# 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/openbrimfea/loads-fea/dynamic-excitation-fea.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.
