ENGINEERING - Royal Australian Navy

More documents

Recommendations

Info

N AVY E N G I N E E R I N G B U LL E TI N F EB R U A RY 2 0 02 3 CNE Introduction In our last issue of the Bulletin, I expressed my concern that the contribution that engineering expertise and experience is making within Navy has been declining for a number of years, and as a result the status of engineering in Navy needs significant improvement. Since being appointed Chief Naval Engineer (CNE), I have sought to determine the issues facing Navy Engineering. BY COMMODORE KENNETH W. JOSEPH I have held discussions with many engineer offi c e rs, sailors and Navy civilian engineers , i n te rv i ewed many junior offi c e rs , p a rt i c u l a rly those consideri n g resignation, and had discussions w i th CN, the Mari t i m e Commander and with Indust ry. I have addressed cours e s including WEAC / M E AC, ATT and I T T, and have visited FIMA East , We st and Darwin. The Engineeri n g fo rum and wo rkshop held in D a rwin in July 2001 exa m i n e d p roblems curre n t ly facing Nav y E n g i n e e ring. Consequ e n t ly, I feel I h ave a good understanding of th e m a ny issues facing Nav y E n g i n e e ring and now the time has come to ta ckle th e m . In my introductory remar ks to the first issue of the N aval Engineering Bulletin I outlined my responsibilities and objectives as CNE. One of my objectives was to refine the engineering processes within Navy, so I have initiated Project HELP – Healthy Engineering & Logistics Policy to correct deficiencies in engineering and logistics policy, and refine and document the processes. The Engineering aspect has commenced and the first phase, now complete, was to define the role of CNE. This position has been defined as the Head of the Corps for Navy engineers and technicians both uniform and civilian, and as the Navy Technical Regulatory Authority. Further details of Project HELP are explained in an article in this Bulletin. Another of my objectives was t o review Navy’s requirement of its engineering personnel and how they may best contribute to Navy’s capability. During the last few years Navy has undergone significant organisational and procedural changes that have impacted on the delivery of Navy Engineering. When combined with changes in technology and the engineering profession, Navy Engineering may now not meet the needs of our Navy operating more complex, minimum manned ships in a commercial support environment. I am also aware that these changes are having an adverse impact on the morale of Navy’s engineering personnel in part because their role and the vision for their future is not clear. The Darwin Engineering Seminar highlighted the need to document how engineers contribute to the Navy mission. So with CN’s approval, I have initiated another project to examine how Navy Engineering will evolve to meet this challenge. The project is being undertaken in two stages. The first stage will develop an issues paper that presents options for the way ahead. The second stage will use the agreed outcomes of the first stage to develop a public document – Navy Engineering Doctrine. This document will describe the future role, capability and requirements of Just remember, particularly in this time of increased operational tempo, that every day – engineers make it happen! Navy Engineering, to better utilise our engineering assets and for engineering personnel to understand how they contribute to Navy’s mission. The project is being undertaken by Commander Mathew Hudson RANR and Mr Athol Yates. Further details are found later in this Bulletin. I know that many of you are most concerned at the loss of the engineering Two Star and now the lack of engineering representation on CNSAC. While I will continue to lobby for both of these, it should be noted that engineering is not self serving – it is an integral part of supporting the Navy Mission. So it is important that your CNSAC representative is well briefed on the engineering aspects of the agenda items for each meeting. Shortly after the first issue of the Navy Engineering Bulletin hit the
4 N A VY EN G I N E E R I N G B UL L ET IN F E B RU A RY 20 0 2 BELOW JUST REMEMBER – ENGINEERS MAKE IT HAPPEN sea lanes, I received a phone call from the Commanding Officer of one of our major sur face combatants saying how much he enjoyed reading it. The feedback from the engineering community has been equally positive. I was most impressed at the standard of the articles and I thank the contributors for their ef forts without which we wouldn’t have a Bulletin. To encourage the submission of articles, prizes are awarded for the best ones. My congratulations go out to Mr Peter Clark, LCDR Mark Warren and CPO Vic Young who won prizes for their contributions to the first edition. I would also like to thank LCDR Ray Cairney for editing this issue between postings. You will observe a number of changes in this issue to align it with Brand Navy, including the name of the Bulletin and its ‘look and feel’. In conclusion, the reinvigoration of Navy Engineering has commenced and I ask for your support to HELP and the Navy Engineering Doctrine. Just remember, particularly in this time of increased operational tempo, that every day – Engineers make it happen! About the author Commodore Kenneth W. Joseph was born 16 April 1954 in Sydney. He joined the Royal Australian Naval College in 1971. He then attended the University of New South Wales in 1973, graduating in 1976 with a Bachelor of Electrical Engineering Degree. This was followed by engineering courses with the Royal Navy and with the United States Navy in 1977/78. He served in the destr oyer, HMAS PERTH from 1978–80,where he managed the ASW and Gunnery systems. As a young Lieutenant in 1981/82 he served on the staff of the Director Naval Weapons Design, primarily concerned with the design and manufacture of the Australian indigenous sonar known as “MULLOKA “. From 1982–85 he served as the Resident Naval Engineer at the sonar manufacturer’s plant. In 1985 he returned to sea as the Weapons Electrical Engineering Of ficer of HMAS PERTH which won awards for Gunnery and Missile system excellence and the effectiveness of ASW,AIO and Communications systems. In 1987 he was posted ashore as the Of ficer in Charge of the Trials Unit at the Royal Australian Navy Trials and Assessing Unit. His responsibilities included the trials and acceptance recommendations of all ne w, modified or overhauled ships, aircraft and other operational systems. In 1991, he was posted to the Naval Postgraduate School in Monterey, California to pursue a Mas ter of Science degree in Management. His thesis addressed Operational Test and Evaluation (OT&E), and he graduated With Distinction in 1992. On returning to Australia in February 1993 he ser ved with the Director Naval Engineering Requirements – War fare Systems where he progressed policies on OT&E and Operational Softwar e Engineering Management. In November 1993, he was posted as the Engineering and Support Director for the Offshore Patrol Combatant Project, wher e he was responsible for the management of the ship design and proposed Integrated Logistic Support during the Project Design Phase. In February 1995, he was promoted to Captain and appointed as the Director Capability Development and Analysis in Force Development (Sea). The appointment as the Minehunter Coastal Project Director followed in December 1996 where he achieved the successful delivery of the first two ships. He was promoted to Commodore in December 1999 and posted as the inaugural Director General Naval Systems in March 2000. He was appointed as the Chief Naval Engineer in September 2000.
Page 1 and 2: NAVY ENGINEERING ISSUE 2 FEBRUARY 2
Page 3: 2 N A VY EN G I N E E R I N G B U L
Page 7 and 8: 6 N A VY E N G I N E E R I N G B UL
Page 9 and 10: 8 N A VY EN G I N E E R I N G B UL
Page 11 and 12: 1 0 N A VY EN G I N E E R I N G B U
Page 13 and 14: 1 2 N AVY E N G I N E E R I N G B U
Page 17 and 18: 1 6 N AVY E N G I N E E R I N G B U
Page 19 and 20: 1 8 N AV Y E N G I N E E R I N G B
Page 21 and 22: 2 0 N A VY E N G I N E E R I N G B
Page 25 and 26: 2 4 N AV Y EN G I N E E R I N G B U
Page 55 and 56:
5 4 N A VY EN G I N E E R I N G B U
Page 57 and 58:
5 6 N A VY EN G I N E E R I N G B U
Page 59 and 60:
5 8 N AVY E N G I N E E R I N G B U
Page 61 and 62:
6 0 N A VY E N G I N E E R I N G B
Page 63 and 64:
6 2 N AVY E N G I N E E R I N G B U
Page 65:
6 4 N A VY E N G I N E E R I N G B
show all

ENGINEERING - Royal Australian Navy

Create successful ePaper yourself

Delete template?

Save as template?