IMOS - Bunker Requirement

The Bunker Requirement communicates request information from the Operator to the Bunker Manager.

Security Module Rights for the Bunker Requirements form differentiate between Operator and Bunker Manager responsibilities by allowing editing for the appropriate fields.

In the Operations module center , under Bunkers, click Bunker Requirement.

If a port call with a Bunker Requirement is changed, the Bunker Requirement remains linked to the new port call, but if the Bunker Alert List is enabled, it will have a Bunker Requirement Alert. If the port call is deleted, the Bunker Requirement is unlinked after the voyage is saved and shows as unlinked in the Bunker Requirement List. An unlinked Bunker Requirement can be linked to a different port call or canceled.
If there is an existing lifting at the Port, in the Planned Liftings grid, editing Req Qty automatically adjusts Opr Qty by the same amount. When this happens, the Opr Qty field is highlighted and a tooltip explains the difference in value between the two fields.

Note: Veslink provides a different form for entering bunker requirements.

Related Configuration Flags

CFGEnableVesselBunkerGrade	Specifies the Fuel Grade in a G (Grade) column on the Vessel or Time Charter In/Out form, which defaults the value on the Bunker Requirement; it can be overridden but is required for Confirmed status.
CFGRequireAgentsToConfirmRequirement	Requires values for Port Agents when confirming a Bunker Requirement.
CFGVerifyMatchingCompany	Displays a validation error if any of a voyage's or Voyage Estimate's linked contracts or Bunker Requirements has a different Company set than the voyage company.
CFGLockConfirmedRequirements	Prevents setting the status of a Bunker Requirement back to Preliminary after it has been set and saved as Confirmed.
CFGLockCancelledRequirements	Prevents setting the status of a Bunker Requirement to any other status after it has been set and saved as Cancelled.
CFGRequireFieldsInBunkerReqs	Enter a comma-separated list of of fields that are required in Bunker Requirements. Possible fields: company, reqQty, vessel, port, and requestedDeliveryDate.
CFGLockPortNameInBunkerReqs	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.
CFGRestrictBunkerRequirementToOneInquiryLine	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.
CFGRequireReqDelDateInStandaloneBnkrReqs	When enabled, the Requested Delivery Date field is a required field on Bunker Requirements that are not attached to a voyage.
CFGEnableVeslinkBunkeringFormDateSync	When enabled, upon submission and approval of a Veslink Bunkering Form, the Bunkering Completed time and date field from that form will be synced with the Bunker Requirement Delivery field and the Bunker Invoice Delivery Date field, if they exist. If there are multiple Bunker Requirements for this port and fuel type, the one with the lower Requirement ID will be chosen.