Skip to main content
Skip table of contents

IMOS - Creating a New Voyage from an Estimate

Walkthrough: Scheduling a Voyage

These breadcrumbs show where you are in the walkthrough. To move to a different section, click its link:

Create an Estimate > Create a Voyage > Hand Off to Operations

Note:

  • You must have the Fix an Estimate Module Right selected, under Actions in the Chartering module, and the following configuration flags must be disabled: CFGEnableVesselVetting, CFGEnableChartManualStatusFlags, and CFGEnableUserGroupOnFixture.

  • Once the estimate has been fixed, further changes to it will not update the voyage operations. This is to distinguish between what has been estimated against the actual voyage performance. On a side note, changes to the voyage fixture will apply to the voyage operations.

To create a new Voyage from an Estimate, do one of the following:

Depending on the Operation Type:

  • For a TC Out Estimate, a TC Out Fixture is created. All the information from the Estimate moves to the fixture and then to the voyage. After the fixture is created, the button changes to Open Fixture.

  • For other Operation Types, the Create New Voyage form appears:

Create New Voyage

When you open the Create New Voyage form, some fields might be completed. Complete the remaining fields according to the voyage.

  • You cannot reuse Vessel/Voy No. combinations.
  • Opr Type: Type of voyage being scheduled. The following default types are available:
    • OVOV: Owned Vessel, Own Voyage
    • OVTO: Owned Vessel, TC Out
    • RELT: Cargo Relet
    • TCOV: TC In Vessel, Own Voyage
    • TCTO: TC In Vessel, TC Out
      Note: Time Charter contracts and Fixtures must be specified for Time Charter Opr Type voyages and cannot be removed once the voyage has been scheduled.
  • Consecutive Voyage: Select this check box if there is already a previous voyage for the vessel. The following apply:
    • The completing date of the previous voyage becomes the commencing date of the new voyage (displayed in the Commencing field).
    • The last port of the previous voyage becomes the commencing port of the next voyage.
    • The ending bunker inventory of the previous voyage becomes the beginning bunker inventory of the next voyage.
    • When creating a new voyage:
      • For an OV/owned vessel without a linked TCI/Head Fixture, the Consecutive Voyage check box is selected by default from the second voyage.
      • When creating a new voyage for a vessel with a TCI/Head Fixture code specified, the Consecutive Voyage check box is selected by default, and the Voyage Number is assigned based on the last voyage linked to that TCI/Head Fixture. If the selected TCI/Head Fixture does not have any voyages linked to it, and configuration flag Allow Voyage Overlap is enabled, the Automatically Number Voyage check box is cleared, and the Voyage Number must be manually specified.
  • Automatically Number Voyage: Select to automatically assign the next sequential voyage number for the vessel.
    • Custom voyage numbers can be defined using configuration flags. You can automatically number voyages in the following ways:
      • In sequence from the last voyage number
      • Based on the current year plus a 2- or 3-digit sequential number. For example, in 2013, the first voyage for each vessel would be either 1301 or 13001.
        Note: Letters are not allowed in voyage numbering.
      • With a unique Voyage Number across the entire database, rather than for a particular vessel. Each new voyage is assigned the next open sequential number.
      • With a unique Voyage Number for voyages of Operation Types SPOT, RELT, and COAS.
  • Create From: If previously entered contract data is available to create the new voyage from, the source may be selected, or you can select it. Upon voyage creation, the source data is included in the new voyage. The available options are:
    • Voyage Fixture: Automatically selected if scheduling a voyage from a Voyage Fixture.
    • TCO Fixture: Automatically selected if scheduling a voyage from a TC Out contract.
    • Cargo: Automatically selected if scheduling a voyage from a Cargo/VC In.
    • Cargo COA: Automatically selected if scheduling a voyage from a Cargo COA linked lifting. Filters help you find the COA by Charterer, Cargo, Load Port, and Discharge Port.
    • Booking: Automatically selected if scheduling a voyage from a booking
      • If no Operation Type is selected, any Booking Number can be selected if it has linked liftings that can be scheduled.
      • If the Operation Type is OVOV, TCOV, or RELT, only Cargo Bookings can be selected.
      • If the Operation Type is set to SPOT, only VC In Bookings can be selected.
    • No Source: To create a voyage from scratch.
  • Voyage Template: If there is a Voyage Template Rule for the vessel, that template appears; otherwise, the last Voyage Template that was used for this vessel appears, but you can clear it or select a different one. You can also change the Voyage Template after the voyage has commenced.

Related Configuration Flags
Name/FlagDescription

Exclude Status from Voyage TC Dropdown
CFGExcludeStatusFromVoyageTCDropdown

A comma-separated list of Statuses that will be excluded from the TC Code dropdown on the Create New Voyage and Voyage Estimate forms. Valid values: Opportunity, On Subjects, Fixed, Delivered, Redelivered, Under Construction, Purchased, Sold, Closed, Canceled, and Withdrawn. Time Charters with Closed, Canceled, and Withdrawn status will be excluded by default.
Allow Voyage Overlap
CFGAllowVoyageOverlap

When enabled, the system will warn that your commencing date is in another voyage's period. It will default No to the message box asking if you want to continue, but will allow clicking Yes.

Default Auto Number Voyage
CFGDefaultAutoNumberVoy

Select the Automatically Number Voyage check box by default for all new voyages.

Voyage No Format
CFGVoyageNoFormat

Automatically assign voyage numbers by year:

  • 0: Default.
  • 3: Use voyage numbers based on entry date year (YY) plus two digits (e.g., the first voyage of 2020 is 2001).
  • 4: Use voyage numbers based on entry date year (YY) plus three digits (e.g., the first voyage of 2020 is 20001).

If this is used in conjunction with CFGUseGlobalVoyageNumbering, when a new year begins:

  • The voyage number will continue sequentially, ignoring the new year. To resolve this, set CFGUseGlobalVoyageNumbering to N.
  • If you must have CFGUseGlobalVoyageNumbering enabled, create a new voyage with voyage number as YY 01 or YY001, and that will be the largest voyage number in the system. Then, you can set CFGUseGlobalVoyageNumbering back to Y.
Use Global Voyage Numbering
CFGUseGlobalVoyageNumbering

Use unique voyage numbers across the entire database, rather than simply for a particular vessel. New voyages are assigned the next highest sequential open number based on the other voyages in the database.

Use Global Spot Voyage Numbering
CFGUseGlobalSpotVoyNumbering

Create new SPOT/RELT/COAS voyages with a globally unique voyage number across these three operation types.

Charterer View
CFGChartererView

Uses the Charterer's view instead of the standard Cargo form. When enabled:

  • When a voyage is scheduled using Cargo as the source, the Opr Type on the Create New Voyage form defaults according to the Counterparty on the Cargo contract. If the Counterparty is an Owner, the Opr Type is SPOT, otherwise it is TCOV or OVOV depending on the Ownership field on the vessel. Opr Type can be changed, and if the selected type is incompatible with the Cargo counterparty, the Counterparty column in the Voyage Manager Cargoes grid is cleared.
  • All noncoload Cargoes in a voyage synchronize to have the same CP Date and CP Terms Details form.
Validate Contract Status to Schedule
CFGValidateContractStatusToSchedule

Restricts scheduling voyages unless Time Charters are Fixed or Delivered and Cargoes are Confirmed.

Enable COA Planning Period
CFGEnableCOAPlanningPeriod

Adds Planning Periods functionality to COAs, with Lift Size and Option % fields and a Planning Period grid. The Pricing information for a Planning Period can be specified in the Planning Period field on the Pricing tab. When linked liftings have the Use Pricing from COA check box enabled, the Pricing information will be inherited from the COA, based on which Planning Period is selected in the Cargo form. This feature should not be used with Cargo Booking (CFGEnableCargoBooking and related flags).

Use Cargo Benchmark on Voyage
CFGUseCargoBenchmarkOnVoyage

If enabled, when scheduling a Voyage from a Cargo contract that uses Benchmark Estimate as its Exposure Basis, the new voyage will be initialized from the Benchmark Estimate of the Cargo contract.

Update Next Voyage With Routing
CFGUpdateNextVoyageWithRouting

When saving a voyage whose last port has been modified, the update to the following consecutive voyage will include insertion/removal of applicable transit ports, and apply automatic update of estimated expenses as necessary.

Allow Restrict Voyage Auto Number Consecutive
CFGAllowRestrictVoyAutoNumberConsecutive

If enabled, a new Module Right Voyage Auto-Numbering/Consecutive Checkboxes appears, allowing the administrator to restrict users' rights to modify the Automatically Number Voyage check box on the Create New Voyage form, along with the Consecutive Voyage check boxes on the Create New Voyage form and the Voyage Manager.

Copy Cargo Reference to Voyage
CFGCopyCargoReferenceToVoyage

If enabled, when scheduling a voyage from a Cargo, the voyage's Reference field is populated with the value from the Cargo.

Create Booking from Voyage
CFGCreateBookingFromVoyage		When enabled, the "Create New Voyage" form has a new option under "Create From:" for "Voyage Booking". When selected, upon saving the voyage, a new Booking will be created and linked to the voyage, with its properties initialized basis the entered voyage data. Both CFGEnableCargoBooking and CFGEnableVCInBooking must be enabled for this feature.
JavaScript errors detected

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

If this problem persists, please contact our support.

Contact Support Close