Skip to main content
Skip table of contents

IMOS - Requirement-Driven Bunker Procurement

NoteConfiguration flag CFGEnableRequirementDrivenBunkerWorkflow must be enabled.

In requirement-driven bunker procurement, you can change operational quantities (Opr Qty) on the bunker plan until a requirement is confirmedAfter that, Opr Qty automatically calculates as the sum of confirmed Bunker Requirements until you have actual liftings, at which point the Opr Qty becomes the sum of the bunkers lifted.

This workflow comprises three phases:

Creating a Bunker Plan

When creating a bunker plan on the Voyage Bunkers form, you can do any of the following:

  • On each Fuel Type tab, edit Opr Qty as needed.
  • Create as many preliminary requirements as you want; they do not affect Opr Qty on the Voyage Bunkers form.


On the Voyage Bunkers plan for a port, you add 1,000 MT of IFO. As long as no requirements have been confirmed, you can continue to change the value of Opr Qty.

When you create the first preliminary requirement, Req Qty and Opr Qty (read-only) in the requirement default to 1,000 MT (the value of Opr Qty on the Voyage Bunkers form). Req Qty on the Voyage Bunkers and Bunker Requirement forms are kept in sync; you can update the value in one of these fields, and it updates the other field as well.

Confirming Bunker Requirements

To confirm a Bunker Requirement, edit its Req Qty as needed and then set its Request Status to Confirmed. On the Voyage Bunkers form, Opr Qty becomes read-only, and its value equals the sum of Req Qty in all confirmed requirements.

  • If you create, edit, or delete a confirmed requirement, Opr Qty recalculates on the Voyage Bunkers form.
  • On any new subsequent Bunker Requirement:
    • Opr Qty (read-only) defaults to the value of the same field on the Voyage Bunkers form.
    • Req Qty defaults to 0 MT.
  • You can create preliminary requirements at any port in the voyage; they do not affect Opr Qty on the Voyage Bunkers form.

Example (continued):

To request 1,000 MT of IFO, you confirm the requirement you just created. The Req Qty value flows back to Opr Qty on the Voyage Bunkers form, which shows 1,000 MT and is locked from editing. The Opr Qty shown in the confirmed Bunker Requirement is always the same as the same field on the Voyage Bunkers form. You cannot edit the Opr Qty in the requirement.

Adding multiple requirements:

More bunkers need to be lifted, so you create a second requirement. On the new requirement, Req Qty defaults to 0 and Opr Qty (read-only) defaults to 1,000 MT.

The amount to lift is 200 MT, so you add 200 MT to Req Qty on the Bunker Requirement. This also adds 200 MT to the same field on the bunker plan, since these two fields are always in sync.

You set the requirement to Confirmed and save it. This triggers an update to the bunker plan. The 200 MT is added to the existing 1,000 MT, so the plan Opr Qty now shows 1,200 MT. The same field in the requirement also shows 1,200 MT.

You decide to cancel the 200 MT requirement. When a confirmed requirement is cancelled or deleted, this triggers another update to the Voyage Bunkers Opr Qty. The 200 MT value is removed from the plan, which now shows 1,000 MT.

Lifting Bunkers

After bunkers have been lifted, Opr Qty on the Voyage Bunkers form changes to show the actual lifted amounts on the vessel.

  • If you create additional confirmed requirements for the same port, the Opr Qty does not recalculate because it shows only the sum of the lifted amounts.
  • You can still create additional liftings for the same port, and the value of the liftings add to the value in the Opr Qty field in the Voyage Bunkers form.

Related Configuration Flags

Prevents setting the status of a Bunker Requirement back to Preliminary after it has been set and saved as Confirmed.


Prevents setting the status of a Bunker Requirement to any other status after it has been set and saved as Cancelled.


Enter a comma-separated list of of fields that are required in Bunker Requirements. Possible fields: company, reqQty, vessel, port, and requestedDeliveryDate.


Prevents changing the Port name after a Bunker Requirement is created and saved with any status.

  • If you want to change the Port in a saved Bunker Requirement, you must cancel or delete the Bunker Requirement and then create a new one.
  • The Port name at the top of the Bunker Requirement form must be the same as the Port name in the inquiry line.

When enabled, you can only add one inquiry line to a Bunker Requirement. The inquiry line is kept in sync with the Req Qty field, regardless of inquiry line status.


When enabled, the Requested Delivery Date field is a required field on Bunker Requirements that are not attached to a voyage.

JavaScript errors detected

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

If this problem persists, please contact our support.