You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 16
Next »
Home > Schedule Optimizer
The Veson IMOS Platform (VIP) Schedule Optimizer is a proprietary algorithm, built on top of the Scheduling workspace, designed to optimize a voyage schedule for either of the following two variables:The optimizer can be used either from the Scheduling workspace, ideal for a voyage-centric workflow, or from the Cargo Book workspace, ideal for a cargo-centric workflow.
The Schedule Optimizer is beneficial for Schedulers, Freight Traders, Charterers, Operators, and Managers at organizations that manage high volumes of often similar voyages.
Workflow
To learn how to use the Schedule Optimizer, see Optimizing Your Schedule.
Error rendering macro 'excerpt-include' : No link could be created for 'VIP - Optimizing Your Schedule'.
Frequently Asked Questions
What can the Schedule Optimizer do? What can’t it do?
The Schedule Optimizer can ingest various data points from a client’s Open Positions and Cargo Book, and use this data to determine the most optimal schedule for the vessels and cargoes, with the goal of either maximizing laycans met or total TCE of the scenario.
When performing these calculations, the Schedule Optimizer takes the following data points into account:
For Open Positions: | For Cargo Book: |
|---|
Vessel open basis date Vessel size/DW Vessel Restrictions Draft
| |
The Schedule Optimizer cannot yet optimize for SPOT or Market Vessels, as the algorithm requires operational information to determine vessel availability.
Can I Optimize for KPI’s beyond Laycans and TCE?
Out of the box, the Schedule Optimizer is focused on these two targets. However, a client can plug in their own algorithm for optimization if they so choose. We have included the two KPIs of laycans and TCE as we see these as foundational points for optimization; we are looking to expand to additional targets as the product matures.
Can I run scenarios to Optimize without committing anything operationally?
Yes. This use case is core to the functionality. Nothing is committed through to operations until the Scheduler makes the final decision and confirms a suggested Estimate. Additionally, the Schedule Optimizer allows the scheduler to keep or discard suggested Estimates through to subsequent runs.
What about co-loading cargos?
The optimizer can co-load cargoes, but there are two important behaviors to understand:
If a vessel has already loaded a cargo that is assigned to a shipment, it won't load cargoes that aren't in that shipment until it has finished the shipment. The vessel also won't start working on a shipment if it already has other cargoes loaded. A cargo is considered to be part of a shipment if it has a shipment number associated with it, even if it is the only cargo in the shipment.
There is no checkbox or setting to turn co-loading on or off, but if the user does not want co-loading, they can assign shipment numbers. Because of the rules described above, that will prevent co-loading.