> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/transportation/ja/shu-song.md).

# 輸送

Verkada Command で、堅牢なカメラとクラウドベースの映像、位置情報、テレメトリを使用して車両フリートを安全に管理します

Verkada Transportation は、バス、列車、フェリーなどの車両にクラウド管理型の物理セキュリティを拡張します。このプラットフォームは、堅牢化されたカメラと KGX61 Transportation Gateway を組み合わせており、カメラへの電源供給、クラウドへの接続、GPS 位置情報と車両テレメトリの取得を行います。Command の単一のインターフェースから、ライブおよび録画済みの映像を確認し、車両を追跡し、インシデントを調査できます。

このコレクションでは、KGX61 gateway と transportation カメラの取り付けと接続、Command でのデバイスの追加と管理、そして位置情報や運転イベントデータを映像とあわせて使用する方法を説明します。また、Transportation が他の Verkada 製品とどのように連携するかも解説しているため、車両群と施設を 1 か所で管理できます。

まずは、こちらのリンクをご覧ください:

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/transportation/ja/hajimeni/page-1.md">Transportation Gateway の使い始め方</a></td></tr><tr><td></td><td><a href="/transportation/ja/hajimeni/roles-and-permissions-for-transportation-gateways.md">Transportation Gateway の役割と権限</a></td></tr><tr><td></td><td><a href="/transportation/ja/hajimeni/transportation-gateways-network-settings.md">Transportation Gateway のネットワーク設定</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/transportation/ja/shu-song.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 `build a script that syncs our docs to a CMS` 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.
