> 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-5.15/voyage-management-system/step-by-step-guides/vessel/internal-data.md).

# Find Vessel Internal Data

Vessel "internal data" can be accessed in the top tab menu of the vessel master data screen.

For "old" vessels that you have in the system that has minimum of one commenced voyage, the internal data should already be established. For new vessels, or vessels without commenced voyages, then these vessels you need to "Create Internal Data" as per below indicated.

![](https://187209081-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Liw6C9Fe7rohFtkU25j%2F-Lt4jARvGRp_ghevLCJA%2F-Lt4tQyl2ZOFcBd-X2DA%2Fimage.png?alt=media\&token=94209763-f414-4cfd-9acb-89d5c4a68dfe)

Below three items need to be filled in to create

![](https://187209081-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Liw6C9Fe7rohFtkU25j%2F-Lt4jARvGRp_ghevLCJA%2F-Lt4uKvG0Uzw2yv7jC0w%2Fimage.png?alt=media\&token=401b11ca-9ec6-41e9-94b9-d6b8a80a1092)

Once this is done it will be possible to access below screen

![](https://187209081-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Liw6C9Fe7rohFtkU25j%2F-Lt4jARvGRp_ghevLCJA%2F-Lt4v782rwDPcIkostYs%2Fimage.png?alt=media\&token=5fd08eed-ebdc-47ba-864b-2cd90d1a1b60)


---

# 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-5.15/voyage-management-system/step-by-step-guides/vessel/internal-data.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.