Veslink has a number of special fields and controls defined, some with calculations, that are on the defined forms and that you can add to forms. When forms include these fields, the data is validated, to make sure that required data is entered and values are valid, before users can save the form. Examples of special fields are:

Date/Time Fields

Dates can be selected from a calendar and must be entered in the date format specified on the System Configuration page. The GMT offset appears next to the Time field; times must be entered in HH:MM format, like 08:10.

On the Arrival Notice or Departure Notice, other logic is associated with the Arrival and Departure fields. For example, on the Departure Notice, the Departure Date/Time updates the Departure Date/Time for the port call and changes the vessel's state from In Port to On Sea Passage.

On a form with a frequency of Daily (which generally means the Noon Report), Veslink issues a warning message if:

• The form has already been submitted for that date.

• A form was not submitted for the previous date, unless it was outside the current voyage or unless the form is required only when the vessel is in passage, and it is not in passage.

Latitude and Longitude Fields

These fields accept both decimal and degree formats, as shown in placeholder text in the fields; they also accept negative values for directions corresponding to South or West.

Weather Fields

• Arrival Notice and Departure Notice weather fields:

  Open

  

• Noon Report weather fields:

  Open

  

Notes:

• Bad Weather Hours: This field maps to Bad Weather hrs on IMOS Activity Reports.

• Sea Height: This number must be entered in decimal format.

• Swell Height: This number must be entered in decimal format.

• Current: Current speed, in knots (Noon Report only).

• Current Direction: With or Against (Noon Report only).

Cargo Handling Control

The Cargo Handling control is a grid on the Cargo Handling form with a line for each cargo, where you can record the details of cargo being loaded or discharged. The control can manage two or more cargoes with the same type and operation, or multiple liftings of the same cargo in a port. 

For Time Charter Out Voyages, you can submit a Cargo Handling form for a port with multiple Cargo Handling lines having the same Cargo name.

Open

In the Cargo Handling control, to add a cargo, click the bottom line of the grid. The control includes the following fields:

• Cargo: When you select from the current cargoes, additional fields appear:

  • Alternative unit figures: You can select a Unit and enter the BL Gross and/or Ship Gross figures corresponding to that unit.

  • Charterer

  • Consignee

  • Receiver

  • Shipper

  • Destination

  • Letter of Protest

• Berth

• L/D: Port Function: L (Load) or D (Discharge).

• BL Code: Bill of Lading code.

• BL/Disch Date: Bill of Lading or Discharge date.

• Unit

• BL Gross: Quantity of cargo loaded, according to the Bill of Lading.

• Ship Gross: Vessel gross capacity.

When a form is approved that has a Cargo Handling control, Cargo and Cargo ID populate in the IMOS Veslink Forms List and Voyage Manager Veslink Forms tab.

For Bunkering

The Bunkers ROB, Event ROBs, and Bunker Consumptions controls, Bunker Tanks table, and Bunkering field enable Masters to send detailed fuel-consumption information to shore.

These controls and field display Fuel Types and consumption categories specified as applicable to the particular Vessel Type (for Veslink only) or IMOS Vessel.

Bunkers ROB Control

The Bunkers ROB control is a grid with information for each Fuel Type applicable to the particular vessel. For each Fuel Type, the control displays the Last ROB amount and the Unit of measure. The ROB control can capture ROBs by sulfur content within a particular Fuel Type. It can also capture auxiliary-engine fuel consumption separately from main-engine fuel consumption.

Each ROB control is associated with a Date/Time field on the same form that tells the date and time when the ROB readings were effective. If a form includes more than one ROB control, each must be associated with a Date/Time field. The Date/Time entry must be completed before the ROB value can be entered.

Veslink performs validations to ensure that the ROB quantity entered does not exceed the sum of the last previous ROB quantity plus any subsequent bunkerings. These validations are based on chronological sequence, so careful attention must be paid to the dates/times given for each ROB and bunkering entry.

Data for fuel consumption can be further defined by engine breakdown.

Open

Unless Use Basic Consumption is selected for the Form Group, the Consumption column includes:

• Main: Protected, calculated as the difference between Total and Aux.

• Aux: Editable.

• Total: Editable, required.

In the Used For section, the Adj field is protected, calculated as the difference between Total under Consumption and the sum of all quantities in the section.

When an Offline Form containing an ROB control is imported into Veslink, data entered into the Consumption section is validated. Veslink calculates consumption values by taking the difference between the current ROB values and the previously recorded ROB values, and compares these values to those entered. If there is a discrepancy between the two values (calculated versus user-entered), the calculated value takes precedence: the Main value is recalculated, and the Aux value continues to display what the user entered. The Total field is highlighted in red with a tooltip that displays the calculated value and the value entered. After approval of the form, if necessary, the fuel values will be updated. 

Example: The ROB of IFO as of Jan. 1 at 8:00 a.m. is 100 MT. Another 500 MT of IFO is added on January 2 at 10:00 a.m., for a total of 600 MT. The system would permit entering an ROB quantity of 590 MT as of January 2 at 10:30 a.m., but not as of January 2 at 9:30 a.m., which is before the bunkering time, so the quantity would remain 100 MT.

The Consumed amount is calculated, except under these conditions:

• This is the first ROB entry for the Fuel Type.

• This is the first ROB entry for the voyage, and the voyage is not consecutive.

• If the current ROB entered is greater than the Last ROB amount, a message to complete a Bunkering form appears. Until the bunkering information is entered, a draft of the original form can be saved, but the form cannot be submitted.

• In addition to entering the total ROB amount, the breakdown of the system-calculated consumption value across various categories (Propulsion, Generator, etc.) can be specified. The system automatically calculates an adjustment to balance the category breakdown with the total consumption. However, if all fuel Consumption Breakdown categories have been disabled, the bunker Consumption Breakdown categories do not appear.

Event ROBs Control

The Event ROBs control records Bunkers ROB for specific events and time frames.

Open

Bunker Consumptions Control