IMOS - Bunker Requirement

Home > Bunkering > Bunker Requirement

Bunker Requirement List

The Bunker Requirement List is the primary work list for processing Bunker Requirements. Bunker Requirements might come from operators or from vessels, through forms (voyage reports).

On the main menu
, under Operations, next to Bunker, click List.
On the Operations menu
, under Bunkers, next to Bunker Requirement, click List.
In the Operations quick links, click
.

Rows are highlighted according to the Operations Lists Settings:

Yellow = Requirements within the Bunker Warning Days
Red = Requirements within the Bunker Alert Days
- As with any other list, you can search, select, adjust, pin, filter, group, and sort columns, reset to the default view, save user views, and export.

By default, the following filters are applied, but you can change them:
- Request Date is on or after 90 days in the past
- Request Status is not Cancelled

Bunker Manager

You can use this list to see the bunkers that will be needed for upcoming voyage itineraries.

To create a work list, create a view that has the columns you want to see and exclude other bunker managers, so you see only your own work.

To have the most critical requirements appear at the top of the list, sort by the ETA column or the Window From column. You can open a voyage to find other information.

Operator or Vessel

You can use the Bunker Requirement List to check on the status of a Bunker Requirement.

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.

To view an existing Bunker Requirement, on the Bunker Requirement List, click its row or Requirement ID link.

To create a new Bunker Requirement, do one of the following:

From Voyage Details:
- On the Voyage Bunkers form:
  - Click New Requirement.
  - On a bunker type-specific detail tab, right-click a port call and then click New Bunker Requirement.
- On the Bunkers, Port/Date, or Consumption tab of the Itinerary, right-click the port line, hover over Bunker Requirements, and then click New Bunker Requirement.
On the Bunker Requirement List, click +.
On the Bunker Purchase List or Bunker Lifting List, click + and then click New Bunker Requirement.
On the main menu
, under Operations, click Bunker.
On the Operations menu
, under Bunkers, click Bunker Requirement.

It is possible to have multiple Bunker Requirements per port call; you can also view any others on the form.

Request Status, Requested By, Procurement Status, Bunker Manager, and Request Note fields are only available to clients with the Bunkering module.

As with any other details view, you can navigate to a different record by clicking its card or return to the list by clicking its Name.
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.
The selection of vendors in the Agent field is limited to the nominated agents specified for the port call.

Voyage Reporting provides a different form for entering bunker requirements.

Port Expenses

When port expenses are entered on the Bunker Requirement form, they contribute to the Total cost of a given bunker lifting, which will be reflected in the Bunker Details Report.

Related Configuration Flags

Name/Flag	Description
Change Paid By or For Account to either TCI Owner or TCO Charterer CFGEnableNonOperatorBunkerPurchases	When enabled, you can change the Paid By or For Account fields to either TCI Owner or TCO Charterer and the record will stay linked with the Bunker Purchase. Bunker Invoices paid by TCI Owner/TCO Charterer cannot be invoiced.
Enable Vessel Bunker Grade 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.
Require Agents to Confirm Requirement CFGRequireAgentsToConfirmRequirement	Requires values for Port Agents when confirming a Bunker Requirement.
Verify Matching Company CFGVerifyMatchingCompany	Displays a validation error if any of a voyage's or Estimate's linked contracts or Bunker Requirements has a different Company set than the voyage company.
Lock Confirmed Requirements CFGLockConfirmedRequirements	Prevents setting the status of a Bunker Requirement back to Preliminary after it has been set and saved as Confirmed.
Lock Cancelled Requirements CFGLockCancelledRequirements	Prevents setting the status of a Bunker Requirement to any other status after it has been set and saved as Cancelled.
Require Fields in Bunker Requirements CFGRequireFieldsInBunkerReqs	Enter a comma-separated list of of fields that are required in Bunker Requirements. Possible fields: company, reqQty, vessel, port, and requestedDeliveryDate.
Lock Port Name in Bunker Requirements 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.
Restrict Bunker Requirement to One 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.
Require Requirement Del Date in Standalone Bunker Requirements CFGRequireReqDelDateInStandaloneBnkrReqs	When enabled, the Requested Delivery Date field is a required field on Bunker Requirements that are not attached to a voyage.
Enable Veslink Bunkering Form Date Sync 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 requirements for the given port call, it updates each one of them. If there are multiple Bunker Requirements for this port, IMOS chooses the first one to sync to (the one with the lower Requirement ID for that port with that fuel type). If the Bunker Requirement Request Status is Canceled, or if Procurement Status is Completed or Canceled, IMOS will not update the Bunker Requirement's Delivery date.
Show Bunker Quantity Range on Requirement CFGShowBunkerQtyRangeOnReq	When enabled, the min/max values for each fuel type will be added to the Inquiries and Purchases grid on the Bunker Requirement form.