ENGINE - Royal Australian Navy

More documents

Recommendations

Info

BY DAN CU RTlS, M PLG SECRETARY MARITIME PLATFORM LIAISON GROUP As the Navy Technical Regulator, Head of Navy Engineering, CORE Bryson, is responsible for the Technical Integrity of all ADF Maritime Materiel assets. This encompasses fitness-for-service, safety and environmental compliance of these assets from design and construction, through life to disposal. To ensure Technical Integrity of the fleet is maintained, Naval Engineering Division, under the direction of HNE, has developed a suite of documents called the Maritime Materiel Requirement Set (MRS). The vast majority of these documents are now written. It is an appropriate time to look at how they are being used and how they could be improved Improving Navy Technical Requirements Some of the MRS documents are very mature and tend to be used with little discussion or variation. Others have developed recently and are stil l developing as they are being used. It is important to note here that the MRS documents represent what is considered to be an acceptable level of risk. In the provision of systems. hardware and so on against these requirements it is not always necessary to exactly meet these requirements, it is however necessary to carefully measure and assess the risk against the MRS requirements. While it is vital to ensure the MRS documents effectively capture Technical Integrity requirements, it is important that they promote innovation and are also able to be achieved by current technology. Stakeholders who work with the MRS, such as DMO and industry, need to have the opportunity to provide input to the MRS for improvement. To achieve this aim HNE has stood up the Maritime Platform Liaison Group. Formation of Maritime Platform Liaison Group The MPLG, made up of representatives from Navy, Defence and industry, is open to anyone who feels they might be able to contribute usefully to the work program. The MPLG enables the Maritime Platform engineering community (from Defence , industry and other parts of government) the opportunity to discuss engineering issues that affect multiple platforms, Maritime Materiel Requirements, delivery against technical requirements and incorporation of new technology into ADF Maritime Materiel and the Maritime Materiel Requirements Set (MRS). It is worthy of note that the MPLG is limited in scope of Naval Architecture, Mechanical and Electrical Engin eerin g elemen ts of ADF Maritime Platforms. It specifically does not address issue covered by the Maritime Survivability Working Group. MPLG Objectives The specific objectives of the MPLG are: • Development of the MRS to ensu re it adequately captures ADF Maritime Requirements; • Provide feedback and advice on implementation of existing MRS documents including suggestions for improvement; • Techn ical information exchange within Australia; • Identify areas where additional MRS coverage is required; and • Identify areas for cooperation and information exchange unde r existing international agreements. MPLG Organisation The MPLG has essentially two levels of organisation. The fi rst is the Advisory Group and the second are the Expert Teams (ET) . The Advisory Group is cha ired by HNE and consists mostly of individuals at the CAPT or EL2 eq uiva lent level and they provide oversight and gu idan ce for the work of the ET and advise the HNE on what should be done with outcomes of the ET efforts. The Advisory Group meets every 6 months. The Expert Teams are formed to investigate particular issues and have definite timeframes and deliverables required of them. They have a particular work program and are led by the relevant Technology Manager from the Directorate of Navy Platform Systems (DNPS). The work of the ET is done online, using a website hosted by DNPS. This allows easy access and promotes active discussion. The members of ET come from organisations with an interest in and an abi lity
to contribute to the work of the particular ET. Progress to date The MPLG website has gone 'live' on 25 Aug 09 and work on the initial set of ET Work Packages has commenced . The initial technical ET's are: • Carriage of Low Flash Point Fuels - The RAN sometimes carries petrol and other low flash point fuels. Lowflash point fuels, so called because of their ability to ignite at relatively low (ambient) temperatures are inherently dangerous cargo and commercially are covered by the International Maritime Dangerous Goods (IMDG) Code; however some of the activities conducted onboard Navy ships are not covered by the IMDG Code. • High Voltage Onboard Ship - Use of high voltages (1000 Volts and above) at sea is a rapidly maturing commercial technology. It is however new to the RAN, so it is important that all aspects of using high voltages at sea are explored and understood before ships with high voltage systems enter service. • Platform Automation Automation of ship systems has been progressing for some time onboard navy and commercial ships around the world . While limited implementation of platform automation can be achieved and understood relatively easily, the implications of high levels of platform automation are not so obvious and this is being explored and clarified. • Surface Ship Stability Deliverables - While the basic principles of ship stability are well understood by all naval architects, Navy-specific requirements for ship stability are not, at least within some sectors of industry. This ET is investigating this problem to assess how the situation might be improved, particularly with respect to stability reports, inclining experiment reports and trim and stability books. • Surface Ship Structure Assurance - Navy has been working for some time to put elements of the fleet into Class, using a variety of Classification Societies. It is important that Navy understand 'classification' and the Classification Societies role. The process of gaining deeper understanding has begun by investigating ship structures and how Navy can be assured of structural fitness for service. How do I get Involved? HNE is looking for interested people from Navy, Defence and industry who have expertise and experience to bring to these investigations and who are willing to share that with the Navy to develop better technical requirements. For further information regarding the MPLG, it's work and how to become involved, please contact the MPLG Advisory Group Secretary, Mr Dan Curtis, on 02 6266 2303 or dan .curtis@ defence.gov.au.
Page 1:
ENGINE ISSUE 16 OCTOBER 2009 NAVY
Page 4 and 5:
BY CDRE JOHN BRYSON INTRODUCTION BY
Page 6 and 7: BY LEUT CALDERAZZO FROM THE EDITOR'
Page 8 and 9: BY CMDR GREG SWINDEN REAR ADMIRAL P
Page 10 and 11: BY CMDR GLENN GREEN WHAT, ME AN ENG
Page 12 and 13: BY CMDR KATH RICHARDS AND CMDR DAVE
Page 14 and 15: 6 Future Environmental Policy Trend
Page 16 and 17: work is funda mentally about how be
Page 18: BY SBlT JOHNSON HOW DO WE KNOW THAT
Page 22 and 23: asins) and is 3200ft long'. The dee
Page 24 and 25: covered in earlier In modules but i
Page 26 and 27: Step 4 - Attend study groups Implem
Page 28: WHEN SHOULD A RADHAZ SURVEY BE COND
Page 31 and 32: the standards expected of them. Acc
Page 36: CPO "HERBY"TANNOCK DISCUSSES DAMAGE
Page 40 and 41: of this internal cooling has not ye
Page 43 and 44: How does the Register work? • Red
Page 46 and 47: BY MR JOHN COLQUHOUN THE SHIP/HELIC
Page 49 and 50: RSO GSO RGURE 4: SHIP HElICOPTER WI
Page 51 and 52: Authority. This creates a somewhat
Page 54 and 55: invokes a number of short courses i
Page 59: OF301E MSC 1 CAUTIAOV PNl V/UHF OF
Page 63 and 64: poor Austra lians and Kiwis trapped
Page 65 and 66: BY LSMT CAMERON WILLIAMS MTUDDAIOP
Page 67 and 68: Course Name Advanced Project Manage
Page 70: Organisational Resilience .........
show all

ENGINE - Royal Australian Navy

Create successful ePaper yourself

Delete template?

Save as template?