> 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-6.46/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/overview-tab/vessel.md).
# Vessel
The Vessel section will display some useful information about the vessel that is currently connected to the voyage. You can click on the  icon to open up the vessel drawer if you seek more information on the vessel.
The information fields for the vessel displayed in the section.
Speed Laden: Showing the speed for laden port calls if all port calls have the same speed. If port calls has different speeds this field will be disabled and the text will be: Multiple. Changing this value will update speed for all laden port calls.
Speed Ballast: Showing the speed for ballast port calls if all port calls have the same speed. If port calls has different speeds this field will be disabled and the text will be: Multiple. Changing this value will update speed for all ballast port calls.
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-6.46/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/overview-tab/vessel.md?ask=&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.
