> 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.34/voyage-management-system/step-by-step-guides/positions/open-vessels-and-cargoes.md). # Open Vessels & Cargoes ### **What counts as an "open" vessel** A vessel's open position is the last port call of its previous voyage, with the port call's departure date as the open date. In this current version, each vessel can only have one open position at a time. An open position is created when: * A new vessel is added to the fleet * A TC In contract is created for a vessel with no existing voyages or open positions (opens at the contract's delivery port/date) * Ballast voyage is created with orders * In this case the open position will be derived from the previous discharge port * e.g. previous discharge Shanghai, TBN bunker Singapore, TBN for-orders Santos → open position = Shanghai {% hint style="info" %} Whether a ballast voyage is included in the open position logic is controlled in the General tab in System setting.\ ![](https://content.gitbook.com/content/Ny80gIso6EjznoCNWbeA/blobs/FHLkPGIPaP8PPDgarKON/Screenshot%202026-09-24%20at%2014.23.13.png) {% endhint %} #### Vessel Open Positions column Each card shows: vessel name, open port, business unit, DWT, draft, and open date. Cards are sorted by earliest open date first. **Vessel filters:** DWT, Business Unit, open position port/date, Trade or Area (load and discharge). Once you apply your filters, the system will remember your set up as long as your memory or cache is not cleared. #### When does a vessel's position "close" An open position is closed (and the vessel drops off the list and map) when the vessel is nominated or allocated, onto a voyage. {% hint style="info" %} Whether Nominated or Allocated is the minimum qualifying status, is controlled in the General tab in System Settings. ![](https://content.gitbook.com/content/Ny80gIso6EjznoCNWbeA/blobs/zxGMy0vc7TJNKKf3Zr6i/Screenshot%202026-09-24%20at%2013.52.41.png) {% endhint %} ### **What counts as an "open" cargo** Three types of cargoes are included in the coverage; **Spot cargoes:** * Cargo is unallocated with a Clean Fix status **CoA Cargoes (from a template):** * Cargo created in the Cargo module from a CoA template, with Clean Fix status and not attached to a voyage. **CoA Cargoes (from a scheduled voyage):** * Cargo generated from the Scheduled Voyages tab in the CoA module, with Clean Fix status and a voyage that is not nominated or allocated. #### Open Cargoes column Each card shows: load port → discharge port, commodity and quantity, counterpart and rate, and laycan date. Cards are sorted by earliest open date first. **Quick actions:** each column has its own search bar. Hovering a card reveals a **+** icon (start a new voyage) and an expand icon (open the full drawer). **Cargo filters:** Business Unit, laycan date, Trade or Area (load and discharge), Commodity, cargo type. Once you apply your filters, the system will remember your set up as long as your memory or cache is not cleared. #### When does a cargo's position "close" An open cargo is closed (and the cargo drops off the list and map) when the voyage it is linked to, is nominated or allocated. {% hint style="info" %} How are cargoes derived from Scheduled Voyages in the CoA module handled? To appear in Positions, a CoA cargo linked to a scheduled voyage needs both of these: 1. Its status is Clean Fix. 2. Its voyage is not nominated or allocated. When you create an estimation from one of these cargoes, Positions makes a copy of the cargo for the new voyage, so the original scheduled voyage is left untouched. Once the new voyage is nominated, the cargo is no longer open. This applies whether it is nominated in Positions or elsewhere. The CoA’s scheduled voyages list is then updated with the nominated voyage. Because the voyage keeps its link to the CoA, the contract metrics tracked from its linked voyages stay correct. {% endhint %} *** --- # 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.34/voyage-management-system/step-by-step-guides/positions/open-vessels-and-cargoes.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.