Kristine Ludvigsen, DNV GL lead of the Open Simulation Platform (OSP) project explains that simulation models \u201cfollow an asset from design to operation\u201d but are typically not made available for cooperation as they run very close to the manufacturers\u2019 IP.<\/p>\n
But there\u2019s more reason than ever to find a collaborative approach.<\/p>\n
\u201cIt all starts with the shipbuilders. Most, for different reasons, will be buying in the equipment from different manufacturers… and then they have to integrate it into a common system,\u201d says Dmitry Kisil of West P&I.<\/p>\n
Not only that, but \u201cwhen we come together with a yard for a newbuild, there\u2019s always some new technology comes into the conversation, it\u2019s evolving all the time\u201d, says Jonas \u00c5kerman of W\u00e4rtsil\u00e4. Inevitably, this new tech demands another layer of software which may not sit that happily on the original architecture.<\/p>\n
\u201cIncidents can and do happen,\u201d says Kisil. \u201cI\u2019ve known propulsion control problems which have left the crew trying to reboot the system while underway – they couldn\u2019t find a way to regain manual control.\u201d<\/p>\n
Complexity poses a challenge. Commercial considerations mean a number of different, contributing suppliers, says Ludvigsen. \u201cFirstly, you want to verify how they sit upfront during development, and secondly, when you upgrade, you\u2019ll want to know they will continue to work together.\u201d<\/p>\n
That can be an issue. \u201cWhile you don\u2019t think twice if you have to renew a phone every two or three years or update the software every month,\u201d says Eero Lehtovaara of ABB, \u201ca ship\u2019s lifecycle of 30 to 40 years makes for very different considerations.\u201d<\/p>\n
As Kisil points out, \u201cit\u2019s just not possible to keep all the equipment and the software up to date\u201d, especially detached systems with little or no outside access. \u201cThese will sooner or later be running an older programme so integrated systems must run without requiring the latest installation. Moreover, he adds, \u201csoftware updates must not create any conflicts\u201d.<\/p>\n
Certainly, this stands to become more of an issue \u201cas you\u2019d always like to push out the best upgrades or versions, but you need to make sure it is fully validated\u201d, says Svein Kleven of OPS programme partner Kongsberg.<\/p>\n
But again, the problem has been that every time design details are exchanged there\u2019s potential for loss of confidentiality.<\/p>\n
\u201cA common platform was necessary,\u201d says Kleven. But it had to respect the individual players\u2019 IP, so the research team has worked out a way to make it happen. Essentially, it comes down to a \u201cblack box\u201d model of the system says Ludvigsen, which keeps the proprietary information inside, but still leaves the dynamic performance data available. So far, given this IP shielding, \u201cwe have found people seem really willing to share\u201d, she comments.<\/p>\n
Further, adds Kleven, when it comes to updates, \u201cit makes a step change\u201d far easier and safer.<\/p>\n","protected":false},"excerpt":{"rendered":"
The need to maintain commercial confidentiality has hampered efforts to develop more collaborative approaches to sharing data in simulation models. But technical advances could help onboard technology integration issues, writes Stevie Knight.<\/p>\n","protected":false},"author":8,"featured_media":617,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[],"sponsor":[],"class_list":["post-616","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-monitoring-control-digitalisation"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/posts\/616","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/comments?post=616"}],"version-history":[{"count":1,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/posts\/616\/revisions"}],"predecessor-version":[{"id":618,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/posts\/616\/revisions\/618"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/media\/617"}],"wp:attachment":[{"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/media?parent=616"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/categories?post=616"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/tags?post=616"},{"taxonomy":"sponsor","embeddable":true,"href":"https:\/\/www.motorship.com\/propulsion-and-future-fuels-conference\/wp-json\/wp\/v2\/sponsor?post=616"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}