Download - Royal Australian Navy

More documents

Recommendations

Info

36 NAVY ENGINEERING BULLETIN AUGUST 2002 Biographical Notes Commander WENDT joined the RAN as a Junior Recruit at HMAS LEEUWIN in July 1961 and after undertaking his initial engineering training at sea completed a Mechanician Fitter and Turner apprenticeship at HMAS NIRIMBA. He then returned to sea progressing through the ranks to Chief Petty Officer (Mechanician). Highlights of his non commissioned career were service in Veitnam waters onboard HMAS PERTH in 1970/71 and then during 1975 when he was responsible for the coordination of the hull and mechanical aspects of the half life refit / conversion of HMAS PERTH in the Long Beach Naval Shipyard in the USA. He was commissioned in 1977 and after undertaking engineering courses in the UK completed his Marine Engineer Officer training on HMAS STALWART and HMAS PERTH. Ross has subsequently been posted as the Marine Engineer Officer of HMAS PERTH, JERVIS BAY and TORRENS. His significant shore postings have been OIC of Darwin Naval Base and FIMA DARWIN, OIC of the Ordering Authority for Ship Repair in Western Australia, Platform Manager of Surface Ships at Naval Support Command and OIC of the Ship Repair Contract Office Eastern Australia Area. Ross discharged from the PNF on his 55th birthday with over 39 years service. He is currently a part time reserve officer filling the position of Fleet Environment and Occupational Health and Safety Officer at MHQ. The ultimate users of the EMPs will be personnel involved with the planning and conduct of activities in the maritime exercise areas. To that end the EMPs will be prepared in a format that: • is simple to use. • provides clear guidance on what activities may have adverse environmental outcomes. • identifies the risk of those adverse outcomes occurring, and the circumstances in which those risks may be increased or reduced. • details procedures to be employed to avoid, reduce or mitigate the risk of adverse outcomes. • advises any associated monitoring and / or reporting requirements. • is simple to revise or amend when legislative changes occur so that it remains a living and relevant document. Activities to be included in the EMPs for blanket clearance are as follows: • Gunnery, Missile & Torpedo firings. (Practice and Warshot) • Fixed and Rotary Winged Aircraft Gunnery & Missile shoots, Torpedo Drops & Bombing. • Supersonic & Low Level Flying and Combat Manoeuvring. • Use of KALKARA & TERRIER Aerial Target Vehicles. • Use of active sonar, sonarbuoys, underwater telephones, NIXIE’s, marine sound signals, smoke floats, submarine launched flares and other pyrotechnics, EMATTs, XBTs, SSXBTs, lasers, noise making decoys, NULKA, SRBOC etc. • HULKEXs and SMASHEXs. Minelaying and Mine Countermeasure exercises. • Demolition activities on the open sea. • Various seamanship activities including: Jackstay transfers, RASs, VERTREPs, full power and high speed manoeuvring and trials, OOW manoeuvres, Close ship steaming etc. • Amphibious Warfare activities. • Routine waste discharges (covering aspects such as types [bilge water, greywater, sewage, garbage] sources, typical quantities and discharge procedures) • Fuel and oil transfers. • RAN, DSTO, RAAF and Army trials of weapons, equipment and explosives. If you can identify any others please pass the information to CMDR Ross WENDT the Fleet Environment and OH&S Coordinating Officer (FEOHSCO) at MHQ on 02 9359 4397. ECC submissions are to be submitted to FEOHSCO on Form AB081 that is available on the DEFWEB or at http://pubsdb.cbrdps.defence.gov.au/wfs/ Further information on the EPBC Act can be found at the following web sights: www.ea.gov.au/epbc/assessappr ov/referals/significanceguide. html www.ea.gov.au/epbc/about/index .hmtl Further information on Environmental Management in Defence and the RAN can be found in the following; • DI (G) ADMIN 40-1 [DI (N) ADMIN 39-1] - Environment and Heritage Protection. • Fleet Generic Environmental Management Plan (GEMP) located in Defence Managers Toolbox. • ABR 6111 Parts 1 and 2 • AFTP 1 Chapter 30 The Maritime Command intends to be a leader in Sustainable Environmental Management. This however, will only be possible with the cooperation of all stakeholders and total compliance by all Fleet units with Environmental Legislative requirements and developed EMP's.
NAVY ENGINEERING BULLETIN AUGUST 2002 37 Defence Engineering & Maintenance Systems Scoping Study (DEMSSS) BY LTCOL ANDREW MONRO DIRECTORATE OF MATERIEL INFORMATION SYSTEMS PLANNING Introduction The move to align the many disparate systems into corporate information management (IM) solutions within Defence has been no coincidence. There are many drawbacks in having too many systems (across the individual Service domains) performing similar functions. These include the lack of a common language within Defence domains, high maintenance costs for information system support, increased training requirements with accompanying reduced flexibility of employment of personnel, and extreme difficulty/cost in providing information for management beyond the individual system level. Additionally, a large number of information systems create the need for an excessive number of interfaces between systems, which usually results in minimal numbers of automated interfaces and high levels of manual interfaces. These all contribute to degraded overall performance of Defence management functions. The former charter of the Joint Logistics Systems Agency (JLSA) to improve the efficiency and effectiveness of the logistics business processes and related information systems within the ADO has now been transferred within the DMO to Management Information Systems Division (MISD). This new Division was formed with the purpose of providing Defence with an information environment that supports Acquisition and Through Life Support. Amongst other things, MISD will support the Defence vision for logistics systems (as endorsed by the Defence Logistics Board), which is: Defence logistics will be supported by a well aligned suite of information systems that provides a high level of automated support for the day to day operation of people and processes involved in the conduct of, or in support of, military operations. The systems will be standard (for common functions) across Defence, but will cater for essential differences of functionality required by individual Services and circumstances. The systems will satisfy essential requirements and use standard Defence logistics language. Duplication of function and data will be minimised to that which is essential for effective military operations. The systems will readily accommodate enhancements. Access to the systems and data will be limited to those requiring it for legitimate Defence purposes. Where appropriate, they will be used by Defence contractors and coalition nations, and will inter-operate with their automated information systems. What does all of this have to do with engineering and maintenance (E&M), you ask? In the past, individual Services within Defence have acquired logistic systems to support their own technical equipment, generally without any formal requirement to consider possible multi-service application or the existence of systems in another service addressing similar requirements. Although there is more scrutiny in the present day, individual Service initiatives persist. This has resulted in a range of information systems supporting similar E&M functions across the Services, which potentially wastes Defence resources. It also makes decisionmaking from a corporate/Defence perspective very difficult because individual Service E&M data is difficult or impossible to aggregate. There are over 90 different E&M applications currently in use across the Services to support
Page 1: NAVY ENGINEERING ISSUE 3 AUGUST 200
Page 4 and 5: 2 NAVY ENGINEERING BULLETIN AUGUST
Page 88 and 89:
86 NAVY ENGINEERING BULLETIN AUGUST
show all

Download - Royal Australian Navy

Create successful ePaper yourself

Delete template?

Save as template?