RECORDER

// USER MANUAL
Release 2.10.0
Date: February/2024

Prepared by: StormGeo

© StormGeo AS. All rights reserved

This publication or parts thereof may not be reproduced or transmitted in any form or by any means, including
copying or recording, without the prior written consent of StormGeo AS
// Table of Contents

1 What is s-Insight | Log Recorder?

........................................................................................................................................ 1

2 Getting started
........................................................................................................................................ 1
2.1 Importing a configuration
.......................................................................................................................................... 1
2.2 Login
.......................................................................................................................................... 3
2.3 Initializing
.......................................................................................................................................... 3

3 Daily use
........................................................................................................................................ 6
3.1 Navigation within the program
.......................................................................................................................................... 6

3.2 Reporting sequence

.......................................................................................................................................... 6
3.2.1 Standard conventions used in s-Insight | Log 6
..........................................................................................................................................
3.2.2 Port-to-port leg - standard 7
..........................................................................................................................................
3.2.3 Port-to-port leg - with stoppage 8
..........................................................................................................................................
3.2.4 Port-to-port leg - with stoppage and maneuvering 8
..........................................................................................................................................
3.2.5 Port-to-port leg - with anchorage/drifting prior berthing 9
..........................................................................................................................................
3.2.6 Standard port call 9
..........................................................................................................................................
3.3 Filing new events 10
..........................................................................................................................................
3.4 Entering cargo details 13
..........................................................................................................................................
3.5 Working with port logs 14
..........................................................................................................................................
3.6 Cargo in the departure event 15
..........................................................................................................................................
3.7 Performance snapshot 17
..........................................................................................................................................
3.8 Consumption breakdown 20
..........................................................................................................................................
3.9 Fuels
..........................................................................................................................................20
3.9.1 Biofuel Reporting Model 22
..........................................................................................................................................
[Link] Fuel Types 22
......................................................................................................................................
[Link] Bunkering Overview 25
......................................................................................................................................
[Link] Fuel Blend Logic 29
......................................................................................................................................
[Link] Reporting Examples 33
......................................................................................................................................
[Link].1 Example 1: bunkering a new biofuel blend (Fossil + Biofuel with a single
PoS) into an empty tank 34
..................................................................................................................................
[Link].2 Example 2: bunkering a new biofuel blend (Fossil + Biofuel with single
PoS) into non-empty tank - Topping up: 38
..................................................................................................................................
[Link].3 Example 3: bunkering a new biofuel blend (Fossil + Biofuel with 2
separate PoS certificates) into an empty tank 40
..................................................................................................................................
3.10 Drafting of events 43
..........................................................................................................................................
3.11 Modifying or deleting events 43
..........................................................................................................................................
3.12 Modify the current Master / Chief Engineer 44
..........................................................................................................................................
3.13 Voyages
..........................................................................................................................................44
3.13.1 Voyage stage logic 45
..........................................................................................................................................
3.13.2 Entering a new voyage 47
..........................................................................................................................................
3.13.3 Modify an existing voyage 48
..........................................................................................................................................

StormGeo . USER MANUAL . s-Insight | Log // I

3.13.4 Deleting a voyage 48
..........................................................................................................................................
3.13.5 Speed orders 48
..........................................................................................................................................
3.14 Schedule and Agents 49
..........................................................................................................................................
3.15 Garbage Record Book 51
..........................................................................................................................................
3.16 Off-hire
..........................................................................................................................................52
3.17 Sending data 54
..........................................................................................................................................

4 Non-daily tasks 54
........................................................................................................................................
4.1 Log Abstract onboard 54
..........................................................................................................................................
4.2 Inserting events 55
..........................................................................................................................................
4.3 Re-sending data 55
..........................................................................................................................................
4.4 Loading a new configuration 56
..........................................................................................................................................
4.5 Unsent events 57
..........................................................................................................................................
4.6 Copy the whole installation to another PC 57
..........................................................................................................................................
4.7 Backup
..........................................................................................................................................58

5 Overview of event types 59

........................................................................................................................................
5.1 Voyage Events 59
..........................................................................................................................................
5.2 Special Events 60
..........................................................................................................................................
5.3 Operational Events 62
..........................................................................................................................................

6 CII........................................................................................................................................
reporting guidelines 63
6.1 Deviation due to Emergency 63
..........................................................................................................................................
6.2 Time sailed in ice 65
..........................................................................................................................................
6.3 STS voyage for tankers 66
..........................................................................................................................................
6.4 Reefer consumption 68
..........................................................................................................................................
6.5 Cargo Cooling & Reliquification Systems on Gas/LNG
..........................................................................................................................................69
Carriers
6.6 Electric Cargo discharge pumps on tankers 71
..........................................................................................................................................
6.7 Boiler consumption for cargo heating and discharge pumps
on tankers 72
..........................................................................................................................................
6.8 Other discharge pumps on tankers 72
..........................................................................................................................................
6.9 CII reporting overview 73
..........................................................................................................................................

7 eLogbook integration 74
........................................................................................................................................

8 Troubleshooting
........................................................................................................................................79
8.1 Access denied 79
..........................................................................................................................................
8.2 Installation
..........................................................................................................................................80
8.2.1 General 80
..........................................................................................................................................
8.2.2 Installer settings cannot be stored 80
..........................................................................................................................................
8.2.3 Upgrading to a new a version 80
..........................................................................................................................................
8.2.4 Configuration import fails 81
..........................................................................................................................................
8.2.5 Configuration not up-to-date 81
..........................................................................................................................................

// II StormGeo . USER MANUAL . s-Insight | Log

8.3 Login
..........................................................................................................................................81
8.3.1 Invalid password 81
..........................................................................................................................................
8.3.2 Incompatible DB 82
..........................................................................................................................................
8.4 Event overview 82
..........................................................................................................................................
8.4.1 Events are disappearing 82
..........................................................................................................................................
8.4.2 The 'Information' box is not showing correct values 82
..........................................................................................................................................
8.4.3 The 'Remaining on board' box is not showing the correct values 82
..........................................................................................................................................
8.4.4 The event menu shows some events grey (with a '?' next to them) 83
..........................................................................................................................................
8.5 Edit Voyages 83
..........................................................................................................................................
8.5.1 Cannot delete a voyage 83
..........................................................................................................................................
8.5.2 Invalid voyage name 83
..........................................................................................................................................
8.5.3 Red fields appear on the right side, the voyage cannot be saved 83
..........................................................................................................................................
8.5.4 After configuration import new values, e.g. new services, are still missing 84
..........................................................................................................................................
8.6 Entering events 84
..........................................................................................................................................
8.6.1 Durations fields are complaining 84
..........................................................................................................................................
8.6.2 Port field is complaining 84
..........................................................................................................................................
8.6.3 Too many (or wrong) red/blue boxes appear upon pressing the 'Check' button 84
..........................................................................................................................................
8.6.4 Numeric values lose their precision when leaving the field 85
..........................................................................................................................................
8.6.5 After configuration import new values, e.g. new services, are still missing 85
..........................................................................................................................................
8.7 Sending reports 85
..........................................................................................................................................
8.7.1 Some reports are not sent 85
..........................................................................................................................................
8.7.2 'Voyage' events 85
..........................................................................................................................................
8.7.3 Errors when sending reports 85
..........................................................................................................................................
8.7.4 Missing reports 85
..........................................................................................................................................

9 Getting support 86
........................................................................................................................................
9.1 Installation problems 86
..........................................................................................................................................
9.2 Application problems 86
..........................................................................................................................................
9.3 Support tool 86
..........................................................................................................................................

10 Appendix
........................................................................................................................................87
10.1 System requirements 87
..........................................................................................................................................
10.2 Known issues 88
..........................................................................................................................................
10.3 Reporting instructions 89
..........................................................................................................................................
10.4 Third party licenses 89
..........................................................................................................................................
10.5 Trademark legal notice 89
..........................................................................................................................................

StormGeo . USER MANUAL . s-Insight | Log // III

1 What is s-Insight | Log Recorder?

s-Insight | Log Recorder is the on board component of s-Insight | Log collecting fleet wide voyage
and emission relevant data.

onboard onshore

Position/ Noon reports,

Arrival, Departure, etc.
(push message e-mails)

Log abstracts, overviews

s-Insight | Log
Recorder

Environmental reporting
· EU MRV
· EU ETS
s-Insight | Log · CII
Server · Compliance with ECAs
and MARPOL areas

Data collected by s-Insight | Log Recorder is stored and is available for various evaluations onshore
in s-Insight | Log Server.

Another purpose of s-Insight | Log Server is to push forward dedicated data to designated e-mail
recipients whenever new voyage data is received from s-Insight | Log Recorder . One aim of s-
Insight | Log is to replace the traditional voyage data recording (e.g. plain e-mails, spreadsheets,
etc.).

2 Getting started

The following chapters describe how s-Insight | Log Recorder is configured for the first time, i.e. after
(re-)installing the application without an existing data path.

2.1 Importing a configuration

When starting the program the first time it is necessary to request a ship configuration.

// 1 StormGeo . USER MANUAL . s-Insight | Log

Fill out the form below and chose a method for sending the request.

This request can be sent directly with your e-mail application. Alternatively, the request file can be
saved to disk and then sent manually. Ask your IT department for the email address of your
dedicated s-Insight | Log Server if necessary.

s-Insight | Log Server will identify your vessel by IMO number and will send a configuration file to the
e-mail address configured by your IT department. In case you do not receive an answer, please send
another request until the server will respond.

The e-mail received from the server will contain password and configuration file as attachment. Save
the attachment to disk and press 'Import configuration'.

· select the configuration file and click 'Open'

· a login screen will appear showing name and IMO number of your vessel

Please note: You cannot import configuration files that were not requested. See Configuration import
fails for details.

StormGeo . USER MANUAL . s-Insight | Log // 2

2.2 Login
To login, enter the password received by e-mail. If you did not receive a password, ask your shore
IT department.

2.3 Initializing
A wizard guides you through the initial setup of s-Insight | Log Recorder ensuring a complete and
consistent reporting on the first voyage leg. It is available for initial setup and re-initialization. In
both cases, a configuration from s-Insight | Log Server is required as input.

Essential data like current amount of fuels, consumables, cargo, officer names and position of the
vessel need to be stated. Last know values from s-Insight | Log Server are shown as default values
if applicable. Click “Next” to accept or “Clear” to delete all inputs. Use the buttons on the bottom for
navigation. Subsequent modifications to the data are possible.

// 3 StormGeo . USER MANUAL . s-Insight | Log

StormGeo . USER MANUAL . s-Insight | Log // 4
// 5 StormGeo . USER MANUAL . s-Insight | Log
3 Daily use

3.1 Navigation within the program

On program start, all events of a voyage will be displayed (usually the one used previously). The
current item selected from the menu is highlighted.

Available pages are:

· Voyages: add/ enter/ delete voyage data, including dates, ports, stages and the current
service

· Schedule: enter your coastal or long-term schedule to keep the office up to date

· Agents: enter details of agents to be used in coastal or long-term schedule

· Events: review/ enter/ delete event data

· Port logs*: edit port log entries

· Officers: specify the current Master and Chief Engineer and review the previous ones

· Cargo*: manage bills of lading (B/L) and cargo details

· Reports: all reports available onboard, currently Garbage Record Book

· Communication: send event reports to shore from here

· Settings: program settings and configuration

(*: only visible for tankers and bulk carriers)

3.2 Reporting sequence

For reporting with s-Insight | Log you have to follow guidelines for sequences of events and also
follow special conventions.

3.2.1 Standard conventions used in s-Insight | Log

Arrival - the time of all fast. First line ashore and FWE - Finish With Engine can reported within the
event separately

BOSP - Begin Of Sea Passage also known as Full Away, F.A. or COSP - Commence Of Sea Passage

StormGeo . USER MANUAL . s-Insight | Log // 6

Departure - the time of begin unberthing. Stand-by engine and last line off can reported within the
event separately

EOSP - End Of Sea Passage

Noon - the standard position report also known as daily report. Typically, it is created at 12:00 LT. In
s-Insight | Log there are Noon (Position) reports for Sea Passage, River, Port, and Stoppage.

River - defines the period where the vessel is neither on sea passage, nor port or at stoppage;
usually the vessel is maneuvering.

Consistent event sequences are required for MRV compliant reports and for any data analysis. To
enforce such a reporting, new events can be created by default only if they are consistent with the
latest event. If, for any reason another event must be created, e.g. to be inserting between existing
events, "Show more..." can be used to enable creation of hidden entries.

3.2.2 Port-to-port leg - standard

A standard port-to-port leg without any stoppage/anchoring

// 7 StormGeo . USER MANUAL . s-Insight | Log

The time between departure and BOSP event is automatically considered as river. Here, for reporting
noon events use the Noon (Position) - River event. The same applies for the time between EOSP and
Arrival event.

All noon events between BOSP and EOSP are to be reported as Noon (Position) - Sea Passage.
Between Arrival and Departure the vessel is in port and only Noon (Position) - Port events shall be
created.

3.2.3 Port-to-port leg - with stoppage

A standard port-to-port leg with one stoppage/anchoring

If the vessel has to stop during a sea passage it can be reported in two ways - either by tracking the
period of slowing down with adding this time to the river passage (maneuvering) see next chapter,
or you can report a Begin Anchoring / Drifting event directly and follow the sequence above. If you
want to report a noon report during the stoppage period please use the Noon (Position) - Stoppage.

3.2.4 Port-to-port leg - with stoppage and maneuvering

A standard port-to-port leg with one stoppage/anchoring and recording the maneuvering period

StormGeo . USER MANUAL . s-Insight | Log // 8

By reporting an EOSP event before the Begin of stoppage event and after the stoppage a BOSP
event the times will be recorded as maneuvering (e.g. river) periods.

3.2.5 Port-to-port leg - with anchorage/drifting prior berthing

A standard port-to-port leg with anchoring/drifting prior berthing

In case the vessel has to drift or drop the anchor prior berthing you can complete your sea passage
with an EOSP event and start to report the anchoring/drifting time with a Begin of Anchoring/Drifting
event. Use the End Anchoring/Drifting event with anchor aweigh or continue approaching to berth.

3.2.6 Standard port call

A standard port call with an optional noon event.

// 9 StormGeo . USER MANUAL . s-Insight | Log

The port period will start with the reported time of the arrival event (all fast) and will end with the
reported time of the departure event (begin unberthing).

Within a the port call Noon (Position) - Port events can be reported. If the vessel is changing only the
terminal or pier a shifting event should be used.

3.3 Filing new events

To enter new events follow these steps:

1. Select 'Events' from menu.

2. Press one of the 'New ... ... event' buttons and select the event you want to file.

By default the menu only shows events that are matching the reporting sequence. You want to
enter an event that is not shown please double check that all previous events have been
entered properly. For more details see Reporting sequence.

3. Enter event time and time zone. A time line shows where the new event will be placed:

Note: When changing the time such that the event swaps place with another event, make
sure to double check surrounding events. When you do not enter events in the order of
occurrence it can easily happen that you enter wrong data (e.g. with fuel consumptions
since last event).

By default all reports use local time.

StormGeo . USER MANUAL . s-Insight | Log // 10

 By clicking you can easily change the input to UTC. Moving the mouse over the date/time
field will show UTC if the input is local time (LT) and vice versa. The timezone must be selected
from the drop-down menu.

4. The screen now changes and shows the event details

· On top of each event you can enter additional recipients for notification of this event.

Note: The standard setup of recipients is done in s-Insight | Log Server.

· Some fields have a copy button attached. Such a button may be used to copy values from
somewhere else (e.g. the ETA port from the last ETA update) reduce manual input.

· Some fields have a 'Calculator' button attached that will calculate the value based on other
entered data.

· In some events you may skip entering consumptions and/or machinery operations (and/or
fresh water consumption and operations, where applicable). Where this is possible you will
find the box 'Consumptions are intentionally not reported in this event' on top of the
consumptions:

When you check this box, consumptions and/or machinery operations (and/or fresh water) will
turn grey. All following events will also skip the current event when calculating durations. Use
this option in case events are following each other very closely, and entered values would be
very low.

The maximum time between events for this to work is configured onshore and is also shown in
a tooltip on the checkbox (put your mouse cursor on it and wait).

Note: Special area events have this option, but if you enter/leave an area that requires
consumptions you may not use it. Watch out for the red check results on the right when
checking your data prior to saving the event.

· All events that allow reporting consumptions also have a Check ROB box inside. Here you may
directly see the results of your consumptions.

You may also add consumptions to a virtual consumer, or even delete fuels from the system,
but beware that this is only possible for small amounts of fuel.

Please note that fuels cannot be consumed if there was no type, sulphur content or mass
specified upon bunkering/ mixing/ initializing - where those details are missing the fuel is
hidden from the list.

· The weather shall be reported in all events as the prevailing weather since last time reported.
Exception is performance snapshot event that requires the current weather of the event time.

// 11 StormGeo . USER MANUAL . s-Insight | Log

· Some boxes in the event are not opened immediately. Instead you only see the headline with
a 'plus' sign left of it. Click on this 'plus' to expand the box and reveal the input fields:

· When you're done you can immediately save, or press the check button first before saving:

When checking the event the check results are shown on the right side of the screen.

o Red fields indicate errors in your event. Correct those errors, otherwise you will not be
able to send the event (the server is unable to understand incomplete messages).

o Blue fields indicate issues that should be reviewed and/or fixed prior to sending. Although
it is possible to send the event anyway (in case time is short) it is highly recommended to
fix these issues, otherwise it may be hard to impossible to interpret the entered data.

o Green fields indicate information that might need further actions, but do not affect the
event's plausibility check status. For instance, when leaving the turn port of your current
round voyage you should check your current voyage (to add a new voyage stage).

Each check result can be expanded to see more details:

· You will now return to the 'Events' page. Please note the 'Value check' column which also
shows if there are errors left in the event. In case you have not checked the event prior to
saving it make sure to return to the event before sending it:

StormGeo . USER MANUAL . s-Insight | Log // 12

A note on the window's [X]-button (close-button): In the event view the button will not close the
application, but leave the editing view instead.

3.4 Entering cargo details

To enter cargo details, select 'Cargo' from the menu.

Note: this section applies to bulk carriers, tankers, LNG and gas carriers only, is not visible for other
ship types.

The 'Status' column also shows throughout time how the cargo changes (fully loaded - yellow, fully
unloaded - green, etc.)

Click 'New B/L' to enter details about the Bill of Lading and associated cargo details.

Depending on your owner/operator it is possible to enter beside the general cargo type also specific
cargo types.

In both cases you have to enter a density for each cargo.

// 13 StormGeo . USER MANUAL . s-Insight | Log

In the departure event or in the port log you can enter loading or unloading operations for all known
cargo.

Remember to always use the calculator button to have the correct total
mass onboard.

3.5 Working with port logs

Whenever an arrival or shifting event is created, a port log entry is generated automatically. You can
see the port logs in the event overview:

Click on "Port log" to open the port log that starts with the respective event. You can also select
'Port logs' from the menu, and select the port log by time and port.

In a port log you may enter:

· port facts (e.g. notice of readiness, cargo tank survey times, ...)

· delays incl. reasons

· loading or unloading of cargoes

· remarks (free text)

To add or remove cargoes use the tabs and buttons on the left side of the screen (right of the
navigation):

StormGeo . USER MANUAL . s-Insight | Log // 14

Press the next to a cargo to remove it from the port log, press the 'Add entry' button to include
cargo to this port log.

Once a cargo has been added to the port log you can start entering loading or unloading operations
for this cargo.

If the selected cargo was already onboard the system will automatically set the toggle button to
discharge .

By pressing this button it will change to loading and a location must be selected.

Every cargo operation you enter here will be automatically filled in the departure event.

Remember to use the calculator button in the departure event to get the correct total mass onboard
.

3.6 Cargo in the departure event

If either not port log with cargo details was created or corrections must be applied you can use the
cargo section in the departure event.

By clicking the a new location (tank or cargo hold) and a cargo must be selected. The 'Content old'
column shows the quantity of cargo which was in that tank/hold before the departure event was
created. If cargo operations had been entered in the port log the content of that operation is stated
here. For corrections the 'Loaded/Discharged' data field can be used. If not port log is used for
recording cargo operations all details can be entered also directly here in the departure event. Press
on the toggle button to either add cargo or to remove cargo .

Content actual must be updated accordingly with the help of the calculator button .

Note: press the calculator button for the total mass onboard

If you do not report specific cargo types but want to be EU-MRV compliant it is possible to enter
directly the total mass onboard.

For general cargo vessels, mass of cargo onboard as well as deadweight (MRV) are to be reported
on departure.

// 15 StormGeo . USER MANUAL . s-Insight | Log

For ConRo vessels, cargo volume (MRV) is to be reported.

If during a port call the total amount of cargo onboard does not change and no cargo operations are
reported, then a warning is issued in the respective departure or shifting. In case of missing input
this shall be fixed. In case the port was called for other reasons, e.g. bunkering crew change or
waste disposal, this can be stated explicitly in Departure or Shifting events to switch of any related
checks.

For passenger vessels, the same mechanism was implemented for “no change of passengers”.

To ensure consistent reporting of cargo operations and total amounts for container vessels and unit
cargo carriers, information about the amount cargo before the operation is displayed in Departure
and Shifting events.

StormGeo . USER MANUAL . s-Insight | Log // 16

3.7 Performance snapshot
For hull & propeller and engine & systems condition analysis it is preferable not to use average
values, e.g. for power and speed through water (STW), but instantaneous values, so the current
STW, current power and current weather at this point in time. This increases validity of the complex
analytics later. For this there is a special event 'performance snapshot' in s-Insight | Log.

When to fill the event

Once per day is sufficient. You can do this together with a normal noon report procedure. Please
make sure the values are not the sum or average since the last noon report but the current
instantaneous values.

What does the performance snapshot consist of

The event starts with the sailing conditions. Here position, speed over ground, speed through
water and draughts are important:

The weather shall be entered contrary to all other events for the present time of the event.

// 17 StormGeo . USER MANUAL . s-Insight | Log

Engine performance data and propulsion power can be reported independently. This enables a
more frequent reporting of propulsion power for performance assessment of hull and propeller,
e.g. by the respective module in ECO Insight.

For hull & propeller condition analysis only sailing conditions and weather data is needed, while
engine performance data do not have to be specified.

Customers mainly interested in engine condition monitoring, can report engine performance data
only. These data are similar to a typical monthly engine performance test. The same applies for
all auxiliary engines. At the bottom of the report and also only relevant for engine condition

StormGeo . USER MANUAL . s-Insight | Log // 18

 please enter the seawater temperatures. They are needed for the ISO correction of measured
consumption values. Propulsion power is reported per individual propulsion train. Please note,
that separating M/E power and propulsion power accounts for power losses between M/E flange
and the propeller.

// 19 StormGeo . USER MANUAL . s-Insight | Log

3.8 Consumption breakdown
Breaking down consumptions by purpose can be useful for subsequent analysis.

This option is only available when enabled on s-Insight | Log Server.

After importing the new configuration, a new column “Used for” is shown for consumptions, allowing
to select values from a given list. One value can be selected per individual entry. There are many
predefined purposes e.g. Maneuvering, Discharging, and Inerting. If not configured otherwise, the
input can be left blank.

To break down a consumption by purpose, multiple entries can be created for the same fuel.
Purposes can be specified for auxiliary engines, boilers and main generator engines.

The total consumption per consumer group is shown next to the group name.

3.9 Fuels
New sulphur limits introduced by IMO regulation “Sulphur Cap 2020” are supported.

The following fuel categories according to sulphur limits were introduced by IMO, see the table
below.

Category Shortcut Sulphur

High sulphur HS > 0.5%

Very low sulphur VLS 0.1% to 0.5%

Ultra-low sulphur ULS <= 0.1%

The Information panel as well as the Check ROB control are using the new categories for Bio-diesel,
HVO, Gas/Alcohol, Other (Biofuel), LFO/HFO, MDO/MGO and Blend fuels.

StormGeo . USER MANUAL . s-Insight | Log // 20

New fuels are emerging in the market to comply with the new regulation. Those fuels show a much
wider spread of values regarding viscosity and density. Further, their lower heating value (LHV)
tends to be higher than previously. Hence, warning limits are adjusted accordingly.

Also, for boil off gases the lower limits for LHV and HHV were adjusted to reflect a wider spread of
quality in the market and different percentage of nitrogen share.

ISO 8217 for marine fuels is still valid and engine manufacturers recommend ordering according to
this specification. However, it is observed that bunker suppliers often refer to a fuel as “VLSFO” in
the BDN. In this case, chose the fuel grade with best matching viscosity when creating a bunker
event.

With new sulphur categories introduced, reporting of cylinder oil is now classified by high and low
base numbers, respectively. It is left to the discretion of the customer how to split between high and
low base numbers.

Since 2020-01-01 high sulphur fuels can only be used, when operating scrubbers.

Running hours of scrubbers can be reported for all events with machinery operations. For this,
scrubbers must be configured as components in s-Insight | Log Server. For hybrid scrubbers running
hours in open and closed loop can be reported separately.

For scrubbers supporting closed loop operation, the amount of chemicals used can be reported.
Furthermore, bunkering, sounding correction, and de-bunkering of chemicals can be reported.

// 21 StormGeo . USER MANUAL . s-Insight | Log

For hybrid or close loop scrubbers, the amount of scrubber sludge can be reported under Tank
soundings in Noon reports. For this, a scrubber sludge tank must be configured on s-Insight | Log
Server.

The disposal of scrubber sludge can now be reported in all disposal events.

“Exhaust gas cleaning” was introduced as new reason for fuel consumption and surplus
consumption, respectively.

A new feature allows reporting the amount of fuel sludge produced per consumption of conventional
fuel (HFO, MDO/MGO). The reported amount is deducted from the fuel ROB automatically thereby
reducing the need of sounding corrections. Fuel sludge is not considered as consumption and
thereby excluded from CO2 emissions.

Fuel sludge shall not exceed 2% of the related consumption, otherwise an error message is issued.
The default severity of this message can be customized, or the check can be disabled on s-Insight |
Log Server.

Reported values can be used in push messages.

Currently, reported fuel sludge is not linked to tank soundings of sludge tanks.

3.9.1 Biofuel Reporting Model

We have enhanced the s-Insight | Log Recorder to meet the latest regulatory requirements of the EU
ETS/MRV and IMO DCS/CII for biofuels. This ensures that our system is fully compliant with these
regulations, providing reliable and accurate reporting.

[Link] Fuel Types

Full list of Biofuel types and Raw materials that were added:

Fuel Fuel Fuel Type Type of Raw material Comment

Class Category

Biofuel Bio-diesel Bio-diesel Pure vegetable oil (oil produced from oil
plants through pressing, extraction or
comparable procedures, crude or refined
but chemically unmodified)

Biofuel Bio-diesel Bio-diesel POME (palm oil methyl ester or palm oil
mill effluent)

StormGeo . USER MANUAL . s-Insight | Log // 22

 Fuel Fuel Fuel Type Type of Raw material Comment
Class Category

Biofuel Bio-diesel Bio-diesel FAME (fatty acid methyl ester)

Biofuel Bio-diesel Bio-diesel Rapeseed biodiesel

Biofuel Bio-diesel Bio-diesel Sunflower biodiesel

Biofuel Bio-diesel Bio-diesel Soybean biodiesel

Biofuel Bio-diesel Bio-diesel Waste cooking oil biodiesel

Biofuel Bio-diesel Bio-diesel FAEE (fatty acid ethyl ester)

Biofuel HVO HVO Hydrotreated (thermochemically

treated with hydrogen) oil of biomass
origin, to be used for replacement of
diesel

Biofuel HVO HVO Hydrotreated vegetable oil from

rapeseed

Biofuel HVO HVO Hydrotreated vegetable oil from

sunflower

Biofuel HVO HVO Hydrotreated vegetable oil from

soybean

Biofuel HVO HVO Hydrotreated vegetable oil from palm oil

Biofuel HVO HVO Hydrotreated oil from waste cooking oil

Biofuel HVO HVO Hydrotreated oil (thermochemically

treated with hydrogen) of biomass
origin, to be used for replacement of
liquefied petroleum gas

Biofuel Alcohol Bio- Methanol from renewable sources

methanol

Biofuel Alcohol Bio-ethanol Ethanol from renewable sources

Biofuel Gaseous Bio-LNG Biogas that can be purified to natural gas

quality

Biofuel Gaseous Bio- Hydrogen from renewable sources

hydrogen

Biofuel Other Other Other Should be used only when

bunkered biofuel raw material
is not in the list

// 23 StormGeo . USER MANUAL . s-Insight | Log

All Fossil fuels that are available for Recorder version 2.10.0 are listed in the table below.

Fuel Class Fuel Category Fuel Type

Fossil LFO RMA10

Fossil LFO RMB30

Fossil LFO RMD80

Fossil HFO RME180

Fossil HFO RMG180

Fossil HFO RMG380

Fossil HFO RMG500

Fossil HFO RMG700

Fossil HFO RMK380

Fossil HFO RMK500

Fossil HFO RMK700

Fossil MDO/MGO DMX

Fossil MDO/MGO DMZ

Fossil MDO/MGO DMB

Fossil MDO/MGO DMA

Fossil MDO/MGO DMC

Fossil Gaseous LNG

Fossil Gaseous Ethane

Fossil Gaseous LPG (Propane)

Fossil Gaseous LPG (Butane)

Fossil Gaseous Hydrogen

Fossil Gaseous Ammonia

Fossil Alcohol Ethanol

Fossil Alcohol Methanol

StormGeo . USER MANUAL . s-Insight | Log // 24

Blend fuel type: additionally, fuel type ‘Blend’ is available, allowing vessels to report bunkering of a
blended fuel type. Example: 30% FAME (Bio-diesel) + 70% DMB (MDO/MGO). Please see chapter Fuel
Blend Logic for more details.

If a vessel plans to bunker only a few fuel types and/or raw materials, it is possible to limit the
number of fossil fuels and biofuels/raw materials available for onboard reporting. This can be
achieved by adjusting the vessel configuration inside the s-Insight | Log Server. Similarly, it is
possible to limit the consumption of each fuel type per engine.

[Link] Bunkering Overview

s-Insight | Log Recorder Bunkering and Fuel mixing events were updated with a new fuel reporting
template.

Bunkering in tanks considered as empty:

1. Bunkering a Fossil fuel type - this option should be used when 100% fossil fuel is bunkered.

// 25 StormGeo . USER MANUAL . s-Insight | Log

2. Bunkering a Biofuel type - this form allows user to select exact biofuel type and raw material of
the bunkered biofuel. This option should be used when 100% biofuel is bunkered:

Reporting of biofuel parameters is mandatory. This information should be available inside PoS
certificate for each related BDN. New biofuel parameters from PoS certificate that were added to
the Bunkering report:

a. Raw material

b. Certificate number

c. Energy content [MJ]

d. Total GHG emission intensity [gCO2e/MJ]

e. EU RED Compliant material [Yes/No]

Since vessel might not have Proof of Sustainability (PoS) certificate right after bunkering
operation, related mandatory validations will be triggered with 14 days delay.

StormGeo . USER MANUAL . s-Insight | Log // 26

3. Bunkering a Blend fuel type - when a blend fuel type is selected, then 2 additional rows are
showed for entering blend component #1 and #2. It is possible to have a blend of 2 biofuels, 2
fossil fuels or 1 fossil + 1 biofuel. Limitations are applied when blend component #1 and #2 are of
the same type, see Fuel Blend Logic for more details.

Bunkering in non-empty tanks / mixing (topping up of tanks):

Fuel top up template allows user to report topping up/mixing of Fossil, Biofuel and Blend fuel types.
The following data should be provided:

· Old fuel type - one of the fuels that are remaining on board and will be mixed with the new
bunkered fuel.

· New fuel type - fuel that will be used for topping up a tank with an existing fuel:

o User should select Fuel class, Fuel type and fill all mandatory parameters. Set of parameters is
dynamic, depending on the bunkered Fuel class (Fossil, Biofuel, Blend).

o In case a blend of 2 different fuels is being topped up, then user must provide details for blend
component #1 and #2, including related mass for each blend component and set of biofuel
parameters from PoS sertificate.

· Resulting fuel type - this is the result of mixing Old and New fuel types.

Limitations are applied when New fuel is a Blend and component #1 and #2 are of the same type.
Additionally, user should comply with fuel blend logic when selecting Old, New and Resulting fuel
types. See Fuel Blend Logic for more details.

// 27 StormGeo . USER MANUAL . s-Insight | Log

Example of topping up a 100% fossil fuel - RMG 500:

Example of topping up a 100% HVO biofuel with raw material - 'Hydrotreated oil from waste cooking
oil':

Example of topping up a biofuel blend:

StormGeo . USER MANUAL . s-Insight | Log // 28

Note: when reporting tank Top up or Fuel mixing, then BDN number of the resulting fuel type is
generated automatically.

[Link] Fuel Blend Logic

There are 3 scenarios when a Blend fuel type can be reported inside application:

1. Bunkering a fuel BDN which is already a blend.

2. Topping up a tank and creating new fuel blend.

3. Mixing 2 of existing BDNs to create a new fuel blend.

Validations were added for ensuring correct reporting and limiting user errors.

Logic description:

· When 2 fuels of the same type are mixed/blended, resulting fuel should also be of the same type,
but not reported as Blend.

· When 2 fuels of a different type are mixed/blended, then resulting fuel should always be Blend.

Please refer to this table, which describes fuel blend logic restrictions in more details:

Fuel Class Fuel Category Fuel Type Blend Restriction

RMA10

RMB30 When blended with other LFO, then resulting fuel = LFO.
LFO
Otherwise resulting = Blend.
RMD80

RME180

RMG180

Fossil RMG380

RMG500
When blended with other HFO, then resulting fuel = HFO.
HFO
Otherwise resulting = Blend.
RMG700

RMK380

RMK500

RMK700

// 29 StormGeo . USER MANUAL . s-Insight | Log

Fuel Class Fuel Category Fuel Type Blend Restriction

DMX

DMZ

DMB When blended with other MDO/MGO, then resulting fuel =

MDO/MGO
MDO/MGO. Otherwise resulting = Blend.
DMA

DMC

LNG When blended with other LNG, then resulting fuel = LNG.
Otherwise resulting = Blend.

Ethane When blended with other Ethane, then resulting fuel =

Ethane. Otherwise resulting = Blend.

LPG When blended with other LPG (Propane), then resulting fuel
(Propane) = LPG (Propane). Otherwise resulting = Blend.
Gaseous
LPG When blended with other LPG (Butane), then resulting fuel
(Butane) = LPG (Butane). Otherwise resulting = Blend.

Hydrogen When blended with other Hydrogen, then resulting fuel =

Hydrogen. Otherwise resulting = Blend.

Ammonia When blended with other Ammonia, then resulting fuel =

Ammonia. Otherwise resulting = Blend.

Ethanol When blended with other Ethanol, then resulting fuel =

Ethanol. Otherwise resulting = Blend.
Alcohol
Methanol When blended with other Methanol, then resulting fuel =
Methanol. Otherwise resulting = Blend.

Bio-diesel When blended with other Bio-diesel, then resulting fuel =

Bio-diesel Bio-diesel. Otherwise resulting = Blend.

HVO When blended with other HVO, then resulting fuel = HVO.
HVO Otherwise resulting = Blend.

Bio- When blended with other Bio-methanol, then resulting fuel =

methanol Bio-methanol. Otherwise resulting = Blend.
Biofuel Alcohol
Bio-ethanol When blended with other Bio-ethanol, then resulting fuel =
Bio-ethanol. Otherwise resulting = Blend.

Bio-LNG When blended with other Bio-LNG, then resulting fuel = Bio-
LNG. Otherwise resulting = Blend.
Gaseous
Bio- When blended with other Bio-hydrogen, then resulting fuel =
hydrogen Bio-hydrogen. Otherwise resulting = Blend.

StormGeo . USER MANUAL . s-Insight | Log // 30

 Fuel Class Fuel Category Fuel Type Blend Restriction

Other When blended with Other, then resulting fuel = Other.

Other Otherwise resulting = Blend.

Blend Blend Blend When blended any other fuel, then resulting fuel = Blend.

Auto generated BDN numbers: when fuels are mixed or topped-up onboard then unique BDN
numbers are automatically generated.

Example 1: Wrong reporting of fuel Topping up:

// 31 StormGeo . USER MANUAL . s-Insight | Log

Example 2: Correct reporting of fuel Topping up:

Example 3: Wrong reporting of Fuel Mixing:

StormGeo . USER MANUAL . s-Insight | Log // 32

Example 4: Correct reporting of Fuel Mixing:

[Link] Reporting Examples

In the upcoming sections a detailed instructions on how to report complex Biofuel blends will be
provided. This includes processes such as Bunkering, Fuel Mixing and Consumption reports.
Additionally, we will also cover scenarios involving Biofuel blends that contain multiple raw materials
with unique Proof of Sustainability (PoS) certificates.

// 33 StormGeo . USER MANUAL . s-Insight | Log

[Link].1 Example 1: bunkering a new biofuel blend (Fossil + Biofuel with a single PoS) into an empty tank

Data inside documentation:

BDN data
BDN number Test_BDN_1

Product name Bio VSLFO

Product Grade RMG 380 & 30% Bio-diesel

Viscosity 21.9 cSt

Sulphur content 0.45%

Density 927.4 kg/m3

Delivered quantity 500 mt

Bio quantity 150 mt

PoS (Proof of Sustainability) certificate example:

StormGeo . USER MANUAL . s-Insight | Log // 34

// 35 StormGeo . USER MANUAL . s-Insight | Log
 PoS certificate data
Unique Number of the PoS Test_PoS_certificate_1

Type of Product Bio-diesel

Type of Raw Material Waste cooking oil biodiesel

Quantity: 150 mt

Energy content (MJ): 5,550,000 MJ

EU RED Compliant material Yes

Total GHG emissions from supply and use of the 14.9 gCO2eq/MJ
fuel (gCO2eq/MJ)

Steps for reporting data into Recorder:

1. Create a new Bunkering event

2. Use control 'Bunkering in tanks considered as empty'

3. Select a Blend fuel type (Fossil + Biofuel) and fill all required fields:

StormGeo . USER MANUAL . s-Insight | Log // 36

4. Save event, send it to s-Insight | Log Server and use this fuel for the following events, when
consumed:

// 37 StormGeo . USER MANUAL . s-Insight | Log

[Link].2 Example 2: bunkering a new biofuel blend (Fossil + Biofuel with single PoS) into non-empty tank - Topping
up:
Assuming BDN and PoS parameters are the same as for Example 1:

Steps for reporting data into Recorder:

1. Create a new Bunkering event

2. Use control 'Bunkering in non-empty tanks / mixing'

3. Select an old fuel type

4. Select an New fuel type as Blend (Fossil + Biofuel)

5. Select Resulting fuel type as Blend and fill all required fields:

StormGeo . USER MANUAL . s-Insight | Log // 38

6. Save event, send it to s-Insight | Log Server and use this fuel for the following events, when
consumed:

// 39 StormGeo . USER MANUAL . s-Insight | Log

[Link].3 Example 3: bunkering a new biofuel blend (Fossil + Biofuel with 2 separate PoS certificates) into an empty
tank
Data inside documentation:

BDN data
BDN number Test_BDN_2

Product name Bio VSLFO

Product Grade RMG 380 & 50% HVO

Viscosity 21.9 cSt

Sulphur content 0.3%

Density 877 kg/m3

Delivered quantity 400 mt

Bio quantity 200 mt

PoS 1 certificate data

Unique Number of the PoS Test_PoS_certificate_1

Type of Product HVO

Type of Raw Material Hydrotreated oil from waste

cooking oil

Quantity: 130 mt

Energy content (MJ): 5,720,000 MJ

EU RED Compliant material Yes

Total GHG emissions from supply and use of the 10.9 gCO2eq/MJ
fuel (gCO2eq/MJ)

StormGeo . USER MANUAL . s-Insight | Log // 40

 PoS 2 certificate data
Unique Number of the PoS Test_PoS_certificate_2

Type of Product HVO

Type of Raw Material Hydrotreated oil from waste

cooking oil

Quantity: 70 mt

Energy content (MJ): 3,080,000 MJ

EU RED Compliant material Yes

Total GHG emissions from supply and use of the 12.5 gCO2eq/MJ
fuel (gCO2eq/MJ)

Steps for reporting data into Recorder:

1. Create a new Bunkering event

2. Use control 'Bunkering in tanks considered as empty'

3. Insert first fuel as Blend type (Fossil + Biofuel from PoS 1)

4. Insert second fuel as Biofuel (from PoS 2)

5. Fill all required fields:

// 41 StormGeo . USER MANUAL . s-Insight | Log

6. Create a new Fuel Mixing event and mix these two fuels together to have a resulting blend with
the same biofuel proportions as bunkered fuel:

7. Save events, send them to s-Insight | Log Server and use this resulting fuel for the following
events, when consumed:

Note: when bunkering a new biofuel blend (Fossil + Biofuel with 3 or more separate PoS
certificates), a similar logic should be applied as per Example 3:

· Bunkering fuel components separately:

StormGeo . USER MANUAL . s-Insight | Log // 42

 o Blend of Fossil & Biofuel1

o Biofuel2

o Biofuel3

o ...

· Mixing them afterwards and using the final resulting fuel blend for consumption reports.

3.10 Drafting of events

There are situations where you want to prepare an event but don't want to send it to shore yet,
since you plan to complete it later.

In those cases you may create the event (as described in Filing new events), but instead of pressing
the 'Save' button in the end you press the 'Save as draft' button:

The event is stored in the database, but marked clearly as a draft in the event overview (note the
different font, color and the icons):

The reason for this obvious marking is to remind you that there is an unfinished event. If you create
other events afterwards (and don't save those as drafts) they will behave as if drafted events do
not exist, i.e. following events will ignore drafts e.g. for duration calculations.

If you need to create events after a drafted one please make sure to check those events as soon as
you complete the drafted event.

Whenever you finish editing the drafted event save it by using the 'Save' button. It then becomes an
ordinary event.

Please note: When the 'Save as draft' button is not available saving the event as a draft is not
possible anymore (e.g. because the event has already been sent).

3.11 Modifying or deleting events

To modify existing events select the event from the overview and press the 'Edit event' button, or
double-click the event. The event will be opened with all its data.

A data check will always be performed when opening existing events, thus the 'Check Results' will
always show. Now you can modify the event's data, check the event again and save your data.
Please be aware that some modifications may affect other events, e.g. when changing consumptions
please make sure to correct following events as necessary. In case a following event becomes invalid
(e.g. ROB became negative, or you removed a fuel that is used later) these events will show a red
icon in the 'Value Check' column later in the overview.

// 43 StormGeo . USER MANUAL . s-Insight | Log

Events may be deleted as long as they were not sent to shore yet. However, special situations may
require to delete events even after they were sent. In this case, deletion of events must be enabled
onshore and a new configuration needs to be sent. After import of the new configuration, any event
can be deleted via “Delete event”. The action itself needs to be confirmed by verbal input. Deleted
events are propagated to s-Insight | Log Server with the next report.

Please use this option with utmost care since deleted event cannot be restored. Furthermore, it is
highly recommended to enable this option only when needed and to disable it afterwards.

3.12 Modify the current Master / Chief Engineer

In case of a crew change you may need to update the current Master and/or Chief Engineer. To do
so follow these steps:

1. Select the 'Officers' page

2. Click 'Add/edit Officers on top of the list

3. Click the next to the table (left side)

4. A new line appears at the bottom of the table, enter the new Officer's details.

5. Save your changes.

The list will be sorted automatically by sign-on date, and the 'In charge' flag will be changed
accordingly.

Note: do not overwrite former Masters/Chief Engineers with the new names and times; create
always new entries and expand the list

3.13 Voyages
Keeping your voyages up to date is very important. Every event you're entering must be part of a
voyage, otherwise it cannot be sent to shore.

The systems checks against the time and against the location (port of arrival and tuning port).
Following warnings shall inform you that you should most probably adjust your voyage details:

In this example the system informs you have reached the port that you have entered as your port of
arrival in the present voyage.

Click on the button to go directly into your voyage menu and adjust your details. For example
create a new voyage; the new departure port and time will overwrite automatically the entered
arrival port and time of the previous voyage.

StormGeo . USER MANUAL . s-Insight | Log // 44

Here the systems informs you that according to your entered voyage details you should have
reached your port of arrival already. In that case you can adjust your time of arrival in the voyage
details or create a new voyage which would automatically overwrite.

Note: always check your reporting instructions on how to use voyages. The application only
performs basic checks, there may be more rules in place that affect the way you must handle
voyages.

3.13.1 Voyage stage logic

Voyage stages should be defined according to the planned vessel cargo stages or voyage direction
stages:

· BALLAST/LADEN stages should be used for voyages where cargo stages are changing from ballast
to laden and vice versa.

· E/W/S/N stages should be used for directional voyages, where voyage stage is changing at a
voyage turning point.

Note: One voyage stage can consist of one or multiple voyage legs, but voyage legs should not
be setup as stages in s-Insight | Log.

1. Example of a correct one way BALLAST/LADEN voyage setup with multiple voyage legs from
Hamburg to Southampton:

Proper setup in s-Insight | Log Recorder:

// 45 StormGeo . USER MANUAL . s-Insight | Log

2. Example of a correct round voyage (East/West) setup with multiple voyage legs from Hamburg to
Yangshan:

Proper setup in s-Insight | Log Recorder:

StormGeo . USER MANUAL . s-Insight | Log // 46

3.13.2 Entering a new voyage
To enter a new voyage press the 'New voyage' button - an empty voyage is now shown.

First enter the voyage details:

· Voyage no: the voyage number as defined by your operator. If a wrong voyage number is entered
you won't be able to save the voyage. Please refer to your operator's instructions on how the
voyage number should look like.

· Service/Trade: select the service/trade as specified by your operator.

· Voyage type: available voyage types are:

o Round voyage: starts and ends in the same port, has 2 stages and a turning port in between
them. The arrival port cannot be edited here because it is the same as the departure port.
In case you skip your arrival port just ignore the warning ('end port mismatch') and continue with
your next voyage.

o One way: has a start and end port, and may have none, one or many stages in between.

Use the 'Add another stage' button (right between the boxes) to create stages, and the 'trash can'
symbol in the top/right corner of the stage boxes to remove stages.

o Idle: has only a 'start' port (which is the port the vessel is idling in), and an expected end.

Depending on your type selection the fields below are configured. All data fields are shown in a
chronological order to help you write down your time schedule. When planning the voyage some
dates/times are only estimations (e.g. the arrival time/end of voyage). Enter these estimations now
and update the voyage details as soon as you know the actual times.

Where possible the application will check and show if voyage details should be reviewed, either via
'check results' (when entering events) or with the 'your attention is needed' box.

// 47 StormGeo . USER MANUAL . s-Insight | Log

When you're done press the 'Save' button. In case there are warnings or errors in your voyage
details, the 'check results' sidebar will appear and show them. Errors (red) must be corrected before
saving the voyage, warnings (blue) should be read but can also be ignored.

When no errors remain press 'Save' again. The voyages list will now appear and the new voyage is
stored in it.

One-way voyages typically consist of a single stage only. Hence, newly created voyages of this type
will no longer allow creating multiple stages unless specified otherwise. This will prevent defining
long voyages with several stages of the same type instead of using the schedule. Existing voyages
are not affected.

By default, new one-way voyages have a single stage only. To continue reporting with multiple
stages, change the corresponding option in s-Insight | Log Server.

While turnports are commonly used by container line operators for defining round voyages, this
concept is uncommon to other operators and vessel types. It is now possible to disable the input of
turnports for round voyages. Existing voyages are not affected.

In order to disable the input of turnports, change the corresponding option in s-Insight | Log Server.

3.13.3 Modify an existing voyage

Modify your voyage if...
details are missing (or were left blank to be filled in later),
o a stage change happened and you need to update a previously assumed time with the actual
arrival time,
o your voyage has ended and you want to overwrite a previous estimation with the actual end
time.
To modify existing voyages you simply click the 'Edit voyage' button on top of the list, the selected
voyage is opened. Modify fields as needed and press 'Save'.

Now the values are checked. If errors or warnings are found the data is not saved, instead all
findings are displayed on the right side of the voyage. Review errors and warnings, correct (at least)
the errors and press 'Save' again.

The voyage details are now saved and will be transferred to shore with the next mail you send.

3.13.4 Deleting a voyage

It is possible to delete the latest voyage available, as long as it has not been sent to shore yet. If
there is only one voyage stored, this one cannot be deleted at all.

As soon as voyages have been sent to shore they cannot be deleted anymore. Modifications to the
voyage are always possible.

3.13.5 Speed orders

“A time charter contains a warranty by the owner that the ship is capable of steaming, fully laden, in good
weather and smooth water at a stated speed and at a stipulated rate of bunker consumption. … Where
the ship fails to attain her charted speed – in good weather and smooth water – during the voyage or
where the bunker is in excess of that stipulated in the charter, the ship owner may be liable. The speed
warranty applies only when the ship is loaded.” [Panayides, Principles of Chartering]

The combination of minimum speed, maximum consumption and applicable weather conditions is
called speed order. Speed orders are provided by the operator to the vessel. It is possible to have
more than one speed order per voyage. To ease communication speed orders are given unique
names like “Full”, “Eco speed”, etc.

StormGeo . USER MANUAL . s-Insight | Log // 48

Speed orders are typically used for bulkers and tankers.

During a voyage the operator advises the vessel to follow a speed order, i.e. to sail at a specified
minimum speed while not consuming more fuel than warranted. The applicable speed order may
change several times during a voyage.

After completion of a voyage, speed orders are used for post-voyage analysis, e.g. calculation of
over-/under consumption, time-gains/losses, etc. Usually severe weather conditions are excluded
from analysis.

Details of speed orders are recorded in the Voyage editor.

Open the Voyage editor, expand the input form “Speed order” and click (+) to insert one row for
each speed order received. Fill in all data and save the input together with other voyage details.

The warranted consumption per day and fuel type is not specific to consumers. If, for example, at a
speed of 9.2 knots, ME consumes 21.4 mt HFO/day and all AEs consume 4.5 mt HFO/day, the total
consumption is still in range of the warranted consumption of 26 mt/day in the example above.

When trading in ECAs only, the warranted fuel consumption usually covers MDO/MGO only. The
corresponding speed order would specify 0 mt HFO/day.

When trading inside and outside of ECAs, two speed orders must be defined respectively, see below.

After speed orders have been defined in the voyage editor, they can be used for all voyage events
on sea passage, e.g. Noon at Sea. For this, go to the event header and select the speed order that
was advised since the last event.

3.14 Schedule and Agents

In addition to the voyage data, a more detailed schedule can be used. This schedule is visible
anshore and can be exported. The schedule is not connected to any events or the voyage itself.

// 49 StormGeo . USER MANUAL . s-Insight | Log

All fields can be edited in the table directly. For each port call, port name and time of arrival at pilot
station (ETA) must be specified, the time zone is needed only once.

To simplify input of repeating port call sequences, selected port calls can be copied. For this, mark the
relevant entries and click the “Copy” button. On insert, the arrival date of the first port call to be
copied must be specified. You can also choose whether to copy agent names and times.

For efficient input of schedules, files can be imported in EXCEL format (*.xls, *.xslx). The file must
contain a worksheet “Schedule” with predefined columns, unknown columns are ignored.

Currently, the schedule is a standalone component, neither linked to voyages nor events. The
missing links shall be introduced in future versions.

Agents – or agent companies – are now supported. To create an agent, select “AGENTS” from the
menu. Company name, address, phone numbers and serviced ports can be specified. Agents can be
assigned to port calls in serviced ports only.

For a port call, agents can have one or more of the following roles:

StormGeo . USER MANUAL . s-Insight | Log // 50

· Husbandry Agent

· Charterer/Liners Agent

· Cargo owner Agent

· Other

It is possible to specify zero, one or more agent roles per port call.
All updates of the schedule are sent to shore.

The following details of the next 4 ports stays can be used in push messages: port name, ETA, ETD,
email addresses of agents.

On s-Insight | Log Server, agent details can also be copied to the clipboard as structured text to,
e.g., forward them to 3rd parties.

Agents can also be defined on s-Insight | Log Server. They are made available to all vessels via
configurations. Upon successful import, agent details are available in the Agent editor. Server defined
agents can neither be modified nor deleted.

3.15 Garbage Record Book

New amendments to MARPOL Annex V entered into force on 1 March 2018. s-Insight | Log is now
fully compliant with the latest version of MARPOL Annex V.

The new Garbage Record Book is split into

· Part I for all garbage other than cargo residues, applicable to all ships

· Part II for cargo residues, applicable to ships carrying solid bulk cargo only

In addition, a new table for exceptional discharge or loss of garbage under regulation 7 was
introduced.

The Garbage Record Book is now directly accessible via menu item “REPORTS”.

Disposal events are displayed per the selected time frame. Please note that disposal events are
included only if recorded with version 2.2 or later.

// 51 StormGeo . USER MANUAL . s-Insight | Log

The Garbage Record Book can also be exported to EXCEL for further processing and printing.

3.16 Off-hire
When a vessel under charter is unable to perform contracted services for a certain period, this is
commonly referred to as “off hire”. This can include, e.g., days spent for repair and drydocking,
whether scheduled or unscheduled. While time, consumptions and reasons are important details for
commercial purposes, the total annual off hire time could be an interesting vessel KPI.

StormGeo . USER MANUAL . s-Insight | Log // 52

To support reporting off hires, 2 new special event types are introduced, “Begin offhire” and “End
offhire”.

For the event “Begin offhire”, time, position, consumption and running hours shall be reported. In
addition to this, one or more reasons, percentage and mode (scheduled or unscheduled) must be
reported. Reasons include, e.g. breakdown ME or AE, overhaul ME or AE, dry docking and PSC
detention.

Subsequent events are flagged in both individual event report and event view until the off-hire
period is finished.

Off-hire reasons, percentage and mode (scheduled or unscheduled) are made available for further
assessment on s-Insight | Log Server.

// 53 StormGeo . USER MANUAL . s-Insight | Log

3.17 Sending data
When you have entered one or more events you can now open the 'Communication' page to send an
events report:

1. Open the 'Communication' page. The Outbox is selected, showing all events that have not
been sent yet.

2. If the 'Value check' still shows red icons (i.e. errors) these events will not be sent. It is highly
recommended that you edit those events and correct the errors, especially if the errors are
somewhere in the middle of the list.

3. Press 'Send all' button to send all event reports.

Please note: You need to have valid export settings in order to send event reports. Go to 'Settings'
and configure the data export if you have not configured the program yet, or if the
configuration is not valid anymore.

4 Non-daily tasks

4.1 Log Abstract onboard

Important event data can now be exported in Excel format for subsequent quality checks and
external assessments. The export includes one row per event in the Events view after applying the
voyage filter. Columns are those from the Event view like position and voyage data but also
additional information like speed, running hours, power, consumption, cargo information, engine
distance, slip, SFOC, etc.

StormGeo . USER MANUAL . s-Insight | Log // 54

4.2 Inserting events
In case events are missing in your time line you can easily add those events, follow these steps:

· open the 'Events' page

· select the missing event from one of the 'New ... event' menus on top of the list;
even if the entry is shown in grey you can select the desired event

· in the first screen select/ enter the correct event time; on top of the screen a message will
appear, notifying you that the event will be inserted in the middle of the time line, which is OK
in this case

· check the time line and verify the new event is entered correctly; now press 'Continue'

· enter all event details, check and save the event

· also make sure to check surrounding events in case you have entered data which affects other
events, e.g. consumptions, which now needs to be corrected

· when returning to the event list also other events may be marked for sending (if consumptions
were entered, as these change the ROB calculations for following events, too)

· the new event will be sent to shore with the next data transfer

4.3 Re-sending data

In case an e-mail got lost you can always send it again. Go to the 'Communication' page, select the
'Archive' box and then the mail you need to send again. Click the 'Resend report' button and the mail
will be sent again.

// 55 StormGeo . USER MANUAL . s-Insight | Log

Lost e-mails are detected on shore. If this happens you will receive a message from the server which
report is missing.

You can identify the missing mails with the ID, which is shown in the archive in the communication
page:

4.4 Loading a new configuration

Eventually you will receive an e-mail with a new configuration file from s-Insight | Log Server. This
may introduce new general data, like port LOCODEs, services, etc or update your vessel's technical
data.

The e-mail includes a zipped configuration file.

· save the file to any location

· open s-Insight | Log Recorder

· select 'Settings' icon and press 'Import configuration'

· select the configuration file and press 'Open'

You will then receive a response from the program whether the file could be loaded successfully or
not. Please note that you can only import the latest configuration that exists.

StormGeo . USER MANUAL . s-Insight | Log // 56

Every new event and every new voyage will now use this new data, but please note: only new
objects will use it, not existing ones. Every voyage or event is linked to the configuration that was
valid at creation time, and this cannot be changed. The only possibility is to delete the voyage/event
and re-create it, if possible.

4.5 Unsent events

Events are invalid if they cause validation errors. Those events are not sent to shore but remain in
the outbox of s-Insight | Log Recorder. This leads to reporting gaps and potentially inconsistent
assessments on s-Insight | Log Server.

It is therefore highly recommended to fix all validation errors. To get assistance, details of the invalid
events can be sent to s-Insight | Log Server. To enable this feature, choose General settings and
check the option to include details of invalid events.

4.6 Copy the whole installation to another PC

In case you need to move your installation from one PC to another please follow these steps, right
after you made a backup of your old setup:

1. Locate the data path. If it is a network path go directly to step 4.

2. If you have configured a local data path, please make a copy of it. Verify the copy, make sure
nobody was accessing data while you copied the data.

3. Copy the data path to the new PC. The location does not matter as long as it is accessible for
all users that will work with the program.

4. Install the software on the new PC. Specify the data path you have created just before (or the
same that was set before if it was a network path).

5. Make sure to configure the same sharing settings (if any) as on the first PC, otherwise other
PCs will not be able to access data afterwards.

6. Verify that the program is starting correctly, and that it shows the data as before.

7. If you have used network shares you need to modify all other PCs that were accessing the old
PC. Use the support tool on every other PC and relocate the data path to the new location.

// 57 StormGeo . USER MANUAL . s-Insight | Log

 8. Verify that all other PCs can access the data at the new location.

4.7 Backup
A backup control can be accessed through Recorder application settings. There are two ways of
doing a backup: manual and automatic:
· Manual backup is only possible when not in edit mode. After 'Backup' button is pressed, then full
Recorder database backup is made and saved locally onboard. Onboard user is able to restore
data from the latest available backup by pressing 'Restore' button. Timestamp is provided of
backup which is available onboard.
· Note: restore feature should be used with precaution. When pressed, all new changes and newly
entered event data, made after the 'Last backup' date, will be lost.
· Automatic backup feature can be enabled when in edit mode. When enabled, a new backup will be
created each time event reports were sent to shore. It is possible to create backup and restore
data manually from backup event when automatic backup options is enabled.
· Note: automatic backup option, when enabled, can have an impact on Recorder performance. For
large onboard databases with many events this feature might increase report sending time. If you
face similar issues, it is recommended to keep automatic backup feature disabled.

StormGeo . USER MANUAL . s-Insight | Log // 58

5 Overview of event types

5.1 Voyage Events

Arrival

File this event when arriving in port. Here you can also fill in tugs, thruster operations and pilots;
changes the voyage state to 'Port'.

The arrival event indicates that you are in a port either for cargo operations and/or at berth. Use
Arrival events also if cargo operations are planned to be done while anchoring.

Shifting

For all vessel movements during one part call you can use the shifting event.

All operations entered are summed in the departure event and in the departure push message.

// 59 StormGeo . USER MANUAL . s-Insight | Log

Sailing notice, Departure

When you are leaving a port you may use the sailing notice to inform shore immediately about your
departure and your next destination port, and also let the server send out push messages for this
event. Typically used if you don't find the time to provide complete details on cargo and machinery
operations, but shore needs immediate notification.

After filing the sailing notice the voyage state is 'Departure', indicating that the next event should be
a departure event, which in turn contains all details on cargo and machinery operations. You may
copy the values from the sailing notice to the departure event prior to entering all other data.

Do not file any other events between a sailing notice and the departure event.

Begin & End canal passage

When entering a canal the voyage state becomes 'River/ Canal'. During canal passages you may file
a stoppage or port event (begin/end anchoring/drifting, arrival/departure).

Begin & End of sea passage (BOSP/EOSP)

With BOSP/EOSP you can define your maneuvering/river times.

Begin & End anchoring/drifting

File this event in case of a stoppage (anchorage/ drifting/ grounding), e.g. when waiting for berth or
canal passage. Upon continuing your voyage, please send an end of anchoring/drifting event.

The voyage state will be 'Stoppage'.

Noon (Position)

Files a noon report (e.g. every 24 hours; depending on your company's/ operator's instructions).
Depending on your current voyage state only one of the four noon events fits. The event you choose
decides which fields you can/ must fill out.

Please note: you may change the default time (i.e. the time that is pre-filled when creating the noon
report) in the settings.

ETA update

File this event to inform shore about changes of ETA/RTA.

5.2 Special Events

Begin & End fuel change over

File the beginning and end of fuel changeover before entering ECAs. These events are available
mainly for compliance reasons. Thus, when leaving ECAs you do not need to file these two events - if
not otherwise requested (i.e. by your operator and/or manager).

Change destination port

If you are deviating towards a new port choose this event. The voyage state will now show
'Deviation' in the info panel (in the events overview). The deviation ends with an arrival event.

StormGeo . USER MANUAL . s-Insight | Log // 60

Begin & End of deviation

In case of a deviation from the planned route (without heading for a new port) report the deviation
(upon begin and when returning back to the scheduled route). The voyage state will show 'Deviation'
in the info panel (in the events overview). The deviation ends either with an end of deviation event,
an arrival or with a change destination port event (which will immediately start a deviation again).

Entering & Leaving special area

File these events upon entering or leaving special areas (e.g. ECAs, piracy areas, etc.).

Note: in some special areas you are required to report consumptions of your engines/boiler.

Other event

File this event in cases your charter party begins/ ends, or when passing landmarks (e.g. Gibraltar,
Land's End).

Oil spill

This event is used to report spillages.

Inventory

Report all fuels/oils remaining on board using this event. You may also enter a list of chemicals on
board in this event.

Monitoring of chemicals on board was expanded by Paints and Thinners, they can be reported during
Inventory event. VOC emissions are calculated automatically based on amount that was consumed.

To start reporting Paints and Thinners all required information (list of products and their VOC content
[g/l]) must be specified and loaded to Server default settings. Please contact StormGeo at
[Link]@[Link] if this is required.

New columns were added to Chemicals on board:

· Last ROB

· Purchases

· Consumption (mandatory)

· ROB

· VOC emiss. [kg]

Cargo condition

// 61 StormGeo . USER MANUAL . s-Insight | Log

The Cargo condition event is available for the tankers, LNG and gas carriers.

You can report the temperatures/pressure of cargo tanks and the associated heating units of a
specific time.

Note: if no heating units are available inform your IT department to do the setup

Cargo condition events have been extended to capture the status of cargo on board in more detail.
For LNG carriers and Gas carriers, temperature and pressure per tank can be reported. More
specifically, product name, quantity, and cargo temperatures (set, top, middle, bottom) are reported.
Average temperatures are calculated per tank and across all tanks.

Column “Delta” shows the temperature difference to the last report. Tank pressure is now captured
in bar. Optionally, air temperature and sea temperature can be specified.

Performance Snapshot

This event captures a momentary snapshot of your engine performance status (and several other
plants) for on shore evaluation of engine usage as well as wear and tier monitoring.

Begin & End of off-hire

When a vessel under charter is unable to perform contracted services for a certain period, this can
now be reported by new offhire events. This can include, e.g., time spent for repair and dry docking,
scheduled or unscheduled. Total off-hire time, consumptions and reasons can be captured for
subsequent assessment.

5.3 Operational Events

Bunkering, Fuel mixing, De-Bunkering

Reporting of bunkering operations. In order to report consumptions on fuels you need to provide all
values* for that fuel before other events allow selection of that fuel.

(*except for BDN/BDR No. - you may already select the fuel in other events without one)

StormGeo . USER MANUAL . s-Insight | Log // 62

Sounding correction

This event allows correction of fuels/oils ROB. When reporting a sounding correction correct the ROB
masses if there are differences (or confirm correct values with 'No difference').

Ballast water source, exchange, discharge, internal transfer

File events as per ballast water record book.

Disposal by incineration, - ashore, - over board, - by barge, Discharge via separator, disposal by
evaporation or by decanting

File events as per garbage/oil record book.

VOC release

Use this event to report the emission of volatile organic compounds for tankers.

Maintenance

Use this event for some maintenance events, e.g. hull or propeller cleaning.

Fuel Lab Analysis Report

Reporting of analysis data received from fuel test labs for bunkered fuels. For each fuel sample, a
separate report needs to be created.

6 CII reporting guidelines

CII stands for Carbon Intensity Indicator.

It is an indicator which the IMO developed to rate the efficiency of ships.

Disclaimer:

Please note the advice below for Carbon Intensity Indicator reporting, differs for each verification
society. The advice below is therefore only a rough indication for correct reporting, when in doubt or
for specific questions please check with your shipping company or the MRV&DCS verifier of your data.

The following items in the S-Insight Log software have an impact on the CII.

6.1 Deviation due to Emergency

The 'Deviation' reporting will not affect the CII of a ship in a big way. As for Deviation periods, the
whole period will be cut out (distances and consumptions). Moreover, such occasions are seldom.
When a ship wants to report 'deviation due to weather', this will only be accepted in strict cases: the
ship suddenly needs to be affected by bad weather, and the weather needs to be so bad that it
affects the safety of the ship.

Do not report deviation in cases: When you have planned an original route, and few days later you
need to deviate because a hurricane will come up on the original route, and you deviate from the

// 63 StormGeo . USER MANUAL . s-Insight | Log

original route to pass in calm waters; then this deviation is not entitled for CII deductions under
'Deviation – weather'.

Scenario no. 1, when destination port is not changing:

1. Report Begin of deviation event in New special event and provide a reason:

a. Reason for deviation: Rescuing

b. Reason for deviation: Emergency

c. Reason for deviation: Weather

d. Reason for deviation: Technical damage

2. Closing deviation period:

a. Report End of deviation event and continue voyage.

b. Report Arrival event, which will automatically close the deviation period.

Scenario no. 2, when destination port is changing:

1. Report Change destination port (deviation) event in New special event and provide a reason:

a. Reason for deviation: Rescuing

b. Reason for deviation: Emergency

c. Reason for deviation: Weather (in seldom cases only, where weather affects safety of ship)

d. Reason for deviation: Technical damage

2. Report Arrival event, which will automatically close the deviation period.

StormGeo . USER MANUAL . s-Insight | Log // 64

6.2 Time sailed in ice
1. Report 'Entering special area' with special area = 'CII Ice conditions'
Vessel will have indication that she is sailing in ice conditions: event list + event header.

2. The following reports will have reporting field: 'Sailing in Ice conditions: Duration:'
Applicable to all events where sailed distance can be reported, except 'End Anchoring/Drifting' and
'Noon at Stoppage'.

3. Report 'Leaving special area' with special area = 'CII Ice conditions'

4. Duration field and Indication of sailing in ice will not be available until Entering Ice conditions
again.

// 65 StormGeo . USER MANUAL . s-Insight | Log

Subsequent events should be reported with the field highlighted below for sailing in ice condition.

6.3 STS voyage for tankers

Tankers engaged in STS voyages may apply the correction factor to all fuel consumption relating to
STS voyages, including cargo transfer at offshore location, voyage, cargo discharge and waiting
periods at anchor or drifting during which the ship reports being part of an STS operation and
voyage. The STS operation includes fuel consumption in port where the transferred cargo is
discharged after such a voyage.

Starting report period (Departure port to STS location) – Example below Port A – STS – Port A.

· Report in Other location in Departure:

o Departure location (Port A)

o Intended Destination (STS)

· Report voyage as normal sea passage

· Report in Arrival as Other location:

o Arrival location (STS)

· Daily Noon Port report Other location (STS)

StormGeo . USER MANUAL . s-Insight | Log // 66

Closing report period:

· Report in Other location in Departure

o Departure location (STS)

o Intended Destination (Port A)

· Report voyage as normal sea passage

o Arrival location (Port A)

// 67 StormGeo . USER MANUAL . s-Insight | Log

* A tanker is engaged in an STS voyage if a voyage between cargo loading and cargo discharging locations, or
a voyage between cargo discharging and cargo loading locations does not exceed 600 nautical miles and the
time for each of these voyages (which does not include port or discharge time) is limited to 72 hours.

6.4 Reefer consumption

There are 2 options of reporting reefer for CII. The simple method is to report number of reefer
containers in each Departure. The other method is for vessels with a Power-meter for Reefer
containers, these vessels can report the kWh used for reefer containers.

Vessel with possibility of reporting Reefer kWh:

1. All Reefer power outlets are available for reporting under Machinery operations -> Reefer
performance
When no Reefer power outlets are created on Server, then new 'Reefer performance' control is
not available.

2. Running hours, Reefer electrical work [kWh], Avg. power and Source of energy must be reported
for proper calculation of CII reduction.

3. Running hours are defaulted from Duration

4. Calculator buttons are available for 'Reefer electrical work' and 'Avg. power', they are working in
the same way as for Effective work and Avg. power (e.g. Main Engine)

StormGeo . USER MANUAL . s-Insight | Log // 68

5. 'Source of energy' dropdown consist off all engines/components that were created on Server
(unique list per each vessel individually) and can provide electricity for reefers:

a. Main engines

b. Auxiliary engines

c. Main generator engines

d. Onshore power supplies (visible in Departure or Noon in port events only)

6. Note: in case electricity was produced by more than 1 engine, vessel should select only the main
energy source in the dropdown.

Vessel without possibility of reporting Reefer kWh:

1. Report 'Number of full reefer on board' under Cargo control.

6.5 Cargo Cooling & Reliquification Systems on Gas/LNG Carriers

Reporting of electrical consumption of cargo cooling/reliquification systems on Gas Carriers and LNG
Carriers.

Cargo cooling system

1. All Cargo cooling systems are available for reporting under Machinery operations -> Cargo cooling
performance.

2. Running hours, Cooling electrical work [kWh], Avg. power and Source of energy must be reported
for proper calculation of CII reduction.

// 69 StormGeo . USER MANUAL . s-Insight | Log

3. Calculator buttons are available for 'Cooling electrical work' and 'Avg. power', they are working in
the same way as for Effective work and Avg. power (e.g. Main Engine)

4. 'Source of energy' dropdown consist off all engines/components that were created on Server
(unique list per each vessel individually) and can provide electricity for Cargo cooling systems:

a. Main engines

b. Auxiliary engines

c. Main generator engines

d. Onshore power supplies (visible in Departure or Noon in port events only)

Note: in case electricity was produced by more than 1 engine, vessel should select only the main
energy source in the dropdown.

Reliquification

1. All Reliquification plants are available for reporting under Machinery operations -> Reliquification
performance.

2. Running hours, Reliquification electrical work [kWh], Avg. power and Source of energy must be
reported for proper calculation of CII reduction.

3. Running hours are defaulted from Duration

4. Calculator buttons are available for 'Reliquification electrical work' and 'Avg. power', they are
working in the same way as for Effective work and Avg. power (e.g. Main Engine)

5. 'Source of energy' dropdown consist off all engines/components that were created on Server
(unique list per each vessel individually) and can provide electricity for Reliquification:

a. Main engines

b. Auxiliary engines

c. Main generator engines

d. Onshore power supplies (visible in Departure and Noon in port events only)

Note: in case electricity was produced by more than 1 engine, vessel should select only the main
energy source in the dropdown.

StormGeo . USER MANUAL . s-Insight | Log // 70

6.6 Electric Cargo discharge pumps on tankers
Electrical consumption of discharge pumps on tankers.

1. All Pumps are available for reporting under Machinery operations -> Pump performance

2. Running hours, Discharging electrical work [kWh], Avg. power and Source of energy can be
reported only for Electric and Hydraulic Cargo pumps.
For all the rest pumps - only reporting of running hours is enabled.

3. Calculator buttons are available for 'Discharging electrical work' and 'Avg. power', they are
working in the same way as for Effective work and Avg. power (e.g. Main Engine)

4. 'Source of energy' dropdown consist off all engines/components that were created on Server
(unique list per each vessel individually) and can provide electricity for Reliquification:

a. Main engines

b. Auxiliary engines

c. Main generator engines

d. Onshore power supplies (visible in Departure or Noon in port events only)

e. Diesel power packs (available only for Hydraulic Cargo Pumps) - when selected, user is guided
to report fuel consumption (not kWh)

Note: in case electricity was produced by more than 1 engine, vessel should select only the main
energy source in the dropdown.

// 71 StormGeo . USER MANUAL . s-Insight | Log

Reporting note for hydraulic cargo pump that is connected to electric power pack: Running hours,
Discharging electrical work and Avg. discharge power should be reported and Source of energy (AE /
ME / MGE / OPS) that generated electricity for electric power pack assigned.

6.7 Boiler consumption for cargo heating and discharge pumps on tankers
Tankers with cargo pumps driven by steam from the boiler and Tankers which do cargo heating with
the Boiler can report below.

Reporting 'Used for' reasons for fuel consumption:

a. 'Cargo heating'

b. 'Cargo discharging (pumps)' for Steam Cargo discharging pumps driven by Boiler

6.8 Other discharge pumps on tankers

Reporting fuel consumption of standalone engine driven cargo pumps during discharge operations on
tankers which may be deducted from the calculation of the attained CII.

Standalone cargo discharging pumps (hydraulic pump connected to diesel power pack):

StormGeo . USER MANUAL . s-Insight | Log // 72

1. Report Pump Running hours and Source of energy as 'Diesel power pack'

2. Report fuel consumption for Power packs and provide 'Used for' reason as 'Cargo discharging
(pumps)'

6.9 CII reporting overview

Which vessels can get certain CII deductions?

Container vessels:

· Sailing in Ice

· Deviation e.g. for SAR / Emergency

· Reefer reporting

Gas Carriers:

· Sailing in Ice

· Deviation e.g. for SAR / Emergency

· Cargo Cooling / Cargo Reliquification

Tankers:

· Sailing in Ice

// 73 StormGeo . USER MANUAL . s-Insight | Log

· Deviation e.g. for SAR / Emergency

· STS

· Boiler consumption for Cargo Discharge and Cargo heating

· Electric driven cargo discharge Pumps

· Other Discharge Pumps (e.g. connected to Diesel Power Pack)

Other vessel types:

· Sailing in Ice

· Deviation e.g. for SAR / Emergency

· Reefer reporting if reefers carried

7 eLogbook integration

Data from Anschütz eLog, electronic logbook, is integrated into s-Insight | Log Recorder. This
integration helps users to create s-Insight | Log reports and fill them using data that is already
available inside electronic logbooks.

How to setup eLog integration onboard? (see screenshot below)

· Prerequisites: Anschütz eLog solution should be available and running on your vessel.

· Update your s-Insight | Log Recorder to version 2.10.0.

· Request and load new vessel configuration from s-Insight | Log Recorder.

· Turn eLog integration on by following steps as per screenshot.

· When eLog solution is not available onboard, it is recommended to keep the switch off
(disabled).

· Endpoint address is the URL of the service:

o [Link]

o where [Link] is the same IP address which is used to access the eLog in the
browser.

o For example, if the eLog has the IP address [Link], then URL would be
[Link]

o Please refer to Anschütz eLog User Manual section 'StormGeo integration' for more
details.

· There is an option to validate your entered Endpoint address by pressing 'Test connection'
button.

StormGeo . USER MANUAL . s-Insight | Log // 74

 · After following these steps and saving s-Insight | Log Recorder settings, electronic logbook
integration should be ready for use.

· When eLog integration is enabled, application is adjusted as described below.

// 75 StormGeo . USER MANUAL . s-Insight | Log

Reporting suggestions sidebar:

Please note that reporting suggestions from electronic logbooks are showed in the main Events
window for the last 7 days only. Older reporting suggestions are not visible. When active
suggestion is not used for 7 days, it is automatically removed from suggestion list.

These suggestions do not automatically change existing or create new reports. They assist user
by suggesting to take necessary actions, but user still needs to create a report, fill it and apply
suggestions manually.

When data becomes available in electronic logbook, then 2 types of reporting suggestions are
showed within this control:

StormGeo . USER MANUAL . s-Insight | Log // 76

 · New events - suggestions for user to create a new event in s-Insight | Log Recorder. User can
either create suggested event or ignore the suggestion. Ignored new event suggestions are
moved to '7 day archive' and can be reviewed or used at a later time, if needed.

· Edit events - suggestions for user to edit data in the existing events that are already created
in s-Insight | Log Recorder. These suggestions are showed when 1 or more data fields inside
the event are not matching value available in electronic logbook. By pressing 'Edit this event'
button, related event will be opened for editing and edit suggestion will be showed inside the
event. See chapter 'Suggestions inside events' for more information.

Main event list:

· There is an option to 'Show reporting suggestions' in the main event list, as per image below.
When this option is enabled, new event suggestions are inserted into the list of existing
events.

· User can either use the sidebar control or main event list to view suggestions and apply
required actions.

· New column 'Suggestions' indicates events and type of suggestions: NEW EVENT or EDITS.

· Even though new event suggestions are showed in the list, they will not be sent to shore,
unless user creates and saves an actual event, based on this suggestion.

· Edit event suggestions indicate a number of active suggestions for editing data fields inside
the event.

// 77 StormGeo . USER MANUAL . s-Insight | Log

Suggestions inside events:

· A new sidebar 'SUGGESTIONS' was introduced inside event edit window next to 'CHECK RESULTS’.

· Available data from eLog is fetched automatically when opening an event (new or existing). This is
done using field mapping information from s-Insight | Log Server.

· Data is being fetched from eLog for the last 24 hours counting from event time. If multiple field
values are found in eLog for the period, then only the latest value is presented.

· User can perform multiple actions:

o Refresh electronic logbook suggestions / fetch new data from eLog by pressing .

o Apply all active suggestions - fill s-Insight | Log Recorder data fields with data from eLog.

o Ignore all active suggestions - mark all suggestions as 'Ignored'. No eLog data will be populated
into s-Insight | Log event.

o Apply a single active suggestion - populated event field with mapped data from eLog.

o Ignore a single active suggestion - ignore mapped data from eLog. This option should be used
when eLog value is not correct or outdated.

o Undo the action - in case of mistake, it is possible to revert Apply or Ignore actions that were
taken during the session.

· It is always possible to enter event data manually, even when there are active suggestions.

· It is recommended to have a clean 'SUGGESTIONS' sidebar by taking Apply or Ignore action for
each suggestion. This way suggestions count indication will show 0 active suggestions inside
event and in the event list.

· In case s-Insight | Log data field value matches eLog suggested value, then it is automatically
marked as 'Applied'.

· Vessel crew actions regarding eLog suggestions are saved between s-Insight | Log Recorder
sessions.

· Suggestions and user actions are stored locally (onboard) and they are not sent to s-Insight | Log
Server.

StormGeo . USER MANUAL . s-Insight | Log // 78

Event and field suggestion mappings

Suggestions inside s-Insight | Log Recorder depend on event and field suggestion mappings inside
s-Insight | Log Server.

In case you have any questions or suggestions for improvements, please contact Service and
Support ([Link]@[Link]).

8 Troubleshooting

8.1 Access denied

Error messages stating 'access denied' are typically caused by insufficient access rights to folders or
network shares. If, for example, the installer fails to set required access rights during upgrade of a
network installation, this may leave the system in an inconsistent state.

Refer to chapter Folder access rights for details on how to check and set access rights.

// 79 StormGeo . USER MANUAL . s-Insight | Log

Another potential cause for this error is the use of encrypted files. If files or directories are
encrypted, access by other machines may not be possible. In this case, change the settings for file
encryption to grant access to the relevant machines, or disable encryption entirely. To change
encryption settings for a file, right-click on the file, select 'Properties -> Advanced...' and select
'Encrypt contents to secure data' (label depending on OS version).

8.2 Installation

8.2.1 General
If the installation fails, please make sure,

· the system meets the minimum requirements specified in System requirements.

· to have write permission to 'Program Files' (or similar) and the data folder (name depending on
OS version and language).

· to have administration rights required for installation of new software.

· to have sufficient access rights to the network location used for a network installation, see
Using the application in a network.

· to have permission to modify folder access rights when sharing the data folder. The installer
tries to access to 'Everyone', for both network share and data folder. Also check that network
sharing is enabled on your machine, i.e. check all machine settings, permissions and services
related to networking.

· to run the installer from a local directory.

· to use the correct installer package.

8.2.2 Installer settings cannot be stored

This option is only available if a custom data path was specified during first-time installation and
'Share this path as network share' was not selected. If instead
· the default data path was used,
· a network share was used, or
· the data path is shared over a network,
the settings are not suitable for subsequent installations. Hence this option is not available. Instead,
all machines are to be configured individually.

See also First time vs. Follow-up installation and Installation options.

8.2.3 Upgrading to a new a version

For a network installation, make sure to upgrade all machines to the latest version.

When upgrading to a new version, the database is updated automatically during first login. If an
error occurs during that process, please note the error message or take a screenshot. Contact with
your IT department and provide the error message as well as the log file of the installation.

StormGeo . USER MANUAL . s-Insight | Log // 80

8.2.4 Configuration import fails
When loading a configuration file one of the following error messages may appear:

The configuration file is not valid since it was not requested for this ship

This occurs when you try to import a configuration that was not requested. It is neither possible to
import old configurations nor those for other vessels.

Instead, please request a new configuration file from the server.

File is not a valid master data configuration. The file may be outdated or is not valid for this ship.

Usually this occurs when the configuration file is too old because it is likely to be incompatible.

Provide the configuration file to your IT department and ask for assistance.

8.2.5 Configuration not up-to-date

The warning 'Configuration not up-to-date' indicates that the current configuration is outdated since
a new version has been installed. It is strongly recommended to request a new configuration file
immediately to enable reporting according to the latest version. For this, simply follow the
instructions given.

1. Click “Send request to shore” to request a new configuration by the standard method for
sending reports.

2. Confirm sending when being asked by the e-mail client.

3. Wait for an e-mail with attachment from s-Insight | Log Server. This usually takes a few
minutes, rarely longer than an hour.

4. Save the attachment to local folder.

5. Click “Import new configuration” and select the file you have saved in the previous step.
If successful, the message will disappear and s-Insight | Log Recorder is ready for reporting again.

The procedure above needs to be done only once. This also applies to network installations.

8.3 Login

8.3.1 Invalid password

Starting the application requires a valid password. This password is case sensitive, for example
'PASS' is not the same as 'pass'. In case of problems, you may check that CAPS LOCK key is not
active.

There is one password per vessel which is administered onshore only. If you can't remember the
password, please contact your IT department, to either get the original or a new one. Please note
that there is no 'master password' or any other way to recover a lost password on board.

// 81 StormGeo . USER MANUAL . s-Insight | Log

8.3.2 Incompatible DB
If, during login the warning 'Incompatible DB' appears, the versions of application and database do
not match.

Please check that the correct version of the installer was used.

When upgrading several machines on a network, make sure that all of them are running the latest
version. Try to login to every machine, one by one. If this works on some, but fails on others, try to
re-install the correct version on those machines. If the problem persists, contact your IT department
for assistance (see chapter Getting help).

8.4 Event overview

8.4.1 Events are disappearing

The overview only shows events within a selected voyage, or stage (if selected). In case of missing
events ensure that the correct voyage is selected.

It is also possible that you have edited the voyage, and existing events now belong to another
voyage (based on the voyage's date and time).

If you miss an event, and it is not shown when you select 'All' on the left side, please contact your IT
department and send your database file to shore (see chapter Getting help for details).

8.4.2 The 'Information' box is not showing correct values

The information box displays values gathered from several places (e.g. voyages, current Master and
last event). If some values are incorrect, please check the information source, e.g.

· Ship name: from the configuration file used for initializing the application; if the name is wrong
please contact your IT department.

· Service/trade, Voyage-stage: see voyage details

· Voyage state: see the most recent voyage event entered, or a combination (e.g. canal +
stoppage)

· Origin, Destination, ETA, RTA: see the most recent event, e.g. Departure, Noon or ETA update,
containing this data

· Last event, at: see the most recent event of the most recent voyage

· Due: shows the timespan between the most recent event, and the current date/time

· Master: see the 'Officers' page

8.4.3 The 'Remaining on board' box is not showing the correct values
The ROB box is calculated from the events where you enter fuels/oils (e.g. Bunkering, Mixing, and
everywhere consumptions were entered). The box is showing fuels separated into HS and LS,
filtered by (fixed) sulphur limits.

In case these values are not showing what you have expected please check your events. Most
events have a 'Check ROB' box inside which you can expand and see the remaining fuels/oils after
that specific event.

StormGeo . USER MANUAL . s-Insight | Log // 82

It is most likely that one (or more) event(s) from now back to where the fuel/oil was bunkered
contains wrong values. You can either trace back all consumptions to spot the error, or wait for the
next sounding correction which will correct the ROB.

If you feel the events are correct and ROB box is still showing the wrong values it is highly
recommended that you contact your IT department for assistance and provide your database for
deep analysis of that case (see chapter Getting help for details).

8.4.4 The event menu shows some events grey (with a '?' next to them)
Some events belong together, e.g. Arrival and Departure. Whenever you enter an arrival event, the
next voyage event (aside from noon rpt. and ETA update) would be a departure or sailing notice.

To ensure you don't overlook these events only the ones that are matching are offered.

If you entered a canal passage some events cannot be entered (e.g. begin of sea passage) since
you have to leave the canal first.

In case some data is missing in the application, and you have no chance to fix it, you can still select
any of the grey menu entries, and enter all data. The mechanism which controls which items are
shown in grey will only look at the most recent event, so things will most likely repair themselves
that way.

If you feel like an event should be possible but isn't, please contact your IT department and send
your database (see chapter Getting help for details) and provide details on which event you
expected to be possible, and why.

8.5 Edit Voyages

8.5.1 Cannot delete a voyage

Only the most recent voyage may be deleted. The only voyage left in the application may not be
deleted at all.

If you tried to delete the latest voyage with at least one voyage remaining there's something wrong
that needs technical assistance. Please refer to chapter Getting help and contact your IT
department.

8.5.2 Invalid voyage name

The voyage name must follow a specific name scheme. The rules on how a voyage name may look
like are made by the ship operations department (and are NOT hard coded in the application); please
contact your operator for details.

8.5.3 Red fields appear on the right side, the voyage cannot be saved
Whenever some data is missing or wrong red fields will appear upon saving, and you may not save
your voyage details unless you fix those errors.

Read every red box carefully and correct the voyage details as necessary.

In case you have corrected the fields, but a red message is still showing please take a screenshot
(see chapter Getting help for a description of how to do so) of all voyage fields and the error
message that won't disappear, and contact your IT department for assistance.

// 83 StormGeo . USER MANUAL . s-Insight | Log

8.5.4 After configuration import new values, e.g. new services, are still missing
If you import a new configuration file, and want to use e.g. new services, you can only do so for new
voyages. See Importing a new configuration for details.

Old voyages are always linked to the configuration file that was valid when the voyage was created,
and this cannot be changed. You can, of course, try to delete the voyage in question and re-create it,
but this is only possible for the most recent voyage.

8.6 Entering events

8.6.1 Durations fields are complaining

Duration fields have a special routine for value checking. Each duration field refers to a previous
event and is calculated (and usually prefilled) when you create the event.

When you enter a duration that does not equal to the calculated value the field is showing a yellow
text next to it. Please make sure the duration you have entered is correct then.

This may also happen if you insert events afterwards, e.g. inserting a Noon report on sea passage
may cause the later event to have a wrong duration at the machinery operations fields.

If you observe wrong calculations of durations frequently, please report this issue to your IT
department and provide your database for deeper analysis (see chapter Getting help for details).

8.6.2 Port field is complaining

The port field, which is used in many events (and the voyage, too) has two different port lists behind
the scenes.

When you enter a port it is first checked against the operator's port list, a list that was specified to
help you picking the correct ports where different UN/LOCODEs are possible, and to filter uncommon
ports. If you enter a port that is not on that list you will get a yellow warning.

Secondly the port is checked against a list of all known UN/LOCODEs. If the port is not on the second
list, which is the list of all currently known ports in the world, a red message will appear as the port
is unknown to the system.

If you receive an error for a port where you know it must be in the system please contact your IT
department and operator, which must both check their port lists for completeness.

8.6.3 Too many (or wrong) red/blue boxes appear upon pressing the 'Check'
button
The 'Check' button will run all available check routines for the current event and show the result on
the right side. Sometimes rules are simple, e.g. mandatory fields must be filled out, and sometimes
rules are complex (e.g. duration rules, consumption checks).

Please read the message in the box (after opening it) carefully and locate the error, fix it and press
'Check' again.

If the error/issue does not disappear, or cannot be fixed at all (e.g. if it complains about a field that
does not exist in the event), please save the current event and contact your IT department providing
your database (see chapter Getting help for details).

StormGeo . USER MANUAL . s-Insight | Log // 84

8.6.4 Numeric values lose their precision when leaving the field
Some fields expect numeric values, e.g. fuel parameters, sailed distance, position. You may enter the
precision (i.e. the part after the decimal dot) as long as you like, but it gets cut off as the cursor
leaves the box.

This is normal since not all values require a high precision. You may enter a high precision, but it gets
rounded. The rounded value is then transferred to shore.

8.6.5 After configuration import new values, e.g. new services, are still missing
If you import a new configuration file, and want to use e.g. new ports, etc., you can only do so for
new events. See Importing a new configuration for details.

Existing events are always linked to the configuration file that was valid when the event was
created, and this cannot be changed. You can, of course, try to delete the event in question and re-
create it, but this is only possible if it has not been sent to shore yet.

8.7 Sending reports

8.7.1 Some reports are not sent

When sending reports, it may happen that some reports are not sent. Basically, events showing
validation errors when the 'Check' button is pushed are not sent and are marked correspondingly.
Open those reports, fix the remaining errors and try to send them again.

If the problem persists or if the events cannot be sent otherwise please contact your IT department
(see chapter Getting help for details).

8.7.2 'Voyage' events

All changes to the voyage including new stages and even new voyages are being sent automatically.

8.7.3 Errors when sending reports

If you have connected directly to your e-mail application and receive an error, contact your IT
department.

The application uses the MAPI interface for interacting with e-mail programs, which is known to have
issues with several e-mail programs. See chapter System requirements for more information.

If the problem persists, switch to file export and send the files manually as attachments.

8.7.4 Missing reports

In case of a missing report, a reminder is sent by the server . Go to 'Communication', open the
'Archive' box, select the report to be resent (identified by ID) and press the 'Resend report' button.

// 85 StormGeo . USER MANUAL . s-Insight | Log

9 Getting support

In case of problems please provide additional information to your service request because this helps
reproducing and solving the problem quickly. Please read the instruction below to collect supporting
information.

9.1 Installation problems

In case of installation problems, please provide the file Install_sLog_Recorder.log located in

· %commonprogramfiles%\Stormgeo\ (32 bit systems) or

· %commonprogramfiles(x86)%\Stormgeo\ (64 bit systems).

For this, you may by copying one of the strings above to Windows® Explorer to open the folder.

9.2 Application problems

In case something goes wrong, please follow the instructions below:

1. Create a screenshot of the About dialogue showing the version and other important
parameters of the installation.

2. Describe the action during which the issue occurred.

3. If possible, provide a screenshot of the situation where the issue occurred.

Use Alt+PrintScreen or PrintScreen to create a screenshot, process it in an external tool like MS

Paint, or MS Word or copy it to the clipboard. Save the file (.PNG is the best option for
screenshots) and send it via e-mail.

4. Use the built-in support to to create a data package, see Support tool.

5. Create an e-mail including all of the information above and send it to your IT department or to
[Link]@[Link].

9.3 Support tool

A built-in support tool is part of the application. To open it, click on (?) in the upper right corner of the
application and select 'Support'.

StormGeo . USER MANUAL . s-Insight | Log // 86

Check the options Logfiles, Reports and Database as requested by Service and Support and send
the package by to [Link]@[Link].

The program’s data folder containing the database, configurations, logfiles and reports can now be
accessed directly via Support menu. However, access should only be needed rarely, e.g. to solve
issues.

Use this option with care. Do not modify data unless requested to do so, e.g. by Service and
Support. Keep in mind, that any modifications may have severe consequences to the program.

10 Appendix

10.1 System requirements

To run this program your PC must meet the following requirements:

· A decent workstation with at least 1 GB of RAM, multi core CPU is highly recommended. The
program itself will require about 50 MB of hard disk space; more might be required for required
packages below.

The minimum screen resolution is 1280x800, though a higher resolution is recommended

(1400+ x 1000+) to avoid excessive scrolling as there is a lot data visible on screen.

o When running the program from virtual machines you may need to disable WPF
(Windows® Presentation Foundation) hardware acceleration. Some virtual machines have
very generic or even broken video drivers which makes the rendering otherwise
impossible.

// 87 StormGeo . USER MANUAL . s-Insight | Log

 o When running lower screen resolution you may experience cramped and/or unreadable
screen content.

· Microsoft Windows® Vista or later

· Microsoft® .NET Framework, Version 4.7.2

o It is recommended to have the latest version of the .NET framework installed (e.g. by
using Windows® Update). Using an outdated version of the .NET framework may lead to
issues that are usually very hard to track down.

o Please note: The standard installer (for online/flash drive distribution) does not include
the .NET framework runtimes. A bigger program installation (for DVD distribution) is
available which includes the framework and checks for its existence on start-up.

· Administrative rights may be necessary to install the program. Also make sure you are
allowed to modify the access rights of the data folder.

· For multi-client access to the data you will need a stable network connection and a
workstation or server providing the database at all times. You may need administrative rights
to modify the access rights for the network share that is used to share the database among
the clients.

· A PDF reader of your choice to show the manual(s). The user manual is PDF version 1.4, thus
most PDF readers should be just fine.

· In order to send event reports directly from the program you need a MAPI compliant e-mail
client. If you don't want direct mail access or MAPI is not working for you, you may also use
the file export functions.

10.2 Known issues

MAPI

Please note: Although MAPI is offered by most mail applications it is known to have issues
depending on your mail client and/or its version:

o Microsoft Outlook®: The confirmation window may appear in the background of the active
window, the application seems unresponsive but in fact is waiting for your response from
a window in the background.

o Mozilla Thunderbird: If the mail cannot be sent by Thunderbird, errors are not always
passed to the MAPI interface, which makes it impossible for the program to detect that
the sending has failed.

o AMOS Mail: You need to specify a data path (during installation) with less than about 90
characters (to be precise: file name and path of the attachment must be <120 characters;
the program uses the format 'reports_YYYY-MM-DD_HH-[Link]' (28 chars) for automatic
file names). When using longer directory names AMOS mail will not be able to send the
file, causing strange error messages.

o Skyfile® Mail: Skyfile provides subaccounts which cannot be selected from within the
application. Whenever you send a report using Skyfile the last configured subaccount will
be used. It is recommended to configure automatic file pickup for Skyfile instead.

Other e-mail clients

Even if you don't use MAPI you still need any E-Mail application available in order to send event
reports to shore. Also be aware of the following known issues with other mail applications:

o Windows® Live Mail: when attaching XML files to an e-mail Live Mail will in some cases
attempt to add some line breaks to the file. This will very likely break the file, rendering it
unreadable to the server and producing an error message.

StormGeo . USER MANUAL . s-Insight | Log // 88

10.3 Reporting instructions
In addition to this user manual the application optionally includes company-specific reporting
instructions. Both user manual and operator instructions are in PDF format requiring a suitable
reader, see System requirements.

To make company-specific reporting instructions available, copy the file '[Link]' to either
the application directory or to the data path next to the file '[Link]'. The application will then
show 'Reporting instruction' in the help menu, providing quick easy access to your documentation.

If available during installation, you can also place the file '[Link]' next to the setup file.
It will then be made available automatically during installation.

10.4 Third party licenses

The following third party products are used within the application. The respective license texts are
also included in the distribution, the licenses are stored in a folder 'Third Party Licenses' within the
application path (file name is noted after 'see also' below) if redistribution of the license is
mandatory:

· DotNetZip - Zip and Unzip in C#, VB, any .NET language

License: [Link] (see also 'DotNetZip Library [Link]')

10.5 Trademark legal notice

Microsoft, Excel, Outlook, SQL Server, Silverlight, Visual C++, Windows, Windows Vista and Windows
Server are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.

Mozilla and Thunderbird are registered trademarks of the Mozilla Foundation.

AMOS Mail is a trademark of SpecTec Group.

Skyfile is a registered trademark of Vizada.

All other trademarks cited herein are the property of their respective owners.

// 89 StormGeo . USER MANUAL . s-Insight | Log

s-Insight | Log is integral part of StormGeo’s s-Suite.

// About s-Suite
s-Suite is an integrated solution for voyage planning, navigation, ship routing and fleet performance management – all from
StormGeo.

// About StormGeo
StormGeo is a global provider of weather intelligence and decision support services, with leading solutions for shipping, oil
and gas, renewable energy, utilities, cross industry and aviation. StormGeo’s products and services help clients manage
risk, optimize performance, reduce costs and increase revenue. The company has 24 offices in 18 countries, including eight
24/7/365 global operations centers. As a participant in the UN Global Compact for Sustainable Ocean Business, our
passion for weather and the protection of natural resources motivates us to support our clients in making informed,
environmentally responsible business decisions.