Expert insight: The efficiency route to greener ships


Nav-Tech Fleet Director, Christopher Goldsworthy, has ensured that all Samskip ships enter 2018 surpassing the EU's new Monitoring, Reporting and Verification (MRV) CO2 emissions regime through measures that will also enhance vessel efficiency.

MRV demands ship owners and operators monitor, report and verify CO2 emissions from vessels larger than 5,000 GT which call at any EU port on an annual basis. As of 31 August 2017, they needed certification to show that they would be in position to collect data on a per-voyage basis from 1 January 2018 to 1 January 2019, to ensure that verified reports can be submitted to the EC by 30 April 2019, and annually thereafter.

In October 2016, Samskip incorporated Nav-Tech to bring new focus to its vessel management. Fleet Director Goldsworthy, whose experience at sea and ashore includes management roles at P&O Nedlloyd, Columbia Ship Management and Bernhard Schulte, says that the new approach has enhanced auditing and ensures quality at the individual vessel level.

“This has made introducing MRV relatively straightforward”, he says. The majority of Samskip vessels are classed with DNV-GL, and Goldsworthy represents Samskip at the Society's Nordic Committee, which regularly discusses environmental and safety issues. It was here that he began to engage with the new MRV-specific application offered through ‘My DNV-GL Portal', designed as an easy way to meet the 31 August 2017 deadline to submit individual ship monitoring plans to an accredited verifier.

"The data gathered as part of MRV will also be invaluable in our continuing strategy to optimise the energy efficiency of Samskip ships.”

Ship efficiency software

To meet its full obligations, Samskip is using DNV GL's Navigator Insight reporting software across its fleet, which accumulates voyage data from departure, through sea passage, noon, stoppages and arrival, including fully integrated bunkering and ROB (remaining on board) management.  Rather than using direct CO2 emission measurements, Samskip's reporting will be based on the energy released by the fuel burned versus transport work done (Distance/Time/Cargo). The tool also checks its data consistency against ship-specific technical information, feeding into an onshore system that collects and compares data across the Samskip fleet.

Samskip has gone a step further by choosing to have the data collected onboard in Navigator Insight presented in DNV GL's performance management portal ECO Insight, which provides comprehensive performance dashboards, benchmarks, and draws on other industry inputs such as AIS (Automatic Identification System) data, fuel quality and weather data to achieve best practice fleet management.


“It is beneficial to the development of quality ship management to be able to compare different aspects of vessel performance across the fleet,” says Goldsworthy. “We expect to find a wide variance between the performance we are logging for sisterships. We will use Eco Insight to benchmark new measures to improve vessel efficiency and emissions, such as more frequent hull and propeller cleaning, variable frequency pumps, ultrasonic devices for fouling prevention and trim optimisation, and assess them for return on investment.”  

Furthermore, Goldsworthy suggests MRV represents an opportunity as well as a challenge, which is why Samskip has surpassed its mandatory requirements by preparing plans for 10 vessels, even though some of the tonnage falls outside MRV governance.

“Samskip wanted to ensure that its older reefer vessels adhere to the same provisions as those required for MRV on a voluntary basis, as part of its overall commitment to sustainability,” says Goldsworthy. “The data gathered for MRV is invaluable in our continuing strategy to optimise the energy efficiency for all Samskip ships.”

Next Expert Insight:

Eelco de Vaal, Creative Director at Okapion, User experience for the multimodal generation.

Last Expert Insight:

Samskip Fleet Management Supervisor Gerwin Winters, Driving towards sustainable transport

Back to archive