Skip to main content
Skip table of contents

IMOS - Managing a Voyage

The Veson IMOS Platform is the market-leading cloud solution for commercial marine freight and fleet management.

To manage a voyage, in the Voyage Manager, do the following:


Step Number

Step

 Key Information: About Voyage Status

1

  • Validation symbol: If information is not complete and correct, click the symbol to see a message describing any issues.

    • : All information is complete.

    • : Some information is missing.

    • : The form contains one or more errors.


2

To save the voyage, click 

.

By default, the voyage Status is Scheduled.

3

When the voyage begins, change the voyage Status from Scheduled to Commenced.

When the voyage Status is changed from Scheduled to Commenced, the Status for the first port changes to Sailed.

4

As you continue through each port, right-click the port line and click Port Activities to enter Port Activities for the voyage. The Itinerary updates with any changes.


5

When you are traveling between ports, right-click the port line and click Activity Reports to track information in the Activity Reports.


6

To enter Port Advances or Expenses, right-click the port line and click Port Expenses. As you enter financial information, it appears on the P&L tab.


7

To enter Voyage Other Revenues and Expenses not associated with a port or with freight, click Other Rev/Exp and then click Other revenues and expenses.


8

When the Start Sea Passage Port Activity is entered for the last port, the port Status changes to TE (Terminated).

The voyage Status also changes to Completed. Port, bunker, cargo, and financial data can still be modified.

9

After all voyage transactions are completed, change the Status to Closed.

After the voyage Status is changed to Closed, the voyage cannot be modified.

For industry-specific voyage management workflows, see BargingLNG, and Pooling module documentation.



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.