Friday, May 10, 2013

What is really wrong with the aircraft carriers...



The new NAO report on the Queen Elizabeth class aircraft carriers program (also known as CVF, Carrier Vessel Future) unsurprisingly describes a world of ignorance within the MOD, and exposes the costs connected with some of the bad decisions made in the years.

But the 74 millions wasted in this double switch is nothing compared to the damage caused by far worse and even less coherent decisions taken by this government and by those which came before it. The 2008 decision to slow the program down, taken by Labour, added more than 1.5 billion of costs in the long term while adding absolutely nothing in terms of capability, so Labour should have the decency of just shutting up about this program in particular. 
But even this disaster is not quite the one i'm going to talk about. 

The real tragedy here is the lack of any capability to clearly select a path and follow it through with coherence. The ongoing uncertainty, the constant rethinks, the inability to recognize the capabilities that absolutely need to be preserved, are the real problems UK defence is wrestling with. 


Much more than carriers



Since the SDSR came out, i’ve been lamenting the total lack of coherence and strategy that is so evident in british military planning. The latest NAO carrier strike report adds even more to this astonishing awareness: the government and the MOD have no real idea of what they want to do.



There is not a focus. There is not a clear idea of what capabilities are needed and consequently no real plan to avoid gapping all of them in sequence. The ability of the MOD to fill up pages and pages of meaningless, useless rambling is amazing, but there is no evidence of a coherent plan behind the description “deployable armed forces”.



Deployable how? With what ambitions? With what means?



The provision of carrier strike is only part of an alarming lack of planning for the future. The “deployable armed forces” of the SDSR are facing, among others:




Soon to be gapped capability to deploy special forces safely by air, due to imminent withdrawal from service of the suitably kitted C130Ks, without Project HERMES having delivered the same level of capability on the C130Js.



Depleted capability to transport heavy equipment by sea, thanks to the removal of 2 out of 6 of the Point-class RO-RO vessels.



Insufficient air cargo capability, despite the welcome purchase of the C17s.



Depleted capability for the Army to operate in the Littoral and sustain its logistic effort in presence of water obstacles (removal from service of the Ramped Craft Logistic vessels without a replacement)



Dramatically reduced amphibious capability, due to the removal of 1 Bay-class LSD and the mothballing of one of the two LPDs.



Much depleted capability to operate at sea in presence of underwater and surface threats, due to the lack of a maritime patrol aircraft.



Much higher risks are due to be accepted in future when deploying the fleet in dangerous areas, due to the gapping of maritime airborne early warning capability.



Lack of air cover for the fleet for at least seven more years.



Most of the key enablers making complex deployments abroad possible have been or will be removed from service in the next few years. How does this fit in the ridiculous, vague claim about still having deployable forces?



It is time the MOD decided what it wants to be able to do, and take coherent decisions to reach the target.



The carriers are key enablers for an expeditionary force. They are indispensable in a wide range of scenarios which require the projection of military power far away from the UK’s shores. They are perfect for interventions that chiefly require air power, such as operations in Libya in 2011. But they are also excellent to gain air superiority far away from home and protect the arrival of land forces, including land-based aviation, which is notoriously most vulnerable on the ground, and which would incur huge risks in trying to deploy to a menaced base in a war zone in absence of friendly forces providing cover.



And they are of course essential to support a forcible entry operation, especially an amphibious assault.



For the UK, the two new aircraft carriers in construction are even more important because they are also the only possible replacement for the current LPHs platforms (HMS Illustrious and HMS Ocean), since the notional LPH(Replacement) program has been dead in the water at least since 2006.



A tiny spark of understanding of this factor emerged in the SDSR, when the Carrier Enabled Power Projection concept was revealed, and there was the first open talk of using the new vessels to carry not just fast jets, but Marines and their helicopters at the same time.



Ever since, the UK’s Strike Carriers have effectively been, in the facts if not in the design, Landing Helicopter Aviation vessels (LHAs). The Queen Elizabeth class is not just a replacement for the Invincible class carriers, but it is going to be the successor to HMS Ocean and to the “Commando carrier” HMS Illustrious (in itself a “re-rolled” Invincible class vessel).



Although non optimal, this is a coherent approach, and the only one financially sustainable and feasible, as the MOD is simply not going to be given the money to build and run the QE class purely for carrier strike, while fielding a number of sufficiently capable amphibious vessels.



While France has the nuclear powered Charles de Gaulle in the carrier role and three Mistral LHDs in the amphibious role, the UK will have to approach the problem differently.



In itself, this is because a quite debatable choice was made in the 90s to build an amphibious fleet made up by ships built around a single, main role: the LPDs (HMS Albion and HMS Bulwark) carry the best part of the task force’s landing crafts and the command and control facilities. The Bay-class LSDs carry the most of the “first wave” vehicles (more equipment would disembark later on from the civilian-standard Point RO-RO cargo vessels) while HMS Ocean (which had to have a sister which in the end was never built) would carry a big share of the Marines, and nearly all of the helicopters.



The separation in roles is dramatically reflected in the ships’ designs: the LPDs and LSDs have large flight decks, but lack hangars. Carrying and maintaining large number of helicopters on open decks at sea is nearly unthinkable, so HMS Ocean’s vast hangar is an absolutely fundamental part of any amphibious task force.



The separation of the roles is not a wrong concept in itself, but it is not a concept suited to the Royal Navy’s budget. As the failure in building a sister for HMS Ocean and the reduction in the original planned number of Bay LSDs (up to six, then reduced to four) remind us, even when the plan was first conceived it was not financially sound.


The reality is that, had the Royal Navy pursued the Landing Helicopter Dock (LHD) path and built Bulwark and Albion in such configuration, much better capability would have been obtained. The French Mistral class vessels are there to remind us of the mistake made.



The credibility of the amphibious capabilities of the UK in the era that will follow the decommissioning of HMS Ocean rests in the cavernous hangars of the QE vessels and on their vast flight decks: the new carriers are desperately needed to keep the RN able to deploy meaningful task groups in the future.





Can’t think more than half an hour ahead





The return to the F35B has one only real advantage over the F35C: it removes the large short term expenditure which would have been needed to modify HMS Prince of Wales at build to take aboard the US EMALS catapults and AAG arrestor wires.



In the long term, the F35B risks to cost more and is surely going to deliver less capability than the F35C. In terms of costs, the NAO notes that the F35B is at least 10 million pounds more expensive, per plane, than the F35C. More importantly, its through-life running costs will be 20% higher. And other sources have suggested 25% higher.



There is a real risk that the reversion to the F35B will end up being a “save now, spend more later” decision. The NAO in its report suggests that, over a 30 years period, the F35B will cost 600 million less than the F35C option, but I’m unconvinced.



We could regret this decision in the future for a whole range of reasons: the inferior capability of the F35B could end up being a problem some day. Its cost, already expected to be higher, could escalate further. Worse, catapults and wires could soon end up being needed all the same, when the importance of large, weapon-capable unmanned aerial vehicles will grow enough to make them indispensable even for a MOD which is getting way too used to look the other way and ignore uncomfortable facts.  



For now, the MOD is hiding its head under the sand by deciding that the first UCAV (notionally planned for the 2030) will be a purely RAF affair, and will only operate out of land bases.



A great example of joint thinking and long term strategic planning, isn’t it?



I have to accept the bitter truth, however: in this case, the MOD did not have the chance to think ahead. The treasury was in no case going to help the MOD cover the higher initial costs of the catapults solution, so there was no way to accommodate the conversion costs in the budget without cutting savagely back in many other areas of Defence. 
However, the decision to return to the B can only be truly accepted, supported and welcomed if it means retaining both carriers in service. The high cost of fitting catapults and wires would have made it virtually impossible to operate both ships in carrier role. The second could and should have served as LPH, for the reasons covered earlier, even though the lack of strategic thinking of course made the government conceive the absurd, insane idea of selling or mothballing such a precious asset.  



However, the F35B makes it possible to operate both vessels as LHAs, combining the provision of combat air capability to the provision of helicopter support to amphibious operations. With the advantage that, with two hulls, an LHA is always available for deployment. 
The one thing that the return to the F35B must give us is the entry in service of both ships. 



Of course, the above concept is too simple to be readily grasped by government and MOD, and we are vaguely tempted with the option of having both ships in service, while the actual decision is pushed back to 2015.



If we ever needed a reminder of the appalling inability to think more than half an hour into the future, we have just been given it.





Self-inflicted problems



The capabilities of the F35 for the UK are further harmed by, again, the lack of a coherent plan inside the MOD. So far, the UK has only required the integration of ASRAAM and Paveway IV onto the aircraft, and according to the NAO even these requirements haven’t yet been finalized and fully costed.



There is also an ongoing saga about how and where the ASRAAM will have to be fitted on the F35: at the beginning there was a (ridiculous) requirement to integrate four ASRAAM for internal carriage. Why the RAF deemed necessary to spend huge amounts of money to try and carry four short range, infrared-guided missiles in the enclosed weapon bays of a stealth fighter goes beyond my possibilities of understanding. A return to the first Sea Harrier, with the ASRAAM carried internally replacing the Sidewinder carried externally?



It becomes even more ridiculous when you think that no one else is bothering with trying to integrate an IR missile for internal carriage on the F35; and it becomes worse when you realize that carrying 4 ASRAAMs internally means not carrying AMRAAM and not carrying air to ground weaponry.



In 2008, the difficulties and cost of such a stupid idea became clearer, and the plan changed, with ASRAAM to be integrated on the two internal AA stations in replacement of the AMRAAM and on the two AA-only external stations under the wings.



Today, it is not clear if this is still the plan of if the ASRAAM is now only due for external integration. 

ASRAAM: stations 4, 5, 7, 8 then rethink, 1, 4, 8, 11. And now?



With the AMRAAM due to leave british service by 2017 and a plan for the integration of Meteor on the F35 having not been finalized yet, the F35 at entry in service risks being as well armed for air to air combat as a Tornado GR4. How to downgrade a multirole aircraft to an under-armed bomb truck.



For a good few years, it appeared that the UK might not integrate Meteor at all on the F35. Hard not to think that the RAF was doing so not to harm procurement of the Typhoon. After all, the one service getting the bad end of the deal would have been the Navy, which ever since it lost the Sea Harrier FA2 has been tragically lacking a capable fighter for the air defence of the fleet.



Fortunately, MBDA, aiming to export opportunities, self-funded efforts to make the Meteor compatible with the weapon bays of the F35, and now the MOD seems to have regained a little bit of wisdom: a recent interview saw the Italian chief of the defence staff confirm that the UK has asked Italy to join a bi-national effort to integrate the Meteor on the JSF, presumably as part of the Block IV software release.



We have to hope that this is confirmed, otherwise the F35 might be done to the sole ASRAAM for a good few years, well into the 2020s.



The Paveway IV is only meant to be integrated on the two internal AG stations. Why?

Good question. I can’t find an answer.



Other weapons have been deleted from the list of requirements (Paveway II and III, Brimstone, Storm Shadow) and will only reappear… sometime, later on. Maybe with the Block V software release.



Just maybe, though. The NAO reports:



The Department is now planning to procure 48 STOVL aircraft in the first tranche in the same quantity and production profile as the carrier variant. Given that the STOVL variant will deliver an aircraft with less range and endurance over a target area compared to the carrier variant, the decision potentially represents a reduction in capability. However, since 2010, the Department has confirmed that it does not have plans to use weapons which would require the greater payload capacity of the carrier variant.





That reads to me like an admission that the F35B is not planned anymore to be able to employ weapons such as Storm Shadow. I hope I’m wrong, because it would make absolutely no sense if this was the case. They hopefully mean that they have no plan to procure a 2000 pounds bomb for internal carriage (the F35B has weapon bays that are 14 inches shorter than the F35C’s ones, limiting it to weapons with the same volumes as the US 1000 lbs JDAM.  



However, the things that make no sense are so common these days around the MOD that it wouldn’t surprise me if my pessimist interpretation was correct.



Among other self-inflicted problems, it is worth highlighting these passages of the NAO report:



As the Carrier Strike capability draws upon both air and navy forces, there is a risk of divergent views on delivering its benefits. There have also been a wide range of views as to what constituted the wider capability known as Carrier Enabled Power Projection while the Senior Responsible Owner has lacked budgetary power and authority to bring coherence to its elements which draw upon the different forces.



As a result, and to address concerns raised by the Committee of Public Accounts, in response to our Carrier Strike report, the Department made the Programme Director of Carrier Strike a full-time, two-star role and gave the role of Senior Responsible Owner for Carrier Enabled Power Projection to a three-star officer responsible for capability decisions across the Department. This move has effectively strengthened the budgetary authority of the role and in April 2013 their mandate was also clarified. The Senior Responsible Owner chairs an Executive Programme Board which is attended by those responsible for the delivery of all of the key elements of the capability. These changes are a welcome clarification of previously inadequate governance arrangements; however, the Senior Responsible Owner will continue to face difficult challenges in successfully delivering the Carrier Strike capability and overcoming the historic, cultural differences between the forces.





I don’t even want to comment this. I think it speaks by itself. To keep the matter under some degree of control, it has taken the formation of a castle of multi-star posts, just like it happened when Joint Helicopter Command had to be formed to remedy to the inconvenient placement of the battlefield support helicopters under RAF command instead of in the hands of the Army.



Thanks for confirming once more that bringing the RAF into the business of naval aviation ranks high among the worst decisions ever made.



The only relief provided by the NAO report is the information that the Chief of Defence Staff is uncomfortable with the lack of carrier air capability and applied pressure to avoid gapping it for any longer time than strictly unavoidable. This is reassuring. However, Chiefs change, and the presence of the RAF in the carrier air equation risks being a source of problems and infighting forever. Will we always enjoy the presence of a Chief of Defence Staff capable to preserve the carrier capability, or will we end up having a new Harrier tragedy?



Or a Nimrod tragedy, too. You can choose your favorite disaster.





Lack of vision



Another stunning demonstration of the lack of honesty and understanding within the MOD planning is the disastrous approach to the replacement of the Airborne Early Warning capability currently provided to the fleet (and to the joint force, as the enduring commitment to Afghanistan demonstrates) by the Sea King MK7 ASaC.



Already some time ago I had written that I was only waiting for the inexorable coming of the idiotic comment sayings that, with no carriers in the water, we don’t need AEW either.



Could I be kept waiting for once? Of course not.



Defense News reports on the NAO document and notes the statement offered by Hammond in reply:



The Department does not consider that the phased introduction of Crowsnest undermines the delivery of carrier-strike capability. Crowsnest will enter service at the same time as HMS Queen Elizabeth and will be fully operational by 2022. Until then, its maritime surveillance capabilities will be augmented by other platforms and systems.






There is one, and one only advantage that an helicopter-based AEW solution offers over the much more capable Hawkeye aircraft: an helicopter can be based on almost any kind of modern warship.



Sea King MK7 has in recent times been operating from HMS Ocean as well as HMS Illustrious, and it has also been aboard Type 45 destroyers.



An helicopter AEW platform, or HEW, If you want, with the H for Heliborne, has the advantage that it can provide any kind of flotilla an invaluable AEW solution, even if there is no large flat top in sight.



HEW does NOT NEED the carrier.  



The carrier NEEDS the HEW platform.



Moreover, not only the carrier needs HEW, the whole fleet NEEDS HEW.


Conclusion: the lack of a carrier does nothing to reduce the importance of HEW.




The need for early warning of incoming air and, later on, missile attacks has been clear even since the 1940s. The massive air attacks, and the threat of the japanese Kamikaze in the Pacific theatre were the original driver for the quick development of early warning solutions.



First was the radar picket ship, vessels fitted with powerful radars sent ahead of the task force to form a first line of defence and to provide early warning to the thick of the force.



Of course, being on a picket ship was a very dangerous job: picket ships were the first to be attacked and the first to be sunk.



Desperation with this situation brought to the light a number of imaginative solutions, including the use of submersibles fitted with radars, destined to stay on the surface to track enemy air activity. Submersibles were harder to spot from the sky, and could always dive underwater, so they had much better chances of surviving the day. But they also made for poor platforms for air control radars.


Nonetheless, the US Navy did use many such EW vessels. The last such boat to be kitted for the role was a nuclear propelled submarine!



Fortunately, by then, technology had progressed enough to make airborne EW platforms viable and effective.




Already once the Royal Navy had the great idea of gapping the AEW capability. It was swiftly punished with the Falklands War, which saw the senior service having to take a step back in time, all the way to using picket ships and, to a degree, submarine EW as well, when five submarines formed a line on the edge of Argentina's 12-nautical-mile (22 km; 14 mi) territorial limit to provide some form of early warning of incoming air raids.  



A cost was paid for this in sunk ships and lost lives. HMS Sheffield is a good image of this, as she was a picket ship, deployed ahead of the main force to make up for the lost capability provided, until not much time before, by the Gannet AEW aircrafts of the old HMS Ark Royal (IV).



Evidently, not enough ships and lives were lost, because the MOD is once again planning to gap this vital capability, from 2016 all the way to 2020 or, more exactly, 2022. Four to six years of return to “stone age” for the Navy.



There is no hiding behind the superior capabilities of the Type 45 and of its Sea Viper missiles. Physics has not changed, and the radar horizon for the detection of low-flying enemies continues to be too close to the ship for defences to work properly.



And at the Falklands the threat was the subsonic Exocet. Today, the threat could well be a massive, supersonic Yakhont missile fired by the BASTION coastal defence batteries sold by Russia to countries such as Siria.



Defences might have improved, but offensive weapons also have, and a missile coming low on the waves at Mach 2 or 3 will leave a ship struggling to react in the few seconds it’ll have between detection of the incoming threat and impact.



But perhaps mr. Hammond believes that the enemy will not want to use its missiles against frigates, destroyers, amphibs and merchant ships. Maybe the enemy will only fire its missiles if there is a carrier to try and hit.



Maybe. But I don’t think so. And Hezbollah doesn’t, either. There’s many people out there who probably don’t agree with mr. Hammond.



I hope, not for him but for the sailors that would pay the ultimate price in such an event, that he can get away with this insane decision without having his own HMS Sheffield moment. 



A decision taken is never definitive  

Another dramatic problem is the dramatic way in which programs even of primary importance tend to drag on and on and on without ever delivering. Even when the MOD takes a decision and starts some kind of activity, it takes uncountable years and uncountable acronyms and "studies" and "assessment phases" and "main gates" and "planning rounds" to get any progress in. 
Again, we return to the tragedy of AEW. 

The Royal Navy has been trying to find a replacemet for Sea King MK7 for well over a decade. We were still in the 1990s when the Future Organic Airborne Early Warning Aircraft (FOAEW) started. And with further research we might find out that the activities started earlier still. 
In the early 2000s the acronym changed, to MASC (Maritime Airborne Surveillance and Control) and in 2010 we arrived to the current CROWSNEST name. 

Capability delivered: none. 

Only this year CROWSNEST has entered the Assessment Phase. The selected path is to fit palletized radar equipment to the existing fleet of Merlin HM2 helicopters, with two proposals to choose from: Northropp Grumman/Lochkeed propose the VIGILANCE radar pod, which they have been testing in flight since last year, on a Merlin HM2. 
Thales proposes migrating the CERBERUS/Searchwater 2000AEW kit from the existing Sea King MK7 to a the slightly modified Merlin HM2 airframe. 

Thales proposal, with existing radar from Sea King MK7 migrated and fitted on sliding rails on the side of the Merlin HM2 fuselage.
 
The Vigilance pod proposed by Lochkeed.
Nothing revolutionary at all, in other words. It proposes to use an helicopter which will return in full service after the upgrade to HM2 standard over the next year. An helicopter that is currently planned to leave service in 2030, notably. 
If Thales wins, even the radar could remain the same, perhaps just touched up a bit. 

Yet they are dragging it along, for budget and non-budget reasons, so much to expect an entry in service only in 2020, with systems that won't be fully operational before the end of 2022. 
That's 9 years from the start of the Assessment Phase, and well over two decades after the whole saga began.    

To set the proportions straight, the E2 Hawkeye was born from a US Navy requirement in 1956, entered service as E2A in 1964 and by 1971 it had been completely upgraded twice, up to E2C standard. All in 15 years

I won't add anything else. I think facts speak loud enough. 
   
     

Saturday, May 4, 2013

My alternative proposal for Army 2020

I promised quite some time ago now that i would try and take a shot at a coherent, realistic, alternative Army 2020 plan, which would not move away from the 82.000 regulars and 30.000 phase 2-trained reservists numbers. No fantasy fleet, in other words, but a serious, disciplined attempt, because of course it remains an exercise of theory, to put together an alternative structure.


My planning has been done building on a number of firm points:

Army 2020 is not just about manpower. It is about training and basing infrastructure as well. If i suggest a whole different army structure, like the original plan for five multirole brigades each comprising heavy armor, i must plan for fewer battalions, because i'll need to move money out from the personnel budget to spend it on infrastructure to prepare other bases around the country for the arrival of heavy armor. New training areas will be needed, and this will imply big expenditure.

I'm sticking to the basing plan released by the MOD as much as possible. I think the basing of the army brigades and units is one of very few things that have been done with real wisdom in these three years. Mind you, there are still challenges, but it is a very good basing layout overall.
Moreover, it reprensent a financially realistic plan. I could suggest different choices, but i could not realistically cost them and say that they would be achievable with the same budget.

I'm not going back to the multi-role brigades because they imply some real challenge in terms of training areas and infrastructure. It is a wise thing, overall, to have the "peacetime" brigades divided by role and by geographic considerations. Salisbury Plain is the right place for the heavy armour. Complementary capabilities, lighter in nature, will come from other brigades.



The above points explain what i'm not changing. But there are other considerations that have made me take several choices different from the ones made by general Carter's team.

The UK's first line of defence is represented by the two high readiness brigades: 3rd Commando and 16 Air Assault. These two brigades are planned to sustain a very challenging rhythm, generating, constantly, battlegroups to keep at very high readiness: the 1800-strong Commando Lead Battlegroup and the 1300-strong Air Assault Lead Battlegroup. This is an Army 2020 / SDSR firm point, which has been, in my opinion, badly betrayed by the choices made in terms of force structure.

I'm fine with the removal of 1st RIFLES battalion from the Commando brigade, but i'm absolutely opposing the reduction of the brigade's engineer capability to the sole 59 Independent Squadron plus Reserve Squadron. It is an insufficient level of engineering support to enable the brigade to deploy whole without being reinforced by other elements scraped up from some other formation, and, worse, it is too little to ensure that the constant formation of serious battlegroups at high readiness can be formed.

A battlegroup should comprise one Commando battalion, one artillery battery, one Commando Logistic Task Group comprising the medical capability and surgical group, C4I capability from 30 Commando IX and one squadron of Engineers.
All elements can be sustained, in general, save for the Engineer component: how can a single squadron, even with a reserve capability available, sustain a constant state of high readiness? It just won't be able to do it.
And the Commando battlegroup will end up weak on combat engineer support, despite the Agile Army studies saying that combat engineering will be high in demand in future ops.

My first move is to keep 24 Commando Engineer Regiment, with HQ Sqn and three regular squadrons. 59 Independent Sqn currently holds most of the capabilities of an HQ Sqn, being alone in the role, so the manpower impact mostly comes from the need for two more field squadrons.

16 Air Assault brigade, has no combat engineer problem, but has its own issues too. First of all, the reduction to just two regular battalions plus 4 PARA (Reserve). Again, this just doesn't do the job in my opinion.
In my army structure, i resurrect an old plan, dating back several years, and assign the british-based Gurkha battalion to 16AA Brigade. The battlegroup at High Readiness will have to be a mixed battalion, formed by two Aviation Companies, good for helicopter assaults and for running out of a C130 following a tactical landing, plus a parachute-current company, capable to airdrop if and when necessary. The Gurkha battalion will be tasked to provide Aviation Companies, obviously. No parachute training, there's no money (and arguably no need for additional capability other than the enduring ability to airdrop a single Company group at any one time).

The Gurkha battalion is chosen because it is based in an acceptable position, and because it is not a formation that has problems recruiting and staying fully manned. 
This change is roughly manpower neutral.

I'm also proposing the formation of a new unit for the air assault brigade: an HQ Troops / Information Exploitation battalion on the model of 30 Commando IX.
This formation would be built up using the RMP element, the brigade HQ, 216 Signal Sqn and Pathfinder Platoon, and it would continue to draw from other army formations for additional capabilities: an air defence troop with Starstreak LML taken out of 12 Royal Artillery, EW teams from 14 Royal Signal regiment and so along.
The manpower increase would come from the re-formation of the 1st Airborne Reconnaissance and Surveillance Squadron (which would build on the history of the WWII airborne reconnaissance sqn), which would include in its strenght the current Pathfinder platoon but would add a standing Brigade Recce Force dedicated to the particular needs of 16 AA Brigade. The Squadron would have Jackals as main vehicle.

Note that there is a possibility that this move would actually be manpower neutral: so far, the Household Cavalry regiment has had an additional squadron in its establishment in order to provide recce support to 16AA. It is not clear if this will continue, under the current planning.

These changes are meant to better and more realistically enable the High Readiness brigades to cover the roles they have been given.



Flexibility must be real, not a catchword. The current Army 2020 plan abuses, in my opinion, of virtual "centralisation" of support units under specialised brigade HQs. I think this arrangement adds no flexibility at all, especially when we consider that the regiments are configured very differently depending on wheter they are Reaction Force-oriented or Adaptable-oriented.
The basing plan has also made good, rational efforts to base regiments in the best possible locations depending on their configuration.
Why have the three Reaction Force's artillery regiments in Larkhill, near the manoeuvre brigades they are meant to support, only to subordinate them to an "Artillery Brigade" based in Tidworth which is also supposed to control regiments located as far away as Newcastle?
It just makes no sense to me. It adds nothing good to the army's capabilities. It possibly hinders them, in fact.
I can't think of another major NATO power even considering the same idea. Not the US, not France, not Germany, not Italy.

My opinion is that intimate combat support elements must remain an integral part of the manoeuvre brigade, especially when the basing plan makes it possible.
So:

1) Disband 1st Artillery Brigade, re-subordinate artillery regiments to the relevant brigades.
2) Move Close Support Engineer regiments out of 8 Engineer Brigade back to the brigades.
3) Move Medical regiments back to the brigades' control.
4) Directly assign to the brigades their Close Support REME battalions.

The same could perhaps done to Logistic (RLC) regiments as well, but in their case it might make more sense to have them in two Logistic Brigades, assigned each to one of the two main deployable brigades.
The Logistic Brigades will include the Force Support REME battalions as well.

The Adaptable Force as currently envisaged in my opinion kind of forgets one of the main points of Carter's own assumptions: an Army is for warfighting, first and foremost. The structure of the Adaptable Brigades as of now is unnecessarily complicated and confused. There are, in the plan, three "main" Adaptable Brigades, but in the facts they are paper tigers, weakened by having their establishments hindered by the need to sustain Cyprus and Woolwish (Public Role) deployments.
Since it is possible to make sure that these brigades are properly configured at all times, with 3 manoeuvre battalions in force, i can't see why we shouldn't do that.

These three "main" brigades will be, as now, the Cottersmore-centered 7th, the Catterick-centered 4th and the Edinburgh-centered 51st.
Some Infantry battalions will need to be subordinated differently from what is now planned. The three mechanised battalions for the Reaction Force will now be the ones based in Aldershot. The change basically means removing from the role 4 SCOTS, which is based as far away as Catterick.
4 SCOTS will now be part of 4th Brigade instead, alongside with 2nd LANCS, which currently would respond to 42nd Brigade.
7th Brigade will assume command of the Guards battalion posted to Pirbright, while the battalion rotating into Public Role at Woolwich will fall, for the duration of its posting there, under the command of the Guards brigade.

In this way, it is possible to keep the strenght of the manoeuvre brigades up, even as battalions rotate in and out of Cyprus and Public Duty.

In an additional effort to make these brigades genuinely deployable, i'm giving them the combat support elements as well. The current Army 2020 plan includes two regular engineer and artillery regiments for the Adaptable brigades, because it privileged the achievement of the minimum number of five enabler formation per each role, so to support the capability for enduring brigade-sized deployments in the future.

I'd like to go a little bit further, and give all three brigades an artillery and engineer capability, so that the three main Adaptable Brigades can do their own 36-month readiness cycle complete of their enablers and thus ready to tackle deployments abroad in operations of some complexity. To do so, i'd backtrack from the plan to disband 40 Regiment Royal Artillery and 28 Regiment Royal Engineer, and use integration of regulars and reserves to keep these two formations at full strenght with minimal change to regular manpower figures.
From the current plan, which calls for 2 regular and 2 reserve Light Gun artillery regiments, i'd move to a plan with three mixed regiments, each with two regular and two reserve batteries.

My assumption (and the Army's one as well, it would appear) is that, to "equal" a regular sub-unit availability with a reserve sub-unit, you need to have two reserve sub-units. This is due both to manpower and training worries regarding the reserves, both to the fact that reservists can only deploy for a 6-month tour once in a 5 years period, while the regulars would do two tours in the same timeframe.
Having two reserve sub-units is meant to make it realistic to expect that the regiment could deploy with a mixed regular/reserve manpower delivering a full three batteries / squadrons /companies without exceding harmony guidelines.

Guidelines for the employment of Reserves

In the engineer field, it would appear that the plan already is for two integrated regiments, with 2 regular and 2 reserve squadrons each.
I would add a third regiment equally configured, at the expense of one of 3 currently planned Force Support engineer regiments (Reserve).
For the regulars, this means one additional RHQ and two additional engineer squadrons. 

Two regular medical regiments are already planned. A third regiment could be provided via an adequately reinforced reserve regiment.

The REME situation is the same: 2 close support regular regiments can be completed by a reserve REME battalion, taken away from a currently planned 4 Force Support battalions for the Adaptable Force.

On the Logistics front, there are two regular Force Logistic regiments planned for the Adaptable Force. The Force Logistic regiment is described as a hybrid unit comprising Supply and Transport/Fuel capability.
While the Reaction Force brigades, logistically heavier, are each supported by a Close Support Logistic and a Thetre Logistic regiments, the lighter Adaptable Brigade are supported by a single hybrid formation.
The equivalent of a third Force Logistic regiment is already planned, under the shape of two Transport and two Supply regiments of reservists.

The above changes are roughly manpower neutral: the number of squadrons and batteries remains the same. The number of Regimental HQs reduces.
However, the barracks in Ripon, which are now home to an engineer regiment but are currently planned to close as the regiment moves to Catterick, in my plan would remain. The third reg/res engineer regiment would be housed in Ripon, in fact.

To balance the changes in manpower and basing that i've described, my alternative Army 2020 reduces the infantry by a further battalion. Difficult choice to make, but the only one possible in my opinion. My proposal would imply the disbandment of 2nd MERCIAN and the closure of barracks in Chester, instead of Ripon.


Agile Warrior studies have concluded that future deployments should see the brigade HQ helped by a Division HQ. The brigade staff must be able to focus on the tactical aspects of the operation, while the 2-star HQ covers the strategy and the theatre-wide issues including theatre logistics. Despite this, Army 2020 proposes a rather confused future of the Divions of the british army.

My plan would see the downgrading of the LONDON DISTRICT, a two-star post not really necessary, in exchange for a more readily deployable capability within 1st UK Division HQ. The division would command the three "main" Adaptable Brigades.

The currently planned 2-star HQ UK Support Command would also revert to being a more traditional Division HQ, not immediately deployable but nonetheless more outward looking.
This Division would command the remaining Adaptable Brigades plus the Guards brigade (result of the downgrading of LONDIST).

The Guards brigade, non-deployable, would act as a container for the units based in the London area for their public duty period. Nonetheless, the Falklands Roulement Companies will come out of the battalions of this brigade. For what i understand, this already happens, but not all the time. In future, i'd want it to be the rule, because the army is stretched and can't afford to lose so many resources to ceremonial roles.

Then there would be three Reserve brigades directly paired to the three "main" Adaptable Brigades.
11 Brigade, the South HQ, would be paired to 7th Brigade. 11th Brigade, for geographic reasons, would also control the reserve elements supporting the Reaction Force, namely the 100 RA regiment, which i propose as possible new GMLRS reserve formation (since the regular GMLRS are moving south, from Newcastle to the Salisbury Plain area) and the Royal Wessex Yeomanry which will continue to provide reinforcement/replacement crews for Challenger 2 MBT formations.
42 Brigade, the HQ North West, would be paired to 4th Brigade.
52 Brigade, which would be re-established, would be paired to 51st Brigade.
These brigades, as much as possible, mirror the regular formation they support and integrate, so there is a TA infantry battalion for each regular one, and a TA Cavalry regiment for each Regular one.

The shifting and re-subordination of squadrons from the Royal Mercian and Lancastrian Yeomanry regiment to reform a Scottish Yeomanry regimen is apparently already on the cards.  

Lastly, there would be two mixed regular/reserve brigades, 38th and 160th, which would be the first choice for upstream defence engagement abroad.

The Force Troops element would be much the same as currently planned. Since Agile Warrior has confirmed the absolute, capital importance of Maneouvre, it is absolutely fundamental to preserve a number of specialised capabilities that make maneouvre possible. I'm speaking of the TALISMAN route clearance capability, and of the M3 rigs for rapid river crossing. These two capabilities would be preserved each into a Squadron of the Land Support regiment, 36 Engineer.


Summary of changes:

Regular 2-star HQs: -1 (LONDIST)
Regular 1-star HQs: -1 (Artillery Brigade)
Reserve brigade HQs: +2 (52 Bde, Guards Bde)

Regular regimental HQs: +3 (24 Commando Engineer, 28 Engineer, 40 Royal Artillery) NOTE: 24 Commando RHQ virtually manpower neutral change, due to HQ capabilities otherwise being part of the Independent Commando Sqn
Reserve regimental HQs: -3 (2 Light Gun artillery regiments, one Force Support Engineer regiment)

Regular Artillery Batteries: +1 TacGroup Bty (number of gun batteries unchanged, but spread over three regiments each with 2 gun batteries instead of 2 regiments of three batteries)
Reserve Artillery Batteries: Same (spread over three regiments instead of grouped up in two)

Regular Close Support Engineer Squadrons: +4 (?) (it depends on wheter the two currently planned Adaptable engineer regiments have 2 or three squadrons each, not yet clear) (2 Commando Engineer squadrons, 2 Adaptable Sqns)
Reserve Close Support Engineer Squadrons: +2
Reserve Force Support Engineer Squadrons: -2

Reserve Force Support REME battalions: -1
Hybrid Regular/Reserve Close Support REME battalion: +1

Regular Infantry Battalions: -1 (2nd Mercian)
Reserve Infantry Battalions: Same

Base closures: Ripon to stay, Chester to close


I believe my Army 2020 proposal delivers an army which is both more flexible and more realistically aligned to the Defence Planning Assumptions set by the SDSR. In addition, it makes efforts to try and adhere to the findings of the Agile Warrior studies.

In a way, my proposal returns to a concept of business that the Army has already experienced in the past, when three Armored and three Mechanised Brigades were meant to have their own 36 months cycle of force generation.
At any one time, in this way, one Armoured Infantry (Reaction Force) and one Light/Mechanised (Adaptable Force) brigades would be trained and ready for operations. The Adaptable brigade could be deployed on simpler interventions, or provide elements to be combined with regiments coming from the Reaction force to form a Multi Role Brigade with the correct mix of capabilities.

How it used to be

One problem, highlighted by Agile Warrior but harder to fix without a proper budget, is the fact that the British Army remains filled with Light Infantry, and is arguably the less mechanised army within the major forces in Europe. There is a very evident gap between Warrior and Foxhound, which FRES UV, currently planned for just 3 infantry battalions, is not going to close.
To improve the situation in this field, a complete rethink of FRES UV is in order, i think. One option would be to take a step back from the expensive, top class 8x8 AFV, and re-assess the possible "good enough" solutions. France is planning to buy hundreds (a thousand, possibly) of 6x6 VBMR vehicles for its medium weight, multirole brigades. Their requirements for the new vehicle are rather ambitious, and include excellent protection for a section of up to 9 soldiers, at a cost as little as 1 million euro per vehicle. My suggestion is to follow this interesting procurement effort with attention: it might be advantageous to go along with the french for once, with the hope to Mechanise at least a further three battalions, one for each "main" adaptable brigade.
It would be a step in the right direction, compliant with the Agile Warrior recommendation to re-mechanise the army.