> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.17/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/overview/vessel.md).

# Vessel

This page reveals the essential information of the Vessel section in the Voyage Overview tab.

<figure><img src="https://content.gitbook.com/content/Zao7rN3mdCfNKVRfQpS0/blobs/ed0tE1ik8ljEZ8kYLPLy/image.png" alt=""><figcaption><p>(Figure 1) Vessel section in Voyage Overview</p></figcaption></figure>

#### Speed & Consumption per Bunker

Speed Ballast: Displays the speed for ballast port calls when all port calls have the same speed. If port calls have different speeds, this field will be disabled and the text will read "Multiple". Changing this value will update the speed for all ballast port calls.

Speed Laden: Displays the speed for laden port calls when all port calls have the same speed. If port calls have different speeds, this field will be disabled and the text will read "Multiple". Changing this value will update the speed for all laden port calls.

The drop-down menu will contain all vessel options for the selected passage, as well as the option to 'Add New Speed'. This new speed will not impact the vessel setup and will only apply to all Ballast/Laden port calls on the chosen voyage. This also applies to the Main Engine Port Idle and Main Engine Port Working fields. For more details, please consult the [Speed and Consumption](/release-8.17/voyage-management-system/step-by-step-guides/vessels/vessel-speed-and-consumption-data.md) documentation.

#### Vessel

Changing vessel in this section will change the voyage's and the connected cargoes' company and business unit to the selected vessel's.


---

# 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.dataloy.com/release-8.17/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/overview/vessel.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.