> 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/master.md). # Knowledge Base Find answers to your questions... Welcome to the main source of information on the Dataloy product suite. {% hint style="success" %} **🚀 You're viewing the Release 8.34 preview** #### Fine-tuning Positions Positions now supports CoA cargoes that sit on scheduled voyages, so charterers can work with their full contract book alongside spot cargoes. When one of these cargoes is used in a voyage estimation, it keeps its CoA link. When that estimation is promoted, the voyage appears automatically in the CoA's Scheduled Voyages tab, and contract quantities stay accurate throughout. Optional CoA cargoes that have not yet been declared now carry an "Optional" tag on the cargo card. This makes it easy to tell options apart from firm commitments at a glance, and the tag clears automatically once the option is declared. The map is easier to read in busy areas. Vessel and cargo layers can be switched on and off independently, and the legend explains what each position state means. Vessel and cargo filters now include your company's own areas and zones. *Feature available upon request.* #### Hire-Payment Improvements Operations controllers have more control over how and when hire is paid. Time Automation has been renamed Payment Cycle Automation. Payment cycles can now be set in days or in monthly and semi-monthly cycles, with the option to follow calendar months or to set specific payment days. New system preferences let you turn the automation on by default for new TC contracts and durations. The create TC and TC duration modals now capture minimum and maximum duration, variance and rate directly. When Payment Cycle Automation recalculates, existing TC rates are kept rather than regenerated. Valid To dates on individual TC rates can also be locked, so manual adjustments are preserved. Accountants get a clearer overview of hire that is coming due. The Pending Hire Payable tab shows the next due period for each contract, can be sorted and filtered by period start date, and assigns each pending item a meaningful date. Business controllers can set a company and business unit on each TC duration, so hire can be reported and invoiced by those dimensions. #### Estimate Combined Result Charterers can add a TC Out "tail" directly to a voyage charter estimate. The delivery port is taken from the VC's last port, and the redelivery date is calculated from the TC days entered. The combined TCE, duration and result across both legs are then shown together, with no need to build and reconcile two separate contracts. The TC Out stays linked to the VC, and fixing the VC does not change its result. OPEX is now applied only once in a charter chain, on the voyage with operational responsibility for the vessel. The logic uses the Owned and Bareboat flags on TC contracts, so running costs are not double-counted. Financial users can allocate derivative lines to voyages that have not yet been nominated, so exposure can be tracked earlier. In Voyage Alternatives, firm ports from the base voyage can now be treated as optional, in the same way as optional ports. {% 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/master.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.