Conference paper Open Access

Instead of Simply Asking 'What?', Naval Engineers Need to Ask 'Why?': Environmental Compliance Challenges and Relevance in Warship Design

Polglaze, J F


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">APASA: A Case Study of Hypothetical Oil Spills in the Southern Great Barrier Reef. Report prepared by AsiaPacific ASA Pty Ltd, Gold Coast, Australia, 2007.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">Fenske C.: "Transforming Grey Ships to Green: Emission Technologies for Naval Propulsion Systems", Proceedings of the Pacific 2012 Conference, Sydney, Australia, 30 January – 3 February 2012.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">James P. &amp; McKay J.: "Goal Based Regulation – The NATO Naval Ship Code", Proceedings of INEC 2014, Amsterdam, the Netherlands, 20 – 22 May 2014.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">Laird, A., Ledingham L. &amp; Goodship J.: "A Future Green Navy - Managing Environmental Expectation on Naval Ships", Proceedings of INEC 2016, Bristol, United Kingdom, 16 – 28 April 2016.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">Mansell J. &amp; Tsamenyi M.: "Sovereign and Crown Immunity for Warships? – Or Acting in a Manner Consistent With IMO Environmental Conventions", Proceedings of the Pacific 2012 Conference, Sydney, Australia, 30 January – 3 February 2012.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">MEM: "UK Shipping Industry Needs to Think Smart on Pollution", Marine Engineers Messenger, 26 April 2018.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">PGM Environment: Defence Seaworthiness Management System - Environment Protection: Analysis and User Guide. Report prepared by PGM Environment, Perth, Australia, 2015.</subfield>
  </datafield>
  <datafield tag="999" ind1="C" ind2="5">
    <subfield code="x">URS: Oil Spill Contingency Plan: Naval Waters - Fleet Base West 2002. Report prepared by URS Australia Pty Ltd, Perth, Australia, 2002.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">IMO/environmental compliance</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">environmental risks</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">operational capability</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">alternative means of compliance</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">technical risk</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">risk evaluation</subfield>
  </datafield>
  <controlfield tag="005">20200120171325.0</controlfield>
  <controlfield tag="001">2530676</controlfield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">2 – 4 October 2018</subfield>
    <subfield code="g">INEC</subfield>
    <subfield code="a">14th International Naval Engineering Conference &amp; Exhibition</subfield>
    <subfield code="c">Glasgow, UK</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">4666119</subfield>
    <subfield code="z">md5:80b8ffbd8dc949ef9a42095fd6c1fd53</subfield>
    <subfield code="u">https://zenodo.org/record/2530676/files/INEC 2018 Paper 088 Polglaze FINAL.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="y">Conference website</subfield>
    <subfield code="u">https://imarest.org/inec</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2018-10-04</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-imarest-inec</subfield>
    <subfield code="o">oai:zenodo.org:2530676</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">PGM Environment, Perth, Australia</subfield>
    <subfield code="a">Polglaze, J F</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Instead of Simply Asking 'What?', Naval Engineers Need to Ask 'Why?': Environmental Compliance Challenges and Relevance in Warship Design</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-imarest-inec</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution Non Commercial No Derivatives 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;Navies perceive benefit from proclaiming the intent to acquire &amp;lsquo;fully environmentally compliant&amp;rsquo; warships, but such statements indicate minimal understanding of what is entailed, or realisation of the emasculation of ships&amp;rsquo; operational effectiveness inherent to such ambition. Inescapable technical realities further void any possibility of achieving this aspiration in all but limited circumstances. Navies need to be smarter in objectively characterising and managing environmental risks, and innovative in generating bespoke technical solutions. Compliance with International Maritime Organization (IMO) marine environment protection obligations can be exceptionally onerous for warships, and in many cases nonsensical to pursue and arguably impossible to achieve. It is also ever more divergent from the standard caveat of &amp;lsquo;not impairing the operations or operational capabilities of such ships&amp;rsquo;. Extant, emergent and forecast regulations address matters such as fuel consumption, speed limits, fuel tank protection, and ship materials. Some requirements can be accommodated, offering benefits in terms of operational effectiveness and sustainment. Many, however, cannot be addressed without penalty in combat capability, survivability and through-life costs.&lt;/p&gt;

&lt;p&gt;IMO rules are founded upon merchant ship risks and linked merchant ship solutions; strict application of merchant ship risk remedies to warships can result in inappropriate design responses to ill-defined, inconsequential or non-existent risks. The design and acquisition processes of warships are also incompatible with IMO implementation schedules. Myopic application to warships of IMO prescripts can result in perverse outcomes which actually amplify risks to the environment.&lt;/p&gt;

&lt;p&gt;Novel ways in which to demonstrate effective compliance with the intent of rules need to be adopted. Sensible environment protection should remain a policy goal, but implementation should only be on an innovative, judicious, and risk-assessed basis if warships are to accentuate operational capabilities, which, axiomatically is the base reason for their existence.&lt;/p&gt;

&lt;p&gt;It is incumbent upon navies to also manage wider regulatory and policy dimensions. This can only be achieved by generating a clear understanding of what compliance entails in terms of capability and technical risks and how this may relate to a navy&amp;rsquo;s core mission &amp;mdash; to fight and win at sea. This must then be communicated as a cogent and reasoned argument to regulators and policy makers. This is so that commitments by navies to &amp;lsquo;environmentally compliant warships&amp;rsquo; are neither arbitrary nor to the detriment of capability.&amp;nbsp;&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.24868/issn.2515-818X.2018.063</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
</record>