Download - Royal Australian Navy
Download - Royal Australian Navy
Download - Royal Australian Navy
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
is the adf too stove-piped to effectively undertake expeditionary operations?<br />
149<br />
In accordance with current direction by the Chief of the Defence Force, each of the<br />
Service Chiefs is responsible for the RTS functions of their Service. The JOC Operational<br />
Preparedness Requirement (OPR) provides guidance to the Services as to the required<br />
quantity and skill level of forces; however, as the JOC OPR serials are not linked to<br />
resources, Service Chiefs have some flexibility in training requirements. 19 In this<br />
respect, the Service Chiefs decide what skills, tasks, and roles personnel from their<br />
Service will perform. The effect of this is that there is no incentive to conduct joint<br />
training or maintain joint skills. Service Chiefs are therefore able to focus on ‘The War’<br />
and not ‘A War’ as required by the JOC OPR.<br />
When examining the current forces elements deployed, the majority are single Service<br />
based. In Afghanistan the Mentoring and Reconstruction Task Force, Special Operations<br />
Task Group and Rotary Wing Group are all majority Army units. Most naval fleet assets<br />
deploy without personnel from other Services and AP‐3Cs and the Control and Reporting<br />
Centre when deployed to Afghanistan are essentially Air Force only units. Only HQ<br />
Hoint Task Force (JTF) 633, the Force Support Unit and Force Communications Unit are<br />
joint organisations. What makes this situation more obviously stove-pipe deployments<br />
is that these units, with the exception of the joint units, are assigned to separate<br />
NATO commands and do not generally support each other. Although HQ JTF633 is the<br />
National Command Element for all of these units, it has no tactical responsibility and<br />
provides only administration and reporting functions. This single Service deployment<br />
environment encourages the Services to continue with their single Service mentality<br />
and does not facilitate joint interoperability.<br />
There are a number of key drivers that show if a force has a joint orientation, including<br />
doctrine, equipment procurement process and personnel management. An examination<br />
of the doctrine process shows that the ADF has a disparate structure. Ideally, doctrine<br />
is designed top down; that is the capstone concepts are developed, followed by the<br />
generalised concepts then the specific concepts and finally the training, techniques<br />
and procedures. Yet an examination of the ADF doctrine process shows that the three<br />
Services develop doctrine independently. As mentioned earlier, the ADF doctrine<br />
organisation, ADFWC is now non-existent and its replacement, JWDTC ineffectively<br />
manned and tasked to control this process; the result is that the Services control<br />
doctrine and joint interoperability is not the guiding principle. So if this is the case<br />
for doctrine what about the other elements?<br />
In the resource constrained environment that the ADF currently finds itself in, the<br />
three Services are competing against each other for finite resources to maintain current<br />
equipment and purchase new equipment. There are two possible solutions, compromise<br />
with the other Services and agree to reducing one’s own capability, or ‘fight the fight’ and<br />
risk being told what to lose. 20 A look at 2009 Defence White Paper and current equipment<br />
acquisition projects demonstrates that fights had been fought and won. 21 Although there<br />
have been some minor compromises and loses, and the fact that the majority of major