> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/overview/performance-benchmarks/110-bus-500-kv-transmission-system.md).

# 110-Bus 500 kV Transmission System

<table data-search="false"><thead><tr><th width="264">Model name</th><th>110-bus 500 kV transmission system</th></tr></thead><tbody><tr><td><strong>Highlights</strong></td><td><ul><li>Only simulation tool capable of simulating this network on as few as <strong>1 core at 24 us or 2 cores at 11 us</strong></li></ul><p>HYPERSIM <strong>automatically parallelizes</strong> the network into 268 tasks and distributes them on all available cores for maximum speed, e.g. 10 us on 7 cores</p></td></tr><tr><td><strong>Model diagram</strong></td><td><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ce50d0919bfed7532728a1fdd3e481c63b891001%2Fimage%20(36).png?alt=media" alt="" data-size="original"></td></tr><tr><td><strong>Single-phase nodes</strong></td><td>336</td></tr><tr><td><strong>Generators (3φ, synchronous)</strong></td><td>14</td></tr><tr><td><strong>Transformers (3φ)</strong></td><td>14</td></tr><tr><td><strong>Single-circuit lines (3φ, Bergeron model)</strong></td><td>171</td></tr><tr><td><strong>RLC (3φ)</strong></td><td>44</td></tr><tr><td><strong>Breakers (3φ) and faults (4φ)</strong></td><td>2 + 1 = 3</td></tr><tr><td><strong>Hardware</strong></td><td><strong>OP5033XG2 - 8</strong></td></tr><tr><td><strong>Software</strong></td><td><ul><li><strong>Platform:</strong> HYPERSIM 2026.1.0.o6</li><li><strong>Compiler:</strong> GCC 8.3.0</li></ul></td></tr><tr><td><strong>Recommended minimum license</strong></td><td>HXG Max (2 cores)</td></tr><tr><td><strong>Results 1 core</strong></td><td><ul><li><strong>Number of core(s) = 1</strong></li><li><strong>Minimum time-step:</strong> 24 us</li></ul></td></tr><tr><td><strong>Results 2 cores</strong></td><td><ul><li><strong>Number of core(s) = 2</strong></li><li><strong>Minimum time-step:</strong> 11 us</li></ul></td></tr><tr><td><strong>Results 7 cores</strong></td><td><ul><li><strong>Number of core(s) = 7</strong></li><li><strong>Minimum time-step:</strong> 5 us</li></ul></td></tr></tbody></table>

\* Performance under transient conditions varying considerably depending on the study type, this benchmark measures the minimum achievable time-step without overruns in steady-state conditions. A rule of thumb is to consider 10 to 20 % buffer time for calculations under transient conditions.


---

# 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://www.opal-rt.com/docs/hypersim/overview/performance-benchmarks/110-bus-500-kv-transmission-system.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.
