> 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.31/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/overview/profit-loss-summary/analysis.md).

# Analysis

When in a voyage drawer the analysis tab is available in the tab section. In this tab you will be presented with a graph to give you a visual view of the development of key values in the selected voyage.

The graph that is displayed represents the total days for the columns, and the TCE for the line. These values can be changed in the dropdown fields on the top left. The timeline shown will be from the preliminary snapshot is taken to the current date. If the voyage is closed, the last value will be the last time the voyage was changed instead of todays date.

![](https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/WODjaisuqyWbTVrznMZv/Screenshot%202021-12-31%20at%2010.44.50.png)


---

# 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://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/overview/profit-loss-summary/analysis.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.