MAC - Manual [Link]

com/manual/vessel-4-3-0/

MAC - Manual

M.A.C. System Solutions

Intro
The MAC PMS System is a distributed system, it consists of two primary software components a vessel software and an office software. Data is manually reported by the vessel crew and
optionally collected by additional hardware components directly from available sensors on board. The collected information is transmitted to shore side and processed by the office system
where it is being displayed for further analysis (Data Transmissions).

The manual reporting system is called reporting module while the collection of sensor data is from here on referred to as the online module.

Reporting is manual work and has to be performed by the vessel crew. Two different login accounts exist for that purpose.

Both accounts can see all data entered-into/generated-by the system. The write rights are limited to the responsibility according to the department. The deck department (captain, first-mate)
will enter nautical-data, voyages, schedules and cargo. The engine department (chief engineer, second engineer) is responsible for consumptions, engine-data, counters, running hours,
remaining on board and bunkering. The exact reports that need to be or can be filled out differ and are subject to change depending on demand by the industry (or type of vessel).

Since the user interface is a web-based application reporting can be done by crew members everywhere where a pc is available and connected to the ship-network. Reported information can
be data read from sensor displays (i.e. gauges, digital counters, …) as well as data from external systems like a cargo management software.

The online module uses real-time collected data from sensors and displays them to the vessel-crew. If real-time data is available it is compressed to data-points every 15 minutes including
deviations and mean values. These datasets are included in the transmissions and allow more detailed analysis of the ship performance.

The online module requires the setup of multiple Data Collector’s and in most cases additional cabeling to collect the real-time data. The hardware and software used is based on an in-house,
modular, standard product, which will be modified/combined depending on vessel or vessel series requirements.

This document is structured in a way to first give you a conceptual and system architectual overview, both equally relevant to the office and vessel version. If you want to start using the
system immediately jump to the user guide.

Reporting

Reports are seperated in two categories, event-based and adhoc. Event based reporting covers the daily business routines — also known as noon-reporting. Adhoc reports can be created as
required by the vessel crew, i.e. after bunkering fuel a bunker report should be created.

Adhoc Reporting

Adhoc reports can be created by both bridge and ecr. Depending on the user different kinds of adhoc reports can be created:

Event-based Reporting

Events will have to be created by the bridge user on a regular basis (Create Event). The event report will ask you to describe an event as a point in time (i.e. Noon 12:00) as well as additional
information regarding the reported period (i.e. opertional mode of the last 24 hours was maneuvering).

Note The reported period will be the duration between the last and current event (i.e. 24 hours).

The type describes what is currently happening at the reported point in time:

Type of Event Description

Arrival Vessel is arriving at the berth position for port stay
Departure Vessel is leaving the berth position during port stay
BOSP Pilot has left the vessel and vessel reached operational speed
NOON Noon event (12:00 LT)
EOSP Before pilot has come on board and slow down from operational speed starts.
Anchor / Drifting Start Beginning of Drifting/Anchorage period
Anchor / Drifting Stop End of Drifting/Anchorage period
Other Other event types not represented, use remark field to clarify

The reported period consists of the operational mode as well as a charter field. The charter field describes if the reported period was performed under charter, without charter or off-hire.

The Operational Mode:

OP-Mode Description
Drifting Vessel has been drifting during the reported period.
Anchorage Vessel has been anchored during the reported period.
Sea Passage Vessel has been operating under sea passage conditions during the reported period.
Docked Vessel has been alongside during the reported period.
Port port stay (12:00 LT)
Maneuvering Vessel has been maneuvering during the reported period.

Events will create child reports that need to be filled out by the crew. Child reports can not be created or deleted seperatly since they belong to an event, deleting an event will also delete its
child reports. After event creation child reports will be unconfirmed (waiting to be filled out).

All events create the following child reports:

Further reading:

View all available data collected by manual reports.

1 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Online

The online system will collect sensor data on board the vessel, two or three Data Collector’s (depending on the vessel) are required for monitoring. Live values will be available on board and
can be viewed using the web interface (Performance Dashboard). A typical data collector setup would require one unit to be installed on the bridge and one in the engine control room. 15
minutes average values will be logged and transmitted to shore, the office and vessel both can view the logged data using the Datalog view.

Note The online module is optional and not all vessels equiped with the reporting module will also be equiped with the online module.

The following type of sensors can be integrated:

Sensor / Device Interface

tank log tcp
ae power powermeter, tcp
shaft-generator analog
GPS (speed over ground, position) NMEA 0183
speed-log (speed through water) NMEA 0183
anemometer (windspeed/-direction) NMEA 0183
rudder position NMEA 0183
water depth NMEA 0183
draft serial or analog
shaft power meter (rpm, power, torque) modbus-tcp, serial or analog
trim/list analog
flow meter (mass or volume based + temperature) modbus-rtu or digital (pulse)

The system is able to support many different types of vendors, further we offer our own sensors/systems for: trim/list and shaft power.

Vessel - Configuration
Baselines

Baselines describe expected performance and will be configured by head office if available. When available, baselines will allow the user to analyse deviations from expected performance or
degradation over time i.e. due to hull fouling or engine problems. If baselines are available and configured they will enhance the analysis (i.e. charter party, basic curves).

Flow Meter

Flow meters (FM) can be configured depending on the fuel system on board. We support flow meters to be configured for:

Main Engine

Aux.-Engines

Common (ME+AE)

Cylinder Oil

Boiler

If the vessel uses a uni fuel system the "missing" flow meter will be calculated based on the other available flowmeters:

FM-ME and FM-AE available

No calculation required

FM-Common and FM-AE available

ME = COMMON - AE

FM-Common and FM-ME available

AE = COMMON - ME

For vessels that use volume flow meters the system will calculate the mass using the Volume Correction Factor, to be able to do that temperature and density are required. All consumption
data collected from flow meters is considered net consumption.

Vessel - Manual
User Guide

How to access the system

The vessel web interface is reachable from anywhere in the ship network using a web browser (ie Chrome, Firefox).

You will be prompted to login, depending on your role on board of the vessel login as ecr or bridge user to proceed.

Username Password
bridge bridge
ecr ecr
Note If the system is not reachable using the specified address please contact the technical office.
Important Internet Explorer is not supported if you encounter problems using internet explorer install firefox if possible (or contact us for further information).

Quick Start

Creating your first report takes only a few minutes, login using the bridge or ecr user and select Reporting from the main navigation. The timeline view will be opened (which can be ignored
for now, it will be explained in a later section) immediatly under the main navigation the sub navigation for reporting will be displayed. On the right side you will find the Create Report
menu, depending on the user different reports will be available — select Remark (the remark report is available to all users).

2 von 16 04.01.2019, 16:04

MAC - Manual [Link]

The remark form will open up, each form field may have additional information which will be indicated by an info icon next to the field name. Move your mouse over the icon to display the
information, i.e. viewing the text for Name informs you that you should use your full name.

When you are done filling out the form hit Create.

If your input data is valid you will get redirected to the remark details displaying the supplied data, from here you can open up the report to edit it (i.e. if you need to fix an error) or delete the
report. The details view will be reachable by using the timeline or overview if you need to edit/delete the report at a later point in time.

Next Steps:

Check the Todo List for what jobs need to be peformed.

Start your noon-reporting by creating an event (bridge) and filling out open reports (bridge & ecr)

Todo List

The following table gives you an overview of when and what jobs need to be performed. You can directly jump to the guide or description required to perform the selected action.

Create Event

Before creating an event make sure you created at least one voyage. To create an event use the report creation menu as seen in the Quick Start. If the create event menu item is not visible
check that you are logged in as bridge since only the bridge user is allowed to create events. After clicking the create event menu item the input form will be displayed and you can start to
enter data.

If you are not sure which type of event to select please read the Event-based Reporting section. Date and time have to be entered in local time. It is important to select the correct timezone for
UTC conversion, to see examples of how the system calculates the UTC time based on your input check out the paragraph on Date & Time. Events must be created and filled in chronological
order as they occur.

The reported period (see picture, framed in red) shows the time from the last reporting event till the selected date in the current event. As well as fields related to the reported period like op-
mode and charter (ie 24h of maneuvering under charter).

After event creation all reports that need to be filled out become available easily accessible by using the timeline view.

3 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Important Avoid changing date/time/timezone of events or creation of events out of sequence (none chronological). Do not create events using the same date/time twice or skip events.
Important An event should be created at least once every 30 hours.

Fill Out Event

After creating an event you can start to fill out the report by clicking on "Fill out Reports".

In the next view, you will guided through all required data step by step. Each report has to be confirmed by the "Save & Next" button in the bottom right corner. The top will display each step
with its current state, completed (confirmed) reports are shown in green and open (unconfirmed) reports in grey. You can jump between steps, to fix errors or check the summary while filling
out, by clicking the steps.

If the assistant button appears at the top you can use automatically fill data fields (see Assistant). Only available if online module is installed and enough data has been logged for the
Note
period.

The steps/reports differ from ecr to bridge user:

After filling out all event child reports, a summary will be displayed. There you can double-check if the data provided is correct.

4 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Create Adhoc Report

Creating an adhoc report has been explained by the Quick Start. All adhoc reports follow the same basic pattern, if you have trouble to make sense of a fieldname please consult the info text
next to the form field label.

Note If you are missing an adhoc report that you want to fill out please check the Adhoc Reporting section to see if you have the required permissions.

ROB & Consumption

The fuel oil and cyl.-oil parts of the ROB report are calculated automatically. Use the following example steps to go through the process of reaching the final ROB figures using all connected
reports.

Preconditions

We already filled out the counters and running hours reports and arrived at the consumption reports.

Step 1: Fill out fuel oil consumption reports

In the following example the "HFO" report will be filled, therefore we click 'Yes' when asked if "HFO" has been consumed.

Using our experience we estimate the "Fuel Sludge” in percent of the fuel to arrive at our fuel consumption including sludge (gross). By entering for example 0.9% fuel sludge a value of 0.522
mt HFO (net) will result in 0.557 mt HFO (gross) for the main engine. With 0.035 mt sludge added or roughly 0.9% (due to rounding).

The calculated gross consumption is the value by which the ROB will be reduced by later.

Note You can skip the automatic conversion by not entering fuel sludge percent and using your own figures for gross/net.

5 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Step 2: Remaining consumption reports

After saving the first FO consumption report. The system will ask if other FO types have been consumed. We answer with no and proceed to step 3.

Step 3: Fill the "Lub Oil" report

Fill the report acc. to the consumption of cyl. oil/circ oil and proceed to step 4 by clicking "Save & Next".

Note Cyl.-oil fields and feedrate settings are only available when 2-Stroke engines are configured.

Step 4: Fill the "ROB" report

When previous reports have been filled, the system will present calculated ROB figures based on the previous stock reduced by the consumed (gross) amounts. These values have to match the
log book data for the same point in time. If additional corrections/soundings have to be reported see Step 4.1.

Fill out the remaining manual fields (like fresh water) and finish the report by clicking "Save & Next".

Important Bunker amounts will be included automatically when reporting adhoc bunker reports and do not require corrections.

Step 4.1: Corrections and Soundings

In certain situations a sounding should be documented and can result in a correction of the stocks. You can report corrections and soundings by checking the corrosponding box at the top.
This will open up additional fields for data entry (see picture). Corrections will adjust the ROB by adding or subtracting the provided amounts.

Note When stock corrections are allowed or should be performed is depended on the head office and charterer.

6 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Important Soundings will not change the ROB value. "Sounding” is only a documentation of a sounding on board of the vessel.

Bunkering & Sludge Disposal

All bunkering and sludge disposals have to be reported, create the report using the Create Report menu (see Quick Start). After filling the report, the "BDN”, "FO analysis” and "letter of
protest " (if available) have to be uploaded to the report. If the documents are not available in time, they have to be uploaded after receiving them.

Note The Bunkering report will automatically update your ROB report.

7 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Cargo

The cargo report needs to be confirmed every event and will open up after each nautical save inside the multi step fill out process (for user bridge).

Choose a cargo action between None, Loading/ Unloading Operation or Update. Depending on the selected action the input fields will be enabled or disabled.

None: If no significant changes occured, choose None.

Loading/Unloading: A Cargo operation has finished and new loading information and forces have been calculated/provided by the loading computer. These values have to be filled as
required by the form.

Update: Vessel has been retrimmed or other significant changes to vessel forces apply and cargo remains unchanged.

Finally confirm the report when everything is filled as required by clicking "Save & Next".

Changing fuel parameter

When the fuel system changes fuel types (i.e. during ECA-zone passage) or fuel quality (different density, net caloric value or sulphur content) it is important to update the fuel parameters as
soon as possible. Updating fuel parameters for the online module is done by accessing the Performance Dashboard and using the change parameters button.

Shifting inside Port

Shifting in a port can be reported by simply continuing to report noon events with op-mode port (without additional events). Separate departure or arrival events may not to be reported.

Hardware Changes

When replacing hardware i.e. an GPS component has been replaced, please validate that the position and speed over ground still are being displayed correctly using the performance
dashboard or by checking the datalog table of the online module. If sensor data becomes unavailable after hardware replacements please contact your technical office department.

Assistant

The assistant helps the user to fill in different data by accessing logged data collected from sensors. The options given in the assistant are based on the sensors installed. By clicking on the
arrow next to "Auto Fill", you can check/uncheck the options you need or don’t need. When using Auto Fill, automatically filled fields get an orange border and a confirmation message pops
up on the top right corner. You can either confirm with the automatically set values, cancel the inputs or send an Error Report if values do indicate equipment failures.

Note Only available if online module is installed and enough data has been logged for the period.

8 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Error Report

In case an error occurs with the automatically read values from the assistant, it’s possible to send an error report. By clicking on the error button, a new window pops up to select the sensors
affected. Clicking on next gives different choices/questions for better troubleshooting. "Save" completes the whole process and sets the sensor to a failure state, which will be displayed (next
to the selected timeframe at the top) indicating the number of the affected sensors (see picture).

Note As long as the failure state is set, it’s not possible to auto fill the affected sensor again.

As soon as the problem is solved, you can click on the exclamation mark icon on the top of the page and select clear for the respective sensor.

Analysis

The analysis lets you take a look at reported and online data as graphs and charts. Online data is color coded using shades of orange, while reported data uses shades of blue, with one
exceptions the charterer speed order which will be displayed as green. baselines (provided by office) and charter-party (if configured) will be displayed green as well.

At the top of the analysis view you can see the vessel profile, the profile displays the speed over ground for both online and reporting data. Both lines should overlap as much as possible,
naturally online data has a higher resolution and not all details can or should be reported.

You can zoom into charts with an date/time axis or by selecting a segment in the overview using the mouse. The selected segment will reduce charter party and basic curve data
Note
displayed to the selected timeframe as well as all other sub views.

In addition to the more traditional charts like line and bar charts, heat maps are used to visualize the density of occuring values. Values are grouped into a value-grid and the quad occupying
the grid position fades from total transparent (almost zero values) to fully opaque (maximum amount of values for the selected timeframe), to see heatmaps in action take a look at the charter
party or basic curves view.

Consumptions used inside the curves and charter party views are based on gross for reporting and net for online data, take into consideration that consumptions can diverge up to
Note
approx. 1.5% due to sludge.

The following analysis sub views can be selected:

Charter Party

Displays a heatmap for ME consumption (mt/day) against speed (SOG). If a charter party is configured a green line will indicate how close the vessel meets the requirements. Since charter
parties require certain conditions the view filters out values that occured during rough sea (⇒ wind greater/equal 4 [bft]).

Basic Curves

Displays performance distribution based on different parameters. The red quad is the lastest reported value, which is available if the selected timeframe includes the current date.

9 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Nautic

Speed

Displays vessel speed over time. The charterer speed order should overlap with SOG (reported and online) as much as possible during passage — if no outside conditions prohibit it.

Track (Map)

Shows the reported or GPS tracked route of the vessel.

Weather

Displays weather conditions, wind strength (beaufort) and wave/swell height.

Draft/Trim

Displays vessels trim in meters as reported and additional online data from draft system and/or trim-list sensors depending on availability.

ME

Load / RPM

Monitored and reported load and rpm of the main engine.

FOC / SFOC

Displays consumption for ME over time using [mt/24h].

COC / SCOC

Main engines cyl. oil consumption and specific consumption (in reference to main engine load/energy).

AE

Load

Shows the load in kW and % of the aux engines. AE load is calculated based on kWh/runningHours and displayed for complete duration of event regardless of actual time of use (usage
distribution during event is not reported).

FOC / SFOC

Displays consumption for AE over time using [mt/24h], as well as approximated SFOC.

Running Hours

Shows the running hours of aux engines in different colors.

AB

Shows aux. boiler consumption information and external (possibly influential) factors like ambient temp. and ME load.

Histograms

Shows distribution of ME RPM, ME Power, SOG, STW, Draft and Trim, to determine operational ranges.

Other

Timeframe Balance (Mixed)

10 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Calculate consumptions based on start/end ROBs for a specific timeframe, in relation to consumption and bunker reports.

Timeframe Balance (Datalog)

Calculate consumptions based on data logging.

CO2 (MRV)

Displays CO2 emission data.

Reporting

Selecting reporting from the main navigation opens up the reporting view and reporting specific sub-menu, from here you can open up the timeline view (default) or all of the overview tables
available for reports (split into Adhoc Reports and Event-based Reports).

Timeline

The timeline displays all reports in chronological order (except the schedule). Clicking on a report will open up the details-card which will give you a brief overview of the data that has been
reported, by default the last report will be selected.

Event based reports are colored white and different symbols will be displayed for different event types. Adhoc reports will use colored quad icons.

Each event based report can have a red indicator to the right showing the open report-count, the black indicator will show reports which have comments connected to it.

The next scheduled port will be displayed at the top of the timeline for estimated time of arrival and departure. Edit the schedule report and change the basis from Long Term to Coastal when
getting closer to the destination. Setting the basis to coastal opens up additional fields (Actual ETA/ETD), this allows to report expected delays or early arrivals/departures.

Overviews

Report overviews display the selected type of report as a table for easy comparison, to open up a report overview use the reporting sub navigation and click on Adhoc Reports or Event-
based Reports depending on the reports you want to view.

Some reports include optional attachments, attached files will be displayed by checkmark to the left side of the table. Report comments will use the same check mark to show that a remark is
available for a certain report. To view the remark or download an attachment select the row of the report to enter the details view, the remark will be displayed in full and the download links
will be available at the bottom of the page.

When viewing event-based reports — red rows indicate that a report has not been filled out yet. The adhoc schedule report displays red rows too, marking entries as being in the future.

Validation and Notification

All reports will display errors if the entered data is not within the constraints expected. The error message appears above the form explaining what went wrong, in addition a red border will be
used to indicate what form fields need to be edited.

Some reports will use notification popups to help reduce mistakes, or speed up the reporting process.

Online

If your vessel is equiped with the online module it is directly accessible from the head navigation, after selecting the online module the default online view (Performance Dashboard) will open
up. Under the head navigation you will find the online sub navigation where you can select the Performance Dashboard as well as the datalog.

Note For more information about the datalog check out the general information (see: Datalog).

Performance Dashboard

The dashboard will display live data collected from connected sensors and devices.

11 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Top to Bottom

Fuel Paramter

The top element displays the currently configured fuel parameters for flow meters available on the vessel (see Changing fuel parameter).

Map

Below the fuel parameters you will find the map displaying the current position. At the bottom right of the map the wind forces will be displayed (relative to the vessel).

Gauges

At the bottom gauges display the current engine load and consumptions including calculated values like sfoc. Additionally nautical values for speeds, trim/list and draft data is available
on the left. Flow meter gauges also include the fuel temperature at the bottom of each gauge (in °C).

Datalog

The datalog view shows all data that has been logged as part of the online module. Values will be logged every 15 minutes.

Reports
Event-based

see Fill Out Event

Cargo

12 von 16 04.01.2019, 16:04

MAC - Manual [Link]

All values according to loading computer calculation (final result after departure).

When creating a cargo report, the first report always has to be a "Loading/ Unloading Operation"- Action to document the initial state.

Counters

Will display the fuel and cyl.-oil counters matching the counters available on board. The counter report will display deltas to show the difference between previous counter reports and now. If
no flow occoured the previous value can be copied over (using the button next to the input).

Engine Data

This report includes detailed information about the main engine as well as the electrical energy provided by aux.-engines and shaft generator. Several input fields, that only are required for a
running main engine, are locked and get activated by entering a value for running hours. "Power" is a calculated value which appears when runninghours and energy is entered.

While filling out an engine data report, the system will calculate power based on your input of running hours and energy. If the calculated power is too high or low a warning will be displayed.

Nautical Data

Entering "0" in the "Made good" fields lock the Environmental Conditions at the bottom.

ROB

Rob reports provide information of the remaining fuel-, circulation-,cylinder-oil, fresh water, main engine sump tank, sludge and bilge water on board.

Running Hours

Running Hours show the different engines and the time they’re running. In case sensors are installed, it’s possible to use "Auto Fill" for the running hours to get the Aux. Engine values.

Fuel Oil Consumption

HFO (Heavy Fuel Oil) LSFO (Low Sulfur Fuel Oil) MDO (Marine Diesel Oil) MGO (Marine Gas Oil)

Fuel Oil contains information about different fuel parameters like density or fuel sludge and the net/gross consumption. It contains HFO, LSFO, MDO, MGO.

Lub Oil

Lub Oil contains information about the consumption of cylinder oil like BN40 or BR70 and the amount of circulation oil refilled.

Adhoc

Crew Change

Local Date

Local Date - when crew change occured

Crew

Captain

Given name followed by surename - full style

C/O

13 von 16 04.01.2019, 16:04

MAC - Manual [Link]

Given name followed by surename - full style

C/E

Given name followed by surename - full style

Garbage Disposal

Method of Disposal

Method of disposal operation for the reported amounts.

Port

Port which received reported amounts.

Amounts Disposed

Plastics

Amount of plastics disposed, MARPOL category A.

Food Wastes

Amount of food wastes disposed, MARPOL category B.

Domestic Wastes

Amount of domestic wastes disposed, MARPOL category C.

Cooking Oil

Amount of cooking oil disposed, MARPOL category D.

Incinerator Ashes

Amount of incinerator ashes disposed, MARPOL category E.

Operational Wastes

Amount of operational wastes disposed, MARPOL category F.

Animal Carcasses

Amount of animal carcasses disposed, MARPOL category G.

Fishing Gear

Amount of fishing gear disposed, MARPOL category H.

E-Waste

Amount of electronic waste disposed, MARPOL category I.

Cargo Residues (None-HME)

Amount of cargo residues disposed, MARPOL category J.

Cargo Residues (HME)

Amount of cargo residues hme disposed, MARPOL category K.

Schedule

Other

Captain

Given name followed by surename - full style

C/O

Given name followed by surename - full style

C/E

Given name followed by surename - full style

Actual ETA

Actual ETD

Voyage

Voyage No.

Acc. charterers voyage no. to be inserted before the new voyage starts

Start Date

Local Date - when new voyage starts

Bunkering

Timezone

Actual time zone

Charterers Bunker Surveyor

Survey Company

Name of Survey Company, e.g. SGS, Intertek etc.

Fuel Oil

HFO

Amount of HFO bunkered acc. to BDN

HFO discrepancy

Amount of missing HFO

LSFO

Amount of LSFO bunkered acc. to BDN

14 von 16 04.01.2019, 16:04

MAC - Manual [Link]

LSFO discrepancy

Amount of missing LSFO

MDO

Amount of MDO bunkered acc. to BDN

MDO discrepancy

Amount of missing MDO

MGO

Amount of MGO bunkered acc. to BDN

MGO discrepancy

Amount of missing MGO

Cylinder Oil

BN40

Amount of Cyl. Oil BN40 bunkered acc. to BDN

BN70

Amount of Cyl. Oil BN70 bunkered acc. to BDN

Circulation Oil

M/E

Amount of M/E Circ. Oil bunkered acc. to BDN

A/E

Amount of A/E Circ. Oil bunkered acc. to BDN

Other

Fresh Water

Amount of Fresh Water bunkered acc. to BDN

Samples

Port

Port where samples have been handed over

Lube Oil Samples

Number

Number of lube oil samples hand over.

Hand-over to

Company name to whom samples have been handed over.

Fuel Oil Samples

Number

Number of fuel oil samples hand over

Hand-over to

Company name to whom samples have been handed over.

Sludge Disposal

Port

Port where sludge has been discharged.

Timezone

Actual time zone

Sludge Company

Name of Sludge Service Company

Total Amount disposed

True & verified amount of all sludge (including water) given ashore

Sludge Surveyor

Survey Company

Name of Survey Company, e.g. SGS, Intertek etc.

Glossary
Date & Time

Dates will be displayed according to ISO-8601 YYYY-MM-DD, i.e. 2015-12-24.

To be able to work with dates and times consistently two timezones are supported:

the vessel timezone as used on board to be determined by master referred to as LT (vessel local time).

the timezone Zulu/UTC (+00:00)

Note When displaying charts or graphs the UTC timezone will be used, always.

Examples of same point in time with different timezones:

LT UTC
2015-12-24 12:00 UTC+11:00 2015-12-24 01:00 UTC+00:00

15 von 16 04.01.2019, 16:04

MAC - Manual [Link]

LT UTC
2015-12-25 12:00 UTC+10:00 2015-12-25 02:00 UTC+00:00
2015-12-25 12:00 UTC-09:00 2015-12-25 21:00 UTC+00:00

Data Transmissions

Since vessels are traveling almost all the time, connection availability varies and transmission speed can be very limited. Since email is the only prominent way of transmitting data,
transmissions are handled as email attachements. Depending on the communication setup and carrier, delays up to a few days are to be expected. Transmissions will be configured to
transmit automatically every 6 hours or when creating/editing a report.

Note Depending on the vessel communication setup, some email transmissions have to be manually triggered.

Gross/Net Consumption

The system supports two high level concepts for consumed fuel, gross consumption and net consumption. Gross consumption includes sludge and is in general the amount of fuel that is used
for book keeping. Net consumption is the amount of fuel after it has been seperated. The reporting module includes consumption for net and gross, the online module only measures net
consumption.

Equi Fuel (HFO Normalization)

Fuel consumption will sometimes be normalized to a specific energy value. HFO normalized values will use the caloric value of 40000 kJ (HFO_SPECIFIC_ENERGY) and the reported net
caloric value of the fuel to be normalized.

ME SFOC - ISO Correction

The following calculation is used to determin ISO corrected values for main engine sfoc net or gross.

Constants:

airPressure = 1013 mbar

heatingBasicValue = 42700 kJ

Formula:
corFactorCWT = (engine.temp_lt_cooler - 25) * 0.06 / 100
corFactorAIT = (engine.er_temp - 25) * 0.02 / 100
corFactorAIP = (1000 - airPressure) * 0.002 / 100
corFactorHeating = (heatingBasicValue / consump_hfo.net_caloric_value)
calculated.sfoc_iso = sfoc / (corFactorCWT + corFactorAIT + corFactorAIP + corFactorHeating)

Volume Correction Factor

The volume correction factor is calculated considering density and fuel temperature and is used to calculate the mass for the corrosponding volume.

Directions

When reporting directions certain fields expect approximations, ie wave direction, wind direction. The selected letters represent the following values in degree.

A0
B 45
C 90
D 135
E 180
F -135
G -90
H -45

FM Fallback Temperatures

The online module accepts volume flow meters temperatures in the range of 0-200 °C. If temperatures are out of range the following fallback temperatures will be used for mass calculation:

ME,AE,Total

85 °C

Boiler

65 °C

Consumption [mt/day]

The unit metric tons per day is used through out the system, a day is defined as 24 hours. For reporting data consumptions will be scaled to 24 hours.

ie:
Duration of Event: 25 hours
Consumption (actual): 10 [mt]
Consumption (mt/day) = 10/25*24

EEOI

EEOI is calculated from departure to next departure. Vessels of type container will will include calculations for [g/(TEU*nm)], bulker and tanker will calculate [g/(mt*nm)] only.

Event Modification Consequences

Changing the timezone, time, date or event type can lead to confusion and should only be done to fix errors. The same is true for events that are created out of order.

Changing timestamp without changing event order occurs by changing the time, date or timezone but without changing the order in relation to the events sorrounding it, ie changing
the timezone from UTC+10:00 to UTC+09:00. This change will change the duration of the event itself and the duration of the next event.

Changing timestamp that result in a changed event order will effect all connected events. Durations for the next event of the old point in time and the next event for the new position
in time.

Important All changes require the bridge and engine department to recheck all reported values.

16 von 16 04.01.2019, 16:04