> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/fahrplan.md).

# Timetable

The "Timetable" widget shows departure times from a starting point and optionally to a destination. Only SBB (Swiss Federal Railways) data is displayed.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/s30Ply7vSkVMVWAlKY6q/Fahrplan%20(8).png" alt=""><figcaption></figcaption></figure>

## When should this display be used?

This display should be used when you want to show departure times for a specific starting point and optionally also visualize the connections to a selected destination.

## What is displayed?

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/VcL85Zsg5B6PpTzMayOM/Fahrplan%20(9).png" alt=""><figcaption></figcaption></figure>

<table data-header-hidden data-full-width="false"><thead><tr><th width="90"></th><th width="183"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Title bar</td><td>The title of the widget. Can be set during widget configuration under "Primary Asset".</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td>Widget icon</td></tr><tr><td><strong>[C]</strong></td><td>Starting point</td><td>Shows the route's departure location.</td></tr><tr><td><strong>[D]</strong></td><td>Destination</td><td>Shows the destination if defined.</td></tr><tr><td><strong>[E]</strong></td><td>Vehicle number</td><td>The vehicle number, e.g. bus or train number.</td></tr><tr><td><strong>[F]</strong></td><td>Mode of transport</td><td>The type of transport, e.g. bus, train or tram.</td></tr><tr><td><strong>[G]</strong></td><td>Arrival in min</td><td>The remaining time until the vehicle arrives, in minutes.</td></tr></tbody></table>

## Configure widget

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/Fi3AhgILpLT8QzDtWCYR/Fahrplan%20(4).png" alt=""><figcaption><p>Fig. 3 Configure widget</p></figcaption></figure></div>

1. Make sure you are in the **"Dashboard"** menu.
2. Add the route schedule widget as [↗ Custom widget.](/collection/english-v14/documentation/widgets/benutzerdefinierte-widgets.md#schritt-fur-schritt-ein-benutzerdefinertes-widget-erstellen)
3. Click on **«Add widget»**.
4. Click on «**Custom»**.
5. Click on **“Your custom timetable widget”**.

   ▷ The window **"Fig. 3 Configure widget"** appears
6. Optional: Select a **\[A]** the primary asset
7. Enter in **\[B]** the **Starting point** and click on one of the suggested places.

   ◈ If only the starting point is selected, all departures leaving from this starting point are displayed.
8. Optional: Enter in **\[C]** the **Destination** and click on one of the suggestions.

   ◈ If the destination is also selected, only departures from the starting point to the destination are displayed.
9. Select in **\[D]** how much space the widget should take up on the dashboard.
10. Click on **\[E]**

    ▷ The widget appears on the dashboard.


---

# 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.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/fahrplan.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.