Engineering - Royal Australian Navy

More documents

Recommendations

Info

Naval Engineering Bulletin • June 2001 CNE Introduction I remember when I was a Lieutenant at sea in the late 1970’s eagerly awaiting the next issue of the Fleet Maintenance Bulletin. It was full of interesting articles by engineers and technicians; some serious discussing issues facing engineering, some informative about new technologies that were to be introduced into Navy (like gas turbines!), and some for a bit of a laugh like someone proposing we could launch gliders by attaching them to 4.5" shells. The articles were graphically illustrated with cartoons and as a young engineer I was fascinated by the Bulletin as it gave me a window on the world of engineering in Navy. It was a forum for communication, information and discussion of issues. It was part of the Profession of Naval Engineering. The Fleet Maintenance Bulletin evolved into the Naval Engineering Bulletin in the late ‘80’s and then just disappeared a few years ago. With this issue we see the return of the Naval Engineering Bulletin. It will again be the forum for communication, information and discussion of engineering issues in Navy. It will be your window to our new world of engineering in Navy. As CNE, I am the professional head of Engineering in the RAN and Head of Corps for the Engineering Branch. I am responsible for providing CN with specialist advice on engineering, defining Navy’s engineering requirements and advising on engineering personnel matters. I am concerned that the contribution that engineering expertise and experience is making within the Navy has been declining for a number of years, and as a result the status of engineering in Navy needs significant improvement. My aim is to promote the contribution that sound engineering advice, professional judgement and the skills of engineers and technicians, both uniformed and civilian can make to Navy. During the last ten years the RAN has undergone significant organisation and procedural changes that have impacted on the delivery of engineering. Our current structure, training, administration and employment of engineering personnel may not now align well with the needs of a modern Navy operating smaller, minimum manned ships that commercially supported. The proposed new acquisitions outlined in the recent White Paper will also effect Navy’s requirement for engineering expertise. While engineering in Navy today is different to when I was a Lieutenant at sea in a DDG, it is just part of an evolution of engineering that has seen the change from sail to steam, from paddlewheels to screw propellers, from burning coal to burning liquid fuel, from large calibre guns to missiles, and the list goes on. These changes in technology have been accompanied by changes to manning, employment, skill requirements, training, logistic support and management. So be reassured, there is still a fundamental need for engineering in Navy, it is just different now, and we need to adapt to the changes. My objectives as CNE include: • Consulting widely and improving communication amongst engineering personnel by initiatives such as this Naval Engineering Bulletin, and engineering seminars; • Reviewing Navy’s requirement of its engineering personnel and how they may best contribute to Navy capability. This would include how engineering personnel should be organised and structured, and what education, training and experience they require. A high priority will be examining the employment of technical personnel ashore and the employment of junior engineering officers; • Examining what engineering and technical personnel require of Navy in such areas as job satisfaction, career progression, and personal development; • Refining the engineering processes within Navy; and • Being a key player in the new officer promotion system and in decisions impacting technical personnel. • Raising the profile of engineering in Navy. In summary, my objective is to reinvigorate Naval Engineering! So enjoy this first issue of the Naval Engineering Bulletin. To ensure it continues I encourage you all to contribute to it. 3
Naval Engineering Bulletin • June 2001 Finally, I would like to thank those people without whose efforts this Bulletin would still be just another good idea - CAPT Craig Kerr, LCDR Tom Munneke and MIDN Angela Andrews. Editorial Board Ken Joseph Commodore, RAN CNE 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 destroyer, 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 Officer 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 Officer 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 new, 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 Master 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 served with the Director Naval Engineering Requirements - Warfare Systems where he progressed policies on OT&E and Operational Software Engineering Management. In November 1993, he was posted as the Engineering and Support Director for the Offshore Patrol Combatant Project, where 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. Chairman Captain Craig G. Kerr, RAN Members Engineering Advisory Council (EAC) Editor Lieutenant Commander Tom Munneke, RAN Published by Defence Publishing Service Disclaimer The views expressed in this Bulletin are the personal views of the authors, and unless otherwise stated, do not in any way reflect Royal Australian Navy Policy Deadline December 2001 Edition 5 October 2001 Contributions should be sent to The Editor, Naval Engineering Bulletin CP4-7-138 Campbell Park ACT 2600 Telephone: (02) 6266 4212 Fax: (02) 6266 2388 or email: navalengineeringbulletin@cbr.defence.gov.au Distribution To be added to the distribution list contact the Editor. 4
Page 1 and 2: Volume 1 Issue 1 June 2001 NAVAL b
Page 3: Naval Engineering Bulletin • June
Page 7 and 8: Naval Engineering Bulletin • June
Page 55 and 56:
Naval Engineering Bulletin • June
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77:
show all

Engineering - Royal Australian Navy

Create successful ePaper yourself

Delete template?

Save as template?