Tag Archive for: Department of Defence

More cookie cutters please: cyber policy in the 2016 DWP

While the PM has heralded the 2016 Defence White Paper as visionary, its treatment of cyber policy is stuck in first gear. As noted by Tobias Feakin last week, DWP 2016 has provided more money and manpower for Australia’s cybersecurity efforts, but lacks a sophisticated policy position on cybersecurity posture, capability and resilience.

The DWP establishes two broad roles for Defence regarding cybersecurity. The first is to protect its own networks, and the second is to contribute to the broader whole of government cybersecurity effort, principally through the multi-agency Australian Cyber Security Centre (ACSC). The DWP proposes to achieve those two goals through investment in a larger workforce, enhanced cybersecurity capability, increased training and R&D. However this policy almost a carbon copy of the positions put forward in 2009 and again in 2013.

Casting back to the 2000 White Paper (yes, cyberspace existed back then), the central notions of Defence’s cyber policy were being formed. The 2000 White Paper noted that ‘information technology is transforming the way that armed forces operate’ and included ‘ensuring these systems are managed effectively, (and) secure against information warfare attack’ as a capability goal. By 2009, the White Paper noted that ‘the potential impacts of such (cyber) attacks have grown with Defence’s increasing reliance on networked operations’. In 2013, it was reworded to say ‘The potential impact of malicious cyber activity has grown with Defence’s increasing reliance on networked operations’. In 2016, that assessment remains: ‘Cyber attacks are a direct threat to the ADF’s warfighting ability given its reliance on information networks’.

Successive White Papers have also used similar language to reference Defence’s contribution to whole of government cyber security efforts. In 2009, the establishment of the Cyber Security Operations Centre was announced, with the caveat that ‘While this capability will reside within Defence…it will be purpose designed to serve broader national security goals’. In 2013, the creation of the ACSC, where Defence would play the ‘principal’ role, was highlighted as a major element of Defence’s cybersecurity posture. In 2016, Defence will continue to contribute to ‘the Government’s enhanced national cyber security efforts’—an area in which it makes a ‘critical contribution to (Australia’s) whole of government cyber security efforts’.

DWP 2016’s language on the treatment of cyber threats focuses on Defence and the Government’s work to ‘enhance’ and/or ‘strengthen’ cyber security capability. The DWP says that ‘The Government will strengthen Defence’s cyber capabilities to protect itself’. In 2013, Defence planned to ‘invest in technology and analytical capability to ensure our situational awareness and response capability remains ahead of the threat’. In 2009, the White Paper also stated that ‘The Government has decided to invest in a major enhancement of Defence’s cyber warfare capacity’.

A big part of the enhancement to Defence’s cyber capability is supposed to come from ‘increasing’ the R&D focus from the Defence Science and Technology Group (DTSG). In 2016, ‘Government will establish a research and development capability to help strengthen the defences of the ADF’s military information systems against attack’. DSTG’s Cyber and Electronic Warfare Division may be surprised to hear about this new cyber R&D capability since they have been responsible for Defence’s cyber related R&D work  for a number of  years now. In 2009, the thenDSTO planned to ‘increase its investigation and application of key enabling technologies…such as cyber warfare and computer security’. In 2013 also, DSTO was going to ‘bolster’ its cyber research in line with the 2013 National Security Strategy.

DWP 2016 has omitted the statement from 2013 on Australia’s position on international law and norms regarding cyberspace. That’s an important piece of the broader cyberspace conflict prevention and confidence building agenda in which Australia plays a leading role in our region. This agenda was important enough for the PM to mention in Washington, and its omission is surely a missed opportunity to promote it in Defence’s principal statement of policy.

Also missing is a strong concept of cyber resilience. Resilience is frequently mentioned in the DWP, but unfortunately, it’s only used once in the DWP in connection to cybersecurity. This is despite the concept of resilience’s emerging centrality to advanced cyber policy positions, such as the US Department of Defense’s Cyber Strategy. The DWP significantly fails to mention that a resilient military not only has the capability to protect itself in cyberspace, but also must be ready to operate effectively in a contested environment where access to cyberspace isn’t possible or trusted. The ability to operate without access to critical command and control networks now and in the future will mark the difference between advanced and less capable militaries and states. That’s a significant oversight, and a further marker of the lack of sophisticated thinking in DWP 2016 on cybersecurity policy.

DWP 2016: a throwback to a harder era

The 2016 defence white paper is a first-class statement on Australia’s strategic situation. It proffers a balanced view of the significance of Australia’s alliances and ably inserts their defence in the context of broader regional and global politics.

A force structure emerges that’s affordable and well pitched to an understanding of the need for an Australian technological edge in a strategic zone to the north of Australia—an area which is witnessing a surge in military capability (and capacity for force projection) at a faster rate than anywhere else. DWP 2016 contains an industry policy which slams into reverse a 20-year drift towards off-the-shelf equipment acquisition. Nowhere is the term ‘self-reliance’ used, but we have a defence industry policy that adopts the rationale and content of the industry section of the 1987 white paper. The rationale then was self-reliance; optimising the ability to build and sustain as many of our platforms as possible. One has a sneaking suspicion we owe this excellent revival to the voters of South Australia.

As a defence statement it has some flaws, which are best encapsulated in paragraphs 3.10 and 3.11. Paragraph 3.10 says:

To ensure Defence has the necessary force structure and force posture to defend and further Australia’s Strategic Defence Interests, the Government has agreed to three equally-weighted high-level Strategic Defence Objectives to guide the development of the future force set out in this White Paper. The Strategic Defence Objectives outline the activities the Government expects Defence to be able to conduct if the Government decides to use military power in support of Australia’s Strategic Defence Interests.

Paragraph 3.11 defines the strategic defence objectives:

  • Deter, deny and defeat attacks on or threats to Australia and its national interests, and northern approaches.
  • Make effective military contributions to support the security of maritime South East Asia and support the governments of Papua New Guinea, Timor-Leste and of Pacific Island Countries to build and strengthen their security.
  • Contribute military capabilities to coalition operations that support Australia’s interests in a rules-based global order.

All three are indeed important defence objectives and have been pursued on a bipartisan basis by Australian governments since before the Cold War ended. But they’ve not been pursued as coequal determinants of the force structure. That’s because if the government were to do so it would be impossible to prioritise a tight budget. Just about any item of expensive kit could be justified under one of them.

Hitherto the first of the objectives, pursued in the context of an area previously defined as of ‘direct military interest’ to Australia, has been the dominant influence. Forces required for the further objectives have been identified as being drawn from a structure pitched to the first.

There’s no discussion of military strategy in DWP 2016. With a focus on the first strategic objective, this strategy would be defence in depth or layered defence. There’s no detailed assessment of most likely threats and concepts of warning time. There’s no clear differentiation in development of capability on what belongs in the ‘force in being’ and what is placed as part of an ‘expansion base’ activated in a shift to a high-threat environment.

Pursuing such detailed analysis of course becomes highly contentious. It’s possible some of it is canvassed in the classified version and in scenario-based planning in the department. Past papers have seen fit to canvass these issues in public. It’s possible that exercising this discipline might be seen by the government to be a throwback to an unacceptable past. What had then been a longstanding preference for a force structure based on expeditionary activities was replaced by a determination, in the first instance, to defend Australia’s approaches. If the spending in the 2016 white paper gets into trouble down the track, the best defence will be found in planning for an uncertain region.

DWP 2016 is saved by a number of factors. It offers a sophisticated enunciation of the multitude of problems Australia confronts globally. It takes a welcome step in prioritising the shifting threat environment into new spheres of cyber and space. It positions us well on the areas of force structure and industry policy for Australia–US collaboration on the technologies entailed in Washington’s so-called third offset strategy. Broadly, the 2016 document is strong on allied collaboration.

Above all, the actual force structure which emerges, particularly big-ticket items for the RAAF, together with submarines and with facilities in the north, conforms to the first strategic defence objective. It ends up in major ways being the defence of Australia document you get when you dare not speak its name. The return to a self-reliant industry policy is at the heart of this. The arguments on sustainment, innovation and enhanced workforce skills are all a throwback to a harder era and are very welcome.

Funding defence and squaring the circle

On Tuesday, the Defence Minister re-committed to releasing a White Paper in the first quarter of this year. That means it’ll be fewer than 51 sleeps before we see the document. More importantly, it means that the White Paper will be sent to the printer before the 2016 federal budget is locked down.

In times past, the resulting sequence of events wouldn’t be a problem. But the forthcoming White Paper comes with big expectations inherited from the Abbott government; specifically, the promises of a costed affordable plan and for defence spending to reach 2% of GDP within a decade. Committing to specific spending levels, let alone a timetable to reach 2% of GDP, is easier said than done with the overall budget still a work in progress.

And it’s not like Turnbull government is in honeymoon mode. The May budget will be the last opportunity for Scott Morrison to establish the government’s economic credibility prior to the election, and the political trainwreck following Joe Hockey’s 2014 budget shows how much is at stake. 

To complicate matters further, the economic and fiscal situation has moved into uncharted waters—not just for Australia but also internationally. Consider the graph above of successive estimates of global growth made by the International Monetary Fund from 2010 onwards. In each and every year, growth has fallen well a below expectation (which means that 2% of GDP ain’t what it used to be). Economists are flummoxed to explain the persistent stagnation. Central bankers continue to search for ways to promote growth with interest rates close to zero and, in some cases, negative. Faith in unconventional monetary policies such as ‘quantitative easing’ is evaporating. Commodity prices have collapsed and equity markets are worryingly volatile.

As a commodity exporting nation with a high dependence on company tax to balance the books, the government’s fiscal situation continues to deteriorate. Wayne Swan said we would be in surplus by 2012–13. Joe Hocky started out with a goal of 2015–16. In December, Scott Morrison pushed out the expected return to surplus to around 2020. But even that dismal projection presumes, somewhat optimistically, that measures currently stalled in the Senate will be passed. Worse still, it’s predicated on continuing unmitigated bracket creep.

Meanwhile, as deficits pile up, so too does Australia’s net debt. While net debt is only projected to grow to around 18% of GDP—a mere third of a trillion dollars—towards the end of the current decade, there’s no reason for complacency (as Treasury Secretary, John Fraser, made clear in a recent speech). Australia’s ability to manage economic risks depends upon maintaining a good credit rating so we can borrow money at favourable rates. Mounting debt works in opposition to this.

Readers of The Strategist don’t need to be reminded that the strategic environment is no more favourable than the economic. These are challenging times, wherever you look. How then will the Turnbull government balance its investments to mitigate economic verses strategic risks? Make no mistake; it’s a zero-sum game. Ignore the snake oil about defence innovation and spinoffs: every dollar spent on defence is a dollar that can’t be used to retire debt.

In the short to medium term, I suspect that the government has limited flexibility about defence spending. In contrast to the lead up to previous White Papers, acquisition approvals have continued apace over the past two years. In theory, some of the unnecessarily rushed shipbuilding activity planned for later this decade could be slowed down, but that would come at a political cost from the frenzied state of entitlement that calls itself South Australia.

Thus, the good news for Defence is that the forthcoming White Paper is likely to confirm extant expectations about the ongoing modernisation and expansion of the defence force. Just as importantly, they will likely provide adequate funding for the task at least until the end of the decade (unless we see a repeat of the regrettable period 2009 to 2013 when Defence was asked to square the circle of ambitious plans and parsimonious budgets).

One thing the government could do is jettison the 2% of GDP target. Setting aside the myriad of technical reasons why a GDP target is dumb (see here and Chapter 3 here), doing so would provide some flexibility in the years ahead to calibrate defence spending in light of evolving strategic and economic imperatives. In the good times of the resource boom, we could afford Defence’s planners the luxury of long-term funding certainty (and they returned the favour by handing money back unspent). Those days are over. Australia’s overall best interests are today served by a government that’s agile and adaptive in its allocation of resources.

The ANAO’s grim picture of Defence testing & evaluation

NUSHIP Adelaide is manoeuvred towards her berth at Fleet base East - Garden Island while her sister ship, HMAS Canberra, can be seen near the entrance into the Captain Cook Graving Dock.

The Australian National Audit Office (ANAO) has just released a report into Defence Test and Evaluation (T&E) that makes a number of important findings. According to the report, this critical enabler to informed decisionmaking in Defence capability development and acquisition is spread across too many smaller T&E organisations and doesn’t have adequate oversight of the competency of all of those staff managing the T&E. The paper also finds that Defence only recently has a centralised T&E policy that needs much more refinement and governance. Lastly, on the recent T&E of the Landing Helicopter Dock (LHD) ship, Defence was unable to deliver a sufficient number of competent T&E staff to process the test reports and concessions in a timely fashion.

Defence uses T&E to have representative users assess if capabilities deliver effective results when used in representative missions. T&E is Defence’s main measure of capability that goes with cost and schedule to determine if a project is reducing risk and thus succeeding. Good T&E gets done as early as possible; ideally T&E gets done as a real preview before full contract (off-the-shelf systems) and certainly should be done before production is contracted.

ANAO last audited Defence’s T&E in 2001–2002. In the 13 years since, they’ve unfortunately found that there has been little or only late progress on most of their areas of concern. That’s despite the concerns being reiterated in a Defence T&E Roadmap in 2008 and in the Senate Inquiry into Defence Procurement (especially Chapters 2 and 12) in 2012. In this same period US Defense has entrenched independent T&E into Congressional laws (Title 10) that provide mandatory independent annual reporting of all T&E measures to Congress on all major Defense acquisitions. Title 10 law also requires T&E competency in all US acquisition projects and T&E agencies overseen by the autonomous Defense Acquisition University. The book and movie The Pentagon Wars has clearly raised awareness in the US for the value of independent T&E for Defense acquisitions much more than in Australia. There’s a clear option for the Australian government to follow America’s lead with Defence Regulations if Defence doesn’t institute strong, independent, early and adequate T&E for its critical capability decisions.

Most strikingly, the ANAO report’s insights to the project management of the new LHD ships illustrate that Defence didn’t have the necessary T&E staff to manage the contractor’s reports in a timely manner and that this necessitated the transfer of some capability risk to Navy. The project positions for the T&E were planned but not filled, and the project manager repeatedly advised project governance boards of the vacancies. But it appears that the now defunct Defence Materiel Organisation was unable or unwilling to appropriately prioritise what ultimately became a Navy problem. These difficulties reinforce the ANAO’s previous findings that Defence isn’t managing its T&E competency in all areas. That this observation occurred in the maritime domain should be of critical concern given the significant investment in ships and submarines anticipated in the new Defence Capability Plan, most of which require significant development, integration, test, build and more test in Australia.

What isn’t directly mentioned in the ANAO report—but concerns me as a former leader in this area—is that of the 12 Defence organisations dedicated to T&E, not one of them does developmental test of ships or submarines: the Navy only has a dedicated operational T&E agency. Each maritime project has to find the T&E expertise and resources itself. In contrast, the Air Force has a dedicated developmental T&E agency. The Army also has one but theirs was in the now defunct DMO and it’s not clear yet if they’ll take this critical enabler back to the service for early insight into project T&E. The implications of this maritime approach are plain to see in the ANAO coverage of the LHD ship T&E. This approach also places significant risk on the adequacy of preview testing for the submarine project options and is at odds with the long-term decision by this government to invest in continuous build of ships.

The ANAO report and the government’s response today in Parliament point to the First Principles Review and subsequent Defence reorganisation as the means to improve Defence T&E. Little is known of the new structures of this reorganisation other than it aims to reduce acquisition bureaucracy and create a strong strategic centre. If the strategic centre is to be better informed for its acquisition decisionmaking it needs to clearly invest in more structured, resourced and competent T&E. A more complete coverage of what such a first principles reorganisation should consider is in my paper titled ‘Implementing the Defence First Principles Review: two key opportunities to achieve best practice in capability development’.

Update: Click here to view Keith Joiner’s Strategic Insights paper, published 17 December 2015.

The future submarine and naval shipbuilding in Australia

The Government has a clear strategy for achieving a productive, cost-competitive and sustainable naval shipbuilding industry.

We also know that Australia cannot afford a naval shipbuilding industry at any price. A reshaping and reform of the naval shipbuilding industry will be needed if we are to deliver the future Navy we need, at a price we can afford.

If we are to ensure that the ADF is a balanced force, with the highest levels of capability and protection we can afford, we must deliver capability that is value for money and internationally cost-competitive.

Substantial reform of the industry will be necessary and hard decisions will need to be made. The Government is willing to make that commitment. We will require industry to do the same.

We expect industry to work with us to reform the naval shipbuilding sector. We expect industry to make the necessary investments, provide the necessary skill base and build innovative new construction practices to deliver highly capable, cost-competitive naval vessels.

At the heart of this will be a commitment from industry for a productivity-based culture, which includes management, the Unions, the workers, with supportive government.

Industry will need to build complex project management skills in senior management and across the workforce. It will need to build experience in its workforce and sub-contractors, it will need to be focused on quality management and delivering the right product at the right price on time the first time.

As you’ll also be aware, submissions for the Competitive Evaluation Process to find an international partner for the Future Submarine Program are due to be received at the end of this month.

The Government understands the great significance of the decision-making process that will occur once these submissions are received and of the decision itself for Australia’s future.

We are determined to get the best capability and the best value for money through the Competitive Evaluation process for the Future Submarine.

There have been some criticisms of the Competitive Evaluation Process that have suggested that the timeframe for the process is not adequate to fully analyse the substantial range of issues that must be considered in proceeding with the submarine’s development.

I would note that all three participants, DCNS of France, TKMS of Germany and the Government of Japan have stated that they are satisfied with the timeframes that we have given them for the Competitive Evaluation Process. Some may say ‘of course they’d say that’ —perhaps they would—but we know that all three participants have invested in developing their responses to meet the schedule and that all three have done everything they can to demonstrate their suitability to be our partner.

When it comes to considering the proposals and making the decision, let me assure you that the Government does not intend to be rushed. This is too important a decision for that. We will take the time required to consider all options and to allow a comprehensive assessment against all of the Government’s criteria to be made.

There is a risk in moving too quickly, clearly, but there is also risk and potential cost, in adding more time to this process.

The Government has considered all the risks inherent in the development activities, and taken the best possible advice from the Department of Defence, and we have chosen this process as the most appropriate means to manage those risks given the nature of the process and the need for this critical capability.

This process provides a way for Australian industry to have the greatest possible involvement in the program, without any compromised cost, capability, schedule or risk.

In addition, the Expert Advisory Panel appointed by Government continues to oversee the conduct of the Competitive Evaluation Process to ensure the fairness and equity of that process.

The aim of the CEP is to inform Government’s decision on the international partner to work with Australia to develop and deliver the Future Submarine.

We have sought and are expecting proposals from all three participants to include proposals for onshore, offshore, and hybrid build options.

Through this process we will assess the ability of participants to work closely with us, including how each would approach our capability and sustainment needs, and how cost and schedule would be managed throughout the program.

For a program of this nature, we need to work closely with the selected international partner to fully develop the Future Submarine. This is going to be very resource-intensive for both Defence and the selected international partner.

Once the partner is selected, there will be about three years of further development work before we finalise the Future Submarine’s capability and cost.

Indeed, lessons from the Collins Class submarine program and other international submarine acquisition programs clearly indicate the need for such collaboration to arrive at the best understanding of capability, cost and schedule.

We need to commence this intensive work without further delay to avoid a submarine capability gap in the future.

As it stands, avoiding a capability gap will require us manage the life of the Collins Class submarines beyond their planned withdrawal. We’ll need to continue to invest in the current fleet for years to come. It’s important we don’t lose sight of this—the Collins Class submarine will continue to be a potent capability for the ADF for years to come.

I’m looking forward to the comprehensive consideration of the CEP, and being able to announce our decision on the international partner for Australia’s future submarine next year.

Regardless of that decision, we need the sovereign ability to maintain that future submarine over many decades. And this will generate significant opportunities and challenges for Australian industry and the science and technology community.

Too much of a good thing?

Talisman Saber 2007

I had the chance last week to give a short presentation at the ADF’s Joint Warfare Conference. As a professional contrarian, I started my contribution with this:

‘Jointness is overrated. It’s a concept more valued by military professionals than it’s likely to be by Australian governments deliberating military action. In particular, the joint amphibious capability we’re going to put a lot of effort (and therefore opportunity cost) into developing probably isn’t going to pay dividends commensurate with the cost. Achieving interoperability with allies and partners is a better use of scarce ADF resources than joining up the individual services within it.’

When I say that jointness is overrated, that doesn’t mean that I think it’s not helpful or desirable. Obviously it’s preferable for the ADF’s various force elements to be able to communicate and coordinate their actions. There are low levels of jointness that are routinely useful: reliable communications between force elements and joint logistics to support a regional peacekeeping operation with a deployed joint headquarters, for example.

But in more contested environments jointness involves complex system integration and data fusion to support shared real time situational awareness and activities like cooperative targeting. And that’s costly. Like most military systems, jointness satisfies Augustine’s 7th law: ‘the last 10% of the performance sought generates one-third of the cost and two-thirds of the problems’.

So we have to think about the utility of those last few percentage points. The ADF certainly hasn’t needed that level of jointness recently. At the moment, the RAAF’s operating in a coalition air campaign, Navy’s off doing naval things off the coast of Africa and elsewhere, and Army has small deployments in a number of places. In none of those is the ADF delivering a joint effect, apart perhaps from the Army’s occasional use of air transport. We have to go back to the Timor operation in 1999 to see the ADF’s three services operating closely together, and even then it was in relatively benign circumstances. (To be fair, we weren’t sure at the time that things mightn’t heat up.)

Yet there’s aspiration to do much more, especially in amphibious operations. The 2009 and 2013 defence white papers said this:

‘The ADF would seek to undertake operations against an adversary’s bases and forces in transit, as far from Australia as possible. This might involve using strike capabilities and the sustained projection of power by joint task forces, including amphibious operations in some circumstances.’

Both documents went on to explain that the aim is to produce an amphibious capability suitable for employment across the spectrum of operational activities— from humanitarian and disaster relief through to power projection. That’s a huge span, and the upper end would require support from the ADF’s most capable combat platforms—fast jets overhead and air warfare destroyers, sea control from surface combatants and submarines, and extensive intelligence support. In short, most of the ADF’s capability would have to be mobilised to support amphibious operations in contested spaces.

I pick on amphibious operations because they require the most jointness. But at the high end I think they’re the sort of operations least suited to a capable but small force like the ADF. Lower down the capability scale it’s easier to imagine a circumstance in which a joint ADF capability would be useful. An evacuation of people at risk in the event of a breakdown of law and order or violent suppression by local authorities in one of the more populous regional nations would be challenging. Being able to move decisively to points of entry and to provide land and air mobility within the nation would be important.

So really I’m talking a matter of degree. If jointness was free I’d want as much as we could get. But it’s not free, and the higher we set the bar the more it costs. We need enough jointness to do the evacuation described above or replicate a Timor operation—the sorts of things we have to be able to do on our own. Anything harder is likely to see us operating with allies and partners rather than standing alone, so I’d argue that interoperability trumps jointness at a certain point.

If we can get interoperability and jointness so much the better. But if we have to choose one, interoperability should get the nod, and in many circumstances would give governments more policy options. I suspect a National Security Committee would rather spend an extra dollar on more interoperability between the ADF and the US, while Defence would probably opt for more jointness. In Iraq and Syria the RAAF has just demonstrated how seamlessly it can work with even the most sophisticated allies. It’s probably fair to say that the RAAF finds it easier to work with the USAF than with the Australian Army. And given what the ADF is likely to be asked to do in the foreseeable future, that’s not necessarily a bad thing.

Defence acquisition, capability managers and the Capability and Sustainment Group

Two recent articles on Defence acquisition one here by my colleague Mark Thomson and another in the AFR here by John Kerin quoting Warren King caused me to reflect on the long journey Defence has already travelled in the pursuit of acquisition reform and the enormous challenge it still faces as it stands up the new Capability and Sustainment Group (CASG) and implements the ‘Smart Buyer’ initiative.

The RAND Study into the lessons learnt from submarine programs in the UK, US and Australia observed (and later reiterated by the Parliamentary Review into Defence Capital Projects), that ‘…technical risks must be identified early, and much thought must be given to deciding, with industry (emphasis added), the appropriate form of the contract and the incentive and risk sharing clauses built into the contract. Getting this wrong can almost guarantee problems with the conduct of the program and the relationships between the government and the contractor.’

These issues aren’t new. Paul Rizzo identified the need for technical skills in his review of naval engineering. John Coles highlighted (PDF) in his Review the need for knowledgeable buyers to ensure program success. The ‘Smart Buyer’ function recommended by the First Principles Review (FPR) is clearly in response to these warnings but again the gap between the recommendation and implementation is as wide as ever. The re-occurring problem has been the Commonwealth’s ability to work with industry to achieve a capability outcome with some degree of consistency and confidence.

A well-run parallel bidding process as planned for the future submarine project certainly offers part of the solution. It should result in a refined solution, improved value for money as all parties refine and reduce risk and, most importantly, an improved capability outcome. Collaboration and transparency will be the key attributes of success but these can only be empowered by knowledgeable buyers and sellers.

Regardless of how successful the parallel bidding process is, the next phase—parallel negotiation—presents a real challenge if the well-informed buyer is missing.

Acquisition folklore tells us that parallel negotiation is the only true path to acquisition salvation. A process in which continued competitive tension improves schedule, price and process. Good process is rewarded with a good outcome, which is defined in terms of schedule and price.

The alternative view is that parallel negotiations increases the cost of bidding for both the Commonwealth, which needs to buy-in an evaluation team, and the bidders because of the time taken and the size of the team necessary to respond several more times over the length of the  negotiations process. What’s not spoken of is that this approach also enables an ill-informed buyer to hide behind a process which is invariably run by a team of earnest but constrained individuals with no guarantee of a better outcome for taxpayers or for the capability users. It may be ‘safe’ because it has a ‘defensible’ audit trail, but there’s no level of assurance that the final outcome will deliver good capability in a timely or cost-effective manner.

In recent years the DMO has been the customer and the user’s representative; the FPR suggests nothing different. This has resulted in capability managers being excluded from the acquisition process. An example of this was in 2007 in the early stages of JP 2072—the battlefield communications project. Prior to the contract being terminated by the DMO, an Independent Review concluded that the initial schedule delay was in part the responsibility of the Commonwealth because of confusion around requirements and access to the end users. This was after 18 months of parallel negotiations and due diligence. Instead of the contract being a framework for the successful delivery of the capability it became a tool for contract termination. It took another 7 years for JP 2072 to be retendered and renegotiated at considerable cost to both industry and the Commonwealth.

The capability managers must be more than just sponsors of the capability life cycle as the FPR suggests. They must be accountable for and lead in the knowledge of their business and the capability outcomes required throughout the process, not just in the requirements phase. This is not a role for desk officers.

Once government approval has been given there is a critical role for the senior leadership team throughout the acquisition process. The leadership team needs to understand operational risk and the level of compromise they are willing to bear in capability outcomes. This is an important and explicit authority that has been missing in the acquisitions process.

While the FPR focused considerable effort on the revised two pass process and structural issues, at the end of the day a successful capability process has at its core three players: industry, the capability managers and CASG. If these players perform their roles correctly, capability should be delivered on time and on budget.

As CASG comes into being there are couple of points worth considering:

Firstly, CASG needs to put aside the fear that any imbalance in their relationship with industry leads inevitably to a price/profit advantage to industry.

Secondly, the role and authority of the capability managers remains unclear in the FPR and requires clarification. Red cards abound but this is focused on giving Government comfort during the approval process—it doesn’t recognise where budget and delivery fails.

Finally, CASG’s ability to ‘make strategic decisions regarding the most appropriate procurement and contracting methodologies’ can only be achieved with the continued involved and authority of knowledgeable and engaged capability managers. Without their involvement, one or more of the three legs of successful capability acquisition, capability outcome, schedule or price, will fail.

Contesting contestability

A MRH-90 Taipan helicopter, conducts a vertical replenishment during First of Class Trials, onboard HMAS Canberra.

Andrew Davies’ three First Principles Review (FPR) posts on contestability (here, here, and here) make interesting reading for anyone who has been on both sides of capability arguments. While I agree with most of what Andrew wrote, there are two assumptions of his I would like to contest.

The first is the assumption that only non-military issues are the subject of contestability (such as cost and schedule). In many cases uncontested ‘professional opinion’ is the root of the evil, even when the mechanics of capability projects are well executed. The ‘Service Position’ often becomes synonymous with the professional military opinion, but in reality, it’s no more than the opinion that happened to prevail in the intra-tribal (read: service) debate. It’s sometimes based on individual or group prejudices and seniority. Once the service chief has formed an opinion, the organisation swings into uncontested decision-based evidence-making rather than evidence-based decision-making.

The second assumption is that the government’s own guidance is a suitable foundation for contesting force structure wishes. In practice, however, it’s all too easy to link a favourite capability to strategic policy by means of a reverse-engineered concept of operations or employment. All the armed services do this and each is free to fight a different war to the other two. It would not be difficult to fill an entire page with examples of the inter-service disconnections. Air Force puts little priority on sustained air defence of surface forces at the distances at which they expect to operate. It has little real expeditionary capability, unless operating from a pre-established base in friendly territory counts as expeditionary. Navy puts little priority on supplying fuel to forces ashore, but they could argue that neither of the other Services has much ability to receive serious quantities of it anyway. Army is getting steadily heavier with little regard for whether the other two services will be able to support its increased logistic demands and even less regard for its suitability for amphibious operations from the helicopter-centric LHDs. Perhaps contestability could usefully be extended downstream from strategic guidance to the operational concepts stage.

As Andrew Davies and others have pointed out, the Force Development and Analysis (FDA) office once served this contestability function, but was eliminated in 1997. So, can a new FDA-like entity challenge professional military opinion and try to impose some contextual discipline on concepts of operations? This is, after all, exactly what the FPR recommends. There is good reason to believe that it will fail, even if the new office under Deputy Secretary Defence Policy is given an allocation of suitably experienced military professionals. Ultimately any organisation comprising active service personnel is susceptible to pressure from the Services. The service owns their people, rates their performance and manages their promotions. Contributing to the defeat of the argument for a favoured capability or specific procurement is hardly likely to be career-enhancing. To a lesser extent, any organisation internal to Defence is susceptible to pressure to toe the corporate line—civilian or uniformed.

There is no easy solution, but an external body, including former Defence civilians—such as Andrew—and former military personnel would seem to be the most viable option. Arrangements for access to information would require careful consideration of course, but that isn’t insurmountable. There are various potential places for it to reside, even ASPI.

It would also strengthen many proposals by testing them and providing a measure of priority and proportionality relative to other capabilities competing for the finite resources available.

The report notes that Defence has been adept at ‘gaming’ the system and a purely internal contestability process is an open invitation to do exactly that. While an independent contestability body is a step beyond the recommendations, without it, the FPR could ultimately turn out to be just ‘another review’.

The demise of the Defence Materiel Organisation

Following the recommendations of the First Principles Review, the government has agreed to move the quasi-independent Defence Materiel Organisation (DMO) back into Defence. In its place will rise the new Capability Acquisition and Sustainment (CAS) group—effectively a pared down version of DMO with its top layer of management removed, but with substantial extra responsibilities in logistics and capability development.

The report’s language is interesting; the DMO is to be ‘disbanded’, which sounds like what you’d do with an outlaw motorcycle gang. That might not be accidental—DMO has made more than a few enemies over the years.

In 2003, the Kinnaird Review of defence procurement then recommended the establishment of a fully independent ‘executive agency’ to undertake acquisition and sustainment. The goals of the proposed separation from Defence were four-fold:

  • a more business-like relationship between DMO and Defence to support ‘clearer lines of authority, accountability and rewards for performance’
  • ‘more flexible remuneration arrangements’ to ‘attract and retain high quality project managers’
  • a separate identity so that DMO could ‘rapidly transform its culture and develop the commercial focus it needs’
  • give the head of DMO ‘sufficient power to be able to recommend against project proposals that do not have adequate risk analysis or are not fully costed’

Executive agency status was judged to be a step too far and, following push-back from Defence, the DMO was established as a financially-independent ‘prescribed agency’ in 2005. As a result, DMO was neither fully independent of Defence nor fully part of it. Nonetheless, the four goals were retained.

A decade later, here’s what the First Principles Review had to say about DMO:

‘The Defence Materiel Organisation has also been beset with problems that have impacted its ability to achieve the required outcomes. It is clear that the organisation has become top heavy, complex and unnecessarily deep. This significantly contributes to Defence not getting the capability it needs at a reasonable cost or in reasonable time.’

So what went wrong? One way to try to answer the question is to examine the progress towards the four goals from 2003.

There’s no doubt that the creation of DMO catalysed a more business-like relationship between the three Services and DMO. What’s more, DMO has been able to work with the Services and defence industry to drive efficiencies. However, at the same time, tensions emerged between DMO and Defence over finance. The issues are arcane, but because DMO and Defence each have their own financial accounts what’s best for one is not always best for the other.

Progress towards more flexible remuneration has been limited. Although the first Chief Executive Officer was employed on a salary exceeding that of either the Secretary or CDF, things slowed down pretty quickly after that. The problem was not that the Public Service Act provided insufficient flexibility, but rather that Defence wasn’t about to let DMO poach its staff and drive up its salaries. Frustrated, DMO did the only thing it could to get around the roadblock; a new layer of deputy secretary managers was born. Even then, the ability to attract the best talent from the private sector remained incomplete.

In terms of building a greater commercial focus, we’re confronted with conflicting data. There’s no denying that DMO has done a lot to professionalise and upskill its workforce. In addition, progress was made in establishing performance-based contracts, especially after the introduction of ‘smart sustainment’ in 2009. On the acquisition side, DMO was certainly a more formidable counterpart when it came to dealing with industry than its predecessors. And notwithstanding claims to the contrary, DMO has been very effective in delivering project within budget (though schedule remains a work in progress). Nonetheless, the First Principles Review believes that much more can be done via a ‘smart buyer’ approach with the private sector playing a greater role in managing both acquisition and sustainment.

Finally, if there was tension between DMO and Defence over financial matters, it was nothing compared with the rancour over whether DMO should provide independent risk assessments to cabinet submissions dealing with major projects. And there were other turf wars, such as the tussle over whether DMO’s financial workforce should be absorbed into Defence ‘shared service’ regime.

Would things have turned out better if DMO had become a fully independent executive agency as recommended by Kinnaird in 2003 and again by the Mortimer Review in 2008? Who’s to know? Greater separation may have prevented the squabbles over finance, staffing and advice to government, but it may have also introduced a different set of problems.

In the end, DMO had few friends. Sooner or later, something was going be done to reduce its power and independence. We can only hope that the pendulum has not swung too far back.

No doubt champagne corks are popping in the executive suites of defence industry as they look forward to dealing with a weakened contractual counterparty. But it must be a bittersweet victory for the folks over at Defence who will now have to take responsibility for the things that used to be blamed on DMO. Sometimes you’ve got be careful what you wish for.

 

 

First Principles Review: a plan to stick to

Below a welter of cliché and bamboozling modern management mumbo jumbo in the First Principles Review of Defence, there lurks much sound advice.

The government has bought it all except for an unconvincing recommendation about the Defence Science and Technology Organisation. It’s a good start.

Peever’s effort stands out from most of the external reviews of Defence over the last 15-odd years, some of which have likely made things worse. It’s not necessary to name names—the culprits are well known.

In significant parts, however, the Peever analysis isn’t as sound as its recommendations. For example, the report wonders why Defence ‘has been unable to reform itself,’ and suggests it may be due to increased operational tempo, budget uncertainty and high turnover of top leaders, including ministers. Those are more excuses than reasons—such things usually stimulate change rather than suppress it.

So if Defence ‘has been unable to reform itself’ in more recent years, why?

First, ‘reform’ has been largely outsourced to dozens of reviews, the dubious recommendations of which have piled on top of one another. This can make for confusing and distracted managers that could be excused for being less concerned about improvement when they can expect that external reviewers will be asked to do their job for them. Peever’s right to ask for a halt on external reviews that overlap with what he covers in his.

Second, too many people at senior levels with narrow divisions of responsibility and the associated additional requirements to consult have coagulated management and restricted possibilities for action.

Third, ‘reform’ needs to be pushed from the leaders at the top—that is, the defence ministers. With one exception: defence ministers since Robert Ray have been undistinguished. Few have taken a strong interest in the proper workings of the organisation. Indeed, a number have succumbed to the insidious notion that they are ‘customers’ of Defence. They aren’t, but when they pretend to be, management stasis is usually just around the corner.

The success of the Peever review will depend largely on the defence ministers getting behind it and not just getting reports from an ‘external Oversight Board’, as recommended by the review and composed of its members. That isn’t a good idea. Beware of reviewers urging their continued engagement. The Minister should be directing the operation and trusting the Secretary and the CDF to get on with it without an ‘Oversight Board’ looking over their shoulders. Peever reckons, rightly, that there are too many layers in Defence, yet he’s recommended the creation of a new one.

Of the many good things in the Peever Review, the following stand out:

  • Creating a stronger centre: centrifugal forces in Defence need to be contained; a stronger strategic centre should help to keep a better balance with a devolved management structure, although the Service Chiefs might not be thrilled at the prospect of having their wings clipped further.
  • Re-integrating the Defence Materiel Organisation: There’s a reasonable case for a closer connection between capability development and acquisition, and for removing the duplication of finance, legal and personnel functions that came with the DMO.
  • Cutting senior staff: the use of deputy secretary positions has been abused throughout the public service. They were designed to help secretaries overcome span of control problems. In Defence, as elsewhere, they’ve caused the very problem they were intended to overcome. Cutting seven deputies should, as Peever says, ‘cascade’ down the hierarchy and help to free up the organisation.

For all its virtues, the Review has some oddities:

  • It says that a new Defence Committee should be the ‘primary decision-making body’. Typically, defence committees are forums for consultation and promoting agreement. However, decisions on many matters that would come before the Defence Committee will need to be taken by responsible individuals in accordance with legislation or the revised diarchy powers that Peever recommends. Those say, for example, that the Secretary should ‘set the budget’ and the CDF should set requirements for enabling functions’ and the ‘workforce framework for the ADF’.
  • The Review recommends that ‘all policy functions’ be put into ‘one organisational unit’. It’s unclear why.
  • The Review describes finance as a control function. It might be better regarded as an ‘enabler’ and treated so organisationally. Peever also commends that the Chief Finance Officer position should always be filled by a qualified accountant. That’s ridiculous; it ignores the fact that some of Defence’s best CFOs haven’t been accountants.

However these are minor quibbles and, in general, Peever’s on the right track. It’s now up to the Minister(s) to see that Defence sticks to the plan.