A proposal from Anglo Engineering Concepts to meet British Army vehicle capability gaps and drive down support costs by adopting system engineering thinking and a design language that places the designer close to the user.
Anglo Engineering Concepts is run by an experienced design engineer that previously worked as one of the three design engineers in the Drawing Office of Alvis. The design engineers’ remit was to bring forward realistic innovation – this approach of creating designs stretching beyond current capability that could be manufactured in the near future from available technology has since remained a core design principle. In more recent times, this same design engineer was part of the team that created Lockheed Martin’s AVA wheeled vehicles that were exhibited at the DE&S DVD events.
The designs described below have been reviewed by serving Army personnel, by MOD and DSTL personnel, and by various experts in industry, including the former Manager of the Alvis Drawing Office. Generally (and it is to be hoped not just out of politeness) the designs have been well received.
Some design choices caused concerns, but wherever possible these concerns have been addressed in subsequent revisions. This highlights another core principle behind the design work – that solid direct communication between designer and user is essential to effective vehicle development.
A Short History
When the MOD embarked upon a replacement programme for CVR(T) it at first seemed, under FFLAV, that modern, more capable and better-protected versions of the Scorpion family were sought. This seemed rational; there are tasks ideally suited to small-light-fast armour which MBT sized vehicles or up-armoured Land Rovers cannot perform as efficiently, if at all.
FFLAV though did not progress to a procurement programme.
The TRACER study that succeeded FFLAV was far more ambitious. As the TRACER programme progressed, the vehicles grew larger and heavier, although still nowhere near MBT size. There seemed to be a capability gap opening up between Land Rover sized CVR(T) and this new breed of digitised high tech reconnaissance vehicles.
Many in industry saw a need for light armour and moved to offer solutions – Stormer 30 being an obvious example.
When FRES described a need for C-130 transportability, simple, light and upgradable armoured vehicles like Stormer 30 were brushed aside as the new programme would deliver exactly that class of vehicle, only better.
Skip forward many years; as we all know, FRES eventually delivered something that is the width and height of an MBT, at half an MBT’s weight and with half an MBT’s engine power.
When FRES turned heavyweight, BAE toyed with what seemed to be a relaunch of Stormer 30, the hull updated and apparently carrying a version of their FRES CV90 prototype turret possibly armed with the Mk44 Bushmaster cannon, but it appeared only as a low fidelity graphic:
This vehicle, it seemed, never reached prototype stage, but CVR(T) derived designs continue to emerge – there are rumours another Stormer 30 rebirth is imminent but yet to break cover – which only serves to show how good the CVR(T) concept was way back in the 1970s.
Anglo Engineering Concepts sprang from a conviction that Ajax could not perform the same tasks that CVR(T) suited, and where size and weight were defining requirements. Several vehicle concepts were created, assessed, and either set aside or carried forward for further development. This coherent design and development process has been ongoing for over seven years. Seven years of design effort aimed at a single family of armour – this is a duration of design effort not seen since the days of the Establishments.
The effect the closures the Establishment had on UK defence equipment design was fundamental. The MOD assumed industry would perform all the work previously done by the Establishments, but cheaper! Of course, it didn’t. Industry is not a charity; unless there’s high probability of a good return on its investment, it does nothing. Without a cast-iron contract, or a winnable competition for one, or at least a clear indication from MOD that they have a clearly defined requirement for a specific capability, there will be no design effort in industry. And as soon as the opportunity expires all design effort stops. Dead. There should be no surprise that since the 1990’s, nearly every armour bid has been based upon previously fielded products minimally modified to tick the latest requirement boxes, or on products imported from afar, developed on their own nation’s taxpayers’ money.
This is perfectly summarised in one simple quote from William Suttie’s book ‘The Tank Factory’, where he is looking back at the 1920s.
“The decision to focus tank design in industry and run down the experienced and innovative Department of Tank Design (DTD) was a significant factor that resulted in Britain becoming a backwater in tank design until the Chertsey Establishment was established.”
Clearly, that was a lesson not learned.
In this modern environment, the sustained focus of design effort is a rarity and has delivered not so much a set of vehicles, as a design system comprising a set of subsystems and components that by use in different configurations permit rapid development of role-specific vehicle types. The designs resulting from this methodology have been created and developed despite there being no MOD procurement project, formal requirement or funded study.
These are simple honest vehicles designed from the inside out to be effective, maintainable and achievable, but just as important is the design process that produced them.
AEC Family of Light Armour
While it has been the norm for the Armed Forces to do the best with the kit which is available, this has at times made tasks more difficult, less effective or in some cases much more dangerous. Gaps in capability place additional strain on the serving soldiers as they wrestle with equipment that is not really the right tool for the job. What is needed is a wider range of useful tools in the Army’s toolbox, so that the difficult task of the soldier can be made as easy as possible.
The most obvious gap in UK equipment is precisely the space that has been occupied by CVR(T), and FV600 before that, and the likes of the Daimler, Coventry, and Staghound armoured cars before that. Considering the age of FV432 Bulldog and M270 MLRS, ongoing concerns over Panther protection, and the mobility of the Mastiff family, there is a broad spectrum of light to medium armour that might be seen as also in need of replacement. It appears the US Army has determined it to has a similar need for such armour (as reported here: https://www.army.mil/article/184597/).
The vehicles broadly align within the earliest FRES framework; C-130 transportable combat armour fulfilling many of the defined FRES roles. But before embarking on a design, their purpose had to be adequately defined. As one of the VERDI-2 trials operators (LCoH Bright) stated at the end of its trial:
“The main question to be answered before TRACER comes off the drawing board is what is the main role of recce? What does it need to do, collect information or destroy enemy light armour or both?”
The first task faced by any armoured vehicle designer and user is to understand the role; to scope out something like a Cardinal Points Specification of perhaps half a dozen defining characteristics the design needs to have. Without such a CPS the created armoured vehicle may not fit comfortably into any roles – a square peg looking for any vaguely square-shaped round hole into which it can be forced.
Once each role had its defined purpose, a brief study was carried out to investigate the problem space, including reviews of the strengths and weaknesses of earlier vehicles to pick out valuable features to carry forward to new designs. Ever since the invention of the tank, armoured vehicle designers have come up with very clever solutions to problems which are as relevant now as they ever were. Incorporating these, together with modern systems and approaches is in no way outdated thinking; the external shape of the new designs merely reflects the packaging of the necessary subsystems and human factors, taking those earlier smart solutions which have been brought up to date into account.
There may be raised eyebrows at the imposed C-130 transportability constraint given that the UK now has A400M but there are sound reasons to work with this constraint. Firstly the 9ft by 9ft gauge and 18t weight limit are entirely appropriate for a family of vehicles to replace CVR(T) and other similar light armoured vehicles. Secondly, while the UK has A400M many of our allies do not, and the flexibility of deploying as part of an allies force seemed worth retaining. Thirdly, complying with C-130 gauge also makes rail and road transport much easier, ensures slick RO-RO operations, and keeps the vehicles down to road vehicle bulk such that few routes would be impassable using extant infrastructure. Finally, holding to C-130 constraints maximises export potential which would be of value to UK PLC.
The counter-argument most often pitched at this is that in the contemporary operating environment, light armour of such compact form cannot meet protection levels necessary to survive the most likely threats. This would be a valid argument if the entire fleet of armour was to be changed to sub-20t vehicles. but the Army will still have its 70t MBT’s, 38t Ajax, 30t+ upgraded Warrior and MIV, which is likely to be a 35t vehicle.
If threats are so severe, then field the kit appropriate but accept the limitations they bring; the restrictions on routes, the greater logistic tail, the reduction in stealth (visual and IR but particularly noise). On the other hand, where rapid reaction and get-to-anywhere mobility are key, using a light small mobility focused armour capability has its advantages.
Different tools for different jobs.
Low weight does not necessarily mean paper-thin protection. These smaller vehicles have been designed with a thick and heavy hide but due to smaller surface areas, the weight of equivalent protection armour is less than would be seen on larger armoured vehicles. There are also some very interesting new developments in passive and reactive forms of protection, and many active forms of protection now being marketed. Clearly, cost is key as in all projects, but this points towards better than expected protection in smaller and lighter platforms.
Those who follow TD’s daily feed of defence related snippets will recall this comment: “Start with a common engine, wheels, tyres, transmission & other bits, then, AND ONLY THEN, build vehicles around them. Systems thinking.” Those who cut their teeth in the UK defence industry of the last century have always sought to use common components and subsystems, a discipline that the Government Defence Establishments promoted, encouraged and sometimes enforced. No surprise then that exactly this approach has been followed with the vehicle concepts described here.
This graphic shows each current vehicle type drawn to the same scale; it is not exhaustive or definitive, for example, no armoured JCB’s nor Command or Engineer or Repair/Recovery Variants of all the types depicted, but it does indicate the broad and varied nature of UK armoured vehicles.
Some of the armour is very new, some are ages old, some have aged well and others badly. Many have been purchased as Urgent Operational Requirements when existing fleet shortfalls were identified and some of these may not be retained in service in the medium term. What is quite plain to see is that there are a lot of different types, each filling a niche role, all needing their unique equipment care and REME support to keep working. That is a lot of different vehicles with different spares requirements and different maintenance procedures.
Shown below is a brief outline of the vehicles, their purpose and some of the development rationale as the process evolved. They are each valid Light Armour solutions as they stand, but it should be understood that they also serve as examples of the wide variety of armour that the design approach can deliver. They may be viewed as vehicle proposals or equally as a basis for further development. They did not come about all at once but progressed over the development period in response to user feedback and other inputs.
The 3D images are taken from CAD where the vehicles have been modelled. The CAD models are not complete production-ready designs but do serve as packaging exercises and allow some degree of human factor and maintenance assessment.
Role: Fast Light Armoured Fire Support; Reconnaissance Vehicle
Design: The initial concept was nothing more ambitious than a low profile hull on which either Ajax or Warrior CSP turrets could be mounted to provide obvious commonality and support advantages whilst also providing a lighter lower-profile fighting vehicle than an IFV. Not as easy a task as imagined, modern turrets are huge compared to those of years ago; a function of larger guns, elaborate feed systems, a lot of electronics to house, the requirement to accommodate physically larger soldiers and the space demands of body armour and wearable personal technology.
There has apparently been a loss of focus on designing armour to the minimal possible dimensions over the years. This may be a simple consequence of moving to CAD – if the design only exists in the virtual world it’s hard to grasp the reality of internal space. There is also a significant reduction in the rate of new projects compared to previous decades, meaning engineers are just not using their skills often enough to gain the all-important knowledge that translates to experience and technical intuition. There is a school of thought that use of automated design tools in place of experienced designers will make better products, but this is far from proven.
For a combination of some or all of the above, Ajax and Warrior CSP turrets are large. During the evolution of the design process it became clear they could not form the basis for a CVR(T) sized vehicle and in addition, their asymmetric width creates issues on small vehicles. After a good deal of concentrated options assessment, a configuration was found that created a balanced vehicle which worked using either of these British Army turrets or either of the two BAE Systems proposed Warrior CSP and CV90 FRES turrets.
This vehicle was named Raven, and for the purposes of illustration, the third-party turret with which it has been fitted is the BAE Warrior CSP turret, selected before the MOD decision was made to buy Lockheed Martin turrets for Ajax and Warrior CSP.
There are some unusual design decisions embedded in the hull design which significantly improves personnel protection without adding weight. This vehicle tips the scales at approximately 14t. As might be expected, it has a crew of three, but perhaps not as expected it also has a high power to weight ratio giving very lively performance. In subsequent reviews, serving British Army representatives voiced concerns and reservations over some of the more radical technical choices involved in the hull design.
Role: Armoured Personnel Carrier
Design: The low profile Raven hull had its roof plate raised to create a personnel carrier. The resulting vehicle, called Rǽde, has similar internal volume to the Alvis Stormer APC. But where that vehicle was defined as 2 crew plus 10 dismounts, using the 97th percentile male soldier anthropometric model that is now demanded, reduces the capacity to 5 dismounts.
The current Def Stan requirement is that vehicle seating must be separate and well defined with restraints and supports, and where possible arranged facing fore/aft. If all the non-mandatory guidance is followed, when there is a seating capacity for five, five is all that can be carried. Older military personnel carriers would be fitted with benches or close-coupled flat-squabbed seating facing side on. While there would be a nominal seating capacity the seating arrangement could take more at a crush in emergency situations. Following all Human Factors guidance has implications that must be understood. In the AEC designs for Armoured Personnel Carriers, the seating for dismounts is blast-attenuating but side-facing, and while the seats are individual and shaped, they are close enough to their neighbours to act as a bench when necessary.
The Rǽde APC CAD model is not yet complete
Role: Close Combat Support; Assault Gun
Design: With a fixed forward firing 25mm Oerlikon KBA or CTA40 and two Selex Enforcer RWS the Ram is designed for close assault in urban and semi-urban terrain. With one RWS the opposition may approach if it is focused elsewhere, with two RWS the probability that neither are about to sweep for threats is small. To aim the hull gun the vehicle must be aimed much like the S-tank, and like the S-tank the hull attitude can be adjusted in this case by air-suspension units. The flanks are designed to support heavy anti-IED/RPG slab armour, making this vehicle both heavy and wide.
Ram has not yet been transferred into CAD.
Role: Protected Cargo Vehicle
Design: In a complete change of direction, there was a request to investigate if the technology of the tracked vehicles above could be re-engineered into a wheeled chassis, specifically, in this case, a chassis for an existing armoured cab, to be configured as a drop-side cargo truck.
The exercise proved successful and resulted in a cargo carrier of modest size and payload capacities between 8t and 11t and room for six NATO standard pallets on its conventional drop-side load deck.
At a late stage, the Design Authority for the cab decided it was not to be used. An alternative AEC cab was created on the same footprint and with the same mounting interface to suit the chassis. The cargo deck and dropsides were modelled on the excellent Marshalls products used on current British Army MAN/Rheinmetall cargo vehicles.
Whilst the suspension and general layout meet the requirement, at between 6.5t and 8t per axle it was too demanding on available technology. The axle rating was reduced to 3.5t per axle for all other wheeled vehicles, making these lighter vehicles feasible within current technology but the geometry and configuration of the suspension remain the same.
A note about this geometry; a request was made to the designer of Jackal and he kindly defined the trigonometry of the suspension. The suppleness of wheel movement will be the equal of Jackal but at 3.5t the axle loading is less and the tyre width greater which allied to high power-weight ratio makes the fully armoured vehicles’ theoretical mobility considerably better than the impressive Jackal
Role: Autonomous Engagement Capability; Armoured Car
Design: The first of the wheeled vehicles using this 3.5t axle loading was perhaps an odd choice. The lack in the UK Order of Battle of high-speed high mobility firepower capable of long distance transits and being able to counter a broad spectrum of threats seemed to be a capability gap worth filling.
The four possible UK turrets (one each for FRES and Warrior CSP from BAE Systems and Lockheed Martin UK) did not fit well on a vehicle designed to be small and mobile, not only because of their size and weight but also because the turret basket size did not suit this vehicle’s narrow V-hull. A more comprehensive selection of firepower was also required. A new remote turret was designed, armed with the CTA40 and with Anti-Aircraft and Anti-Tank Guided Weapons installed conformally. The turret also has an elevating sight – it only rises a few feet, but as one RAC Major commented, he had found standing on the turret top with a pair of binos a very effective way of seeing without being seen; he didn’t see the limited elevation as a handicap. The hull has room for just two crew, but then the gun has its autoloader and the missiles are in essence ready-rounds, and the 7.62mm coax was given a large ammo can to use, so much of the gunnery effort was taken care of by machinery and advance vehicle preparation. The turret was set on an 8×8 hull of low profile and of a deep V profile in which the crew operated, sat in a well-protected citadel using the array of electronic vision options for driving targeting and situational awareness.
A point to consider here is that LCoH Bright at the conclusion of the VERDI-2 trial stated the following:
“The trial on Salisbury Plain was a success in as much as it proved a two-man crew can operate effectively for 48 hours in a closed down environment, and it opened our eyes to what is available to the recce soldier of tomorrow […but…] it must be smaller and faster.”
The Ræcc vehicle concept, like VERDI, is a two-man vehicle, with electronic vision and a remote turret, but packaged small enough to fit C-130 and just possibly light enough for CH-47 lift and has mobility and speed in Jackal’s class. That’s all LCoH Bright’s wishes fulfilled.
It was presented to a group of the Army that has a remit to embrace and assess new developments. But where Raven raised some concerns under review of the User group, Ræcc raised considerable objections. The reliance upon electronic vision, no ability to get the commander head-out with a clear sight of all sides of the vehicle, difficulties with misfires and ammunition feed stoppages and on and on.
So despite the outcome of the VERDI-2 trial, when offered just what that trials team recommended it was the User that rejected unmanned turrets and solely electronic vision. Quite disappointing, but the point of the AEC design approach is that the same building blocks may be moved and recombined with a high degree of configuration flexibility, so the rejection of one particular vehicle configuration does not mean a start from scratch.
A redesign then…
Role: Autonomous Engagement Capability; Armoured Car
Design: Raccoon is still an 8×8 but now with one-man turret.
To accommodate the one man, the turret is physically larger and has a reduced number of missiles. And of course, it now has a basket that occupies much of the hull. The hull too needed redesign, with effort upon retaining some of the crew protection mechanisms employed in the earlier Ræcc hull. It grew a little taller, the turret moved further back.
It is not as compact as Ræcc, but one of the opportunities the redesign brought was the provision of protected missile stowage for two of each GW type, armoured both from the outside world and from the crew citadel within.
Role: Reconnaissance Vehicle
Design: The turret of Raccoon, complete with both natures of guided weapons, is still more compact than the Ajax and Warrior CSP turrets. The next task was to see how much smaller the tracked hull could get if this one-man turret was to be used. The hull width reduced as the basket is a smaller diameter; the L/C ratio that defines tracked vehicle steering behaviour allowed a shorter run of track on the ground as the vehicle was narrower, there was (just) enough room to get two crew, driver and gunner, side by side in the hull and room for the engine bay behind the turret basket.
This compact vehicle called Rapier-C ended up very nearly CVR(T) scale.
Rapier-C is a tracked vehicle as narrow as Scimitar (if track guards are omitted) and a few percent longer and taller, with a crew of three, and with CTA40, 7.62 coax, ATGW, Anti-Aircraft GW and an elevating sensor. It has low ground pressure within 10% of that of Scimitar and a very high power to weight ratio that provides astonishing performance. With removal of track guards, antennas and the upper EO/IR sensor, it fits into an ISO container.
It is perhaps worth pausing here to compare and contrast with Ajax. Many will not have seen Ajax in the metal and will base an idea of scale upon photographs. Face to face, it really is imposingly large as are most new armoured vehicles, but for those who remember the compact dimensions of Scorpion/Scimitar/Sabre, this is a real step change. To help appreciate the size difference in absolute terms, the image below provides a comparison, behind Scimitar the blue coloured vehicle is Rapier-C, the pink outline is Ajax. Each to scale
There is no doubt that once in service, Ajax will be a competent vehicle and there will be situations in which it will be the ideal fighting vehicle to use. Would these be situations where similarly armed similar weight Warrior CSP couldn’t be used with similar success? Or similarly armed similar size and weight MIV? Or even Challenger 2 which is similar in width and height and has only 25% greater ground pressure under its tracks?
Possibly, possibly not, but it is a fair bet these other vehicles could be more readily substituted for a missing Ajax far better than an Ajax could be substituted for a missing Scimitar in situations ideally suited to the CVR(T) capability
Role: Reconnaissance Vehicle
Design: A predecessor to Rapier-C, Rapier-A was a concept using the remote turret of Ræcc complete with CTA40, coax, SHORAD and ATGW and its elevating surveillance sensor, offering better personnel protection than Rapier-C in a smaller package yet, but at the expense of Mk1 eyeball direct vision – a proper VERDI-2 capability in a Scorpion sized vehicle – but currently shelved due to the User rejection of reliance upon remote electronic interaction with the outside world.
Role: Fast Scout and Liaison
Design: Following the FCLV debacle and the continuing run of rumour and disquiet that Panther may not suit the role for which it was procured, and in order to see how compact a vehicle the standard wheeled driveline and suspension set-up would support, a vehicle along the lines of Ferret was constructed.
This was Raðe – a two or three man vehicle, rear-engined. Originally penned to take the Thales (ex-Helio) FVT800 turret, it seems Thales has withdrawn this. So a similar turret fitted with .50 cal and a 7.62mm chain gun was created. With the one-man turret there is only room for the driver sat ahead of the basket front & centre; with a remote weapon station, two personnel would easily be accommodated behind the driver. Two axles hence 7t all-up mass, overall dimensions not dissimilar to CVR(T) but obviously with greater ground clearance.
For comparison, this is not of Ferret scale. The reason is simple – there is no way a vehicle of Ferret size could accommodate two 97th percentile soldiers, let alone the three that this vehicle could accommodate. Raðe is similar in dimensions to the Coventry Armoured Car, and both wider and taller than CVR(W) Fox
Role: Civil Order Policing; Military Utility
Design: Using Raðe as a starting point, a Utility Variant was drawn up called Rǽs. In order to create a usable rear access cargo compartment, the engine bay was moved to the side just in front of the rear wheel. The wheelbase had to extend to make the space meaning this is the only wheeled vehicle that fails to meet defined HMLC criteria, due to break-over angle. While the cargo space is limited the vehicle retains the same armour protection as all other vehicles. The siting of the engine bay means there is no room for a turret basket so RWS or simple head-out machine gun would be the self-protection measures. The vehicle was designed to adopt roles that FV1611 (Humber Pig) would have undertaken; riot control and civil order policing.
Rǽs has yet to be modelled in CAD.
Role: Autonomous Engagement Capability; Armoured Car
Design: At a briefing to British Army personnel new to the AEC concepts, it was suggested the mix of ATGW and anti-aircraft guided missiles on Raccoon was flawed, not because they were technically incompatible but because the level of training to get one crew competent on both missile types was unlikely to be provided. Better to fit just ATGW and a gun, they said. Another redesign then.
Removing one of the missile systems allowed the turret profile to reduce back to that of the unmanned turret whilst still having room for the one crewmember within. There followed effort to redesign the first Ræcc hull to suit this smaller one-man turret, which has worked although some of the benefits of the earlier design are lost, notably in relation to hull crew protection. The end result was a vehicle looking remarkably similar to Ræcc and using the same subsystems driveline etc, but having a completely different internal configuration and hull structure. This is called Ræcc-R, it represents a moderately compact armoured car the likes of which were common Army equipment until the 1970s, armed with the Army’s favourite medium calibre gun, CTA40, and ATGW. Vehicle performance on a par with the typical Golf TDi.
Role: Reconnaissance Vehicle
Design: The Ræcc-R turret (or a close derivative of it) offered itself as a way to revive the remote turret Rapier-A recce vehicle. Keeping to a vehicle crew of two, driver in the hull and vehicle commander either in the optionally-manned turret or beside the driver, the vehicle remains as compact as Rapier-A and maintains that vehicle’s crew protection advantages, but now, of course, allows the commander to operate head-out in the turret. Use of this turret does, of course, mean the absence of anti-aircraft GW but there remains the 40mm CTA gun, the coax 7.62mm chain gun and two ATGW in a conformal silo, as well as an elevating sensor.
A note about sensors here; the preference is to use spherical units as they maintain a constant silhouette as they pan and tilt which helps reduce their detection. But fully gyro-stabilised sensor balls are eye wateringly expensive – each one way more than the cost of the base vehicle – so a more cost effective adequate surveillance and targeting sensor solution has to be found. Assuming an affordable optics solution is found the vehicle design is sound. Still work in progress, this is Rapier-AC
Role: Multi-Role Rapid Reaction
Design: This was the only vehicle in the set that was designed from the outset as a multi-role concept based upon an automotive V-hull and a clearly defined and separate ‘mission module’ for the crew and the mission equipment. However this is not one vehicle structural design to which role equipment is bolted. Each role requires a separate design of mission module and to support the diverse needs of the role the V-hull may differ in length and number of axles. The intent is that each vehicle would leave the factory already configured to role and that any reconfiguration to different role would require return to factory or at least to third-line workshops.
The design of Ox owes much to FV603 Saracen, a fine design in concept if a little flawed in execution. Not surprisingly, when creating a wheeled V-hulled APC with engine bay in the nose and crew compartment behind, the result looks like Saracen. No bad thing; the design was well considered. The V-hull holds a constant profile the full length of the vehicle and is the structure upon which all the driveline is mounted. The mission module sockets into this V-hull behind the engine bay and may take a variety of forms, although each so far considered has a similar driver station.
The following graphic shows some of the options:
Several variants of the Ox family have been constructed within CAD, showing the variations in V-hull length, number of axles and variations in mission module.
Role: Fast Light Armoured Fire Support
Design: Earlier this year the Raven hull design was reviewed in conjunction with the Rheinmetall Lance and Leonardo Hitfist 30P turrets; with these more compact units the hull could be reconfigured and some of the radical elements engineered out. This much more conventional reworked design has been named Raven-R. Apart from the obviously different turret, it has a forward engine bay beside the driver and a rear escape/resupply hatch, but otherwise shares the original Raven hull’s components, performance and vehicle role.
What it loses is the unconventional crew protection advantage of the original Raven hull, but its entirely conventional layout would not raise any of the concerns voiced against the original design. While the vehicle could be constructed at the same weight as Raven it would be expected that extra blast protection measures would be demanded to offset the higher risk configuration. This would, of course, impact vehicle weight.
While the use of a turret not fitted with CTA40 may prevent UK MOD from considering the vehicle, use of this hull with either Lockheed Martin UK turrets, Ajax or Warrior CSP, by current assessments is inappropriate due to the long forward overhang in front of the ring which pushes the turret axis far back down the hull. There would also seem to be significant width of turret to the right of the centreline in each of the Lockheed Martin designs which makes fitment to these narrow vehicles far from ideal. It is possible the information available in the public domain is misleading, or indeed has been misunderstood, but until further information is published it seems wise to look at narrower turrets such as Lance or Hitfist.
An outstanding task is to look at the options for fitting turrets with larger calibre guns. Both Leonardo and CMI/Cockerill have 105mm or 120mm turrets that may fit. It would be better if a high-pressure gun option fitted such that MBT armour might be challenged. Initial assessments suggest the turret baskets are too broad for either wheeled or tracked vehicles of this size; the rings are similarly broad but could be accommodated. It is a shame there are apparently no decent guns being made or marketed in the 60mm to 75mm range – such a calibre would suit vehicles of this size well.
AEC Family Values
Every one of the above vehicles remains within C-130 gauge for air transport; every one fits within the UK’s most restrictive W6 rail gauge (for some of the taller vehicles that requires use of Warwell wagons but many could sit on typical flat container wagons). The 4×4 scout Raðe, the utility Rǽs and each of the Rapier recce vehicles could be moved inside 20ft ISO containers with minimal preparation. These are designed to be easy to deploy in numbers to wherever they are needed. Tracked vehicle ground pressure is just 10% higher than CVR(T) at its initial 9t Gross Vehicle Weight, 60% of that of Warrior and 40% of Challenger 2. Tracked vehicle acceleration would leave most GTIs behind and wheeled vehicle acceleration matches typical family cars, this performance a result of ensuring enough torque to sustain speed on a 40⁰ climb gradient if ever wheels or track could keep traction. High levels of redundancy within the driveline would offer resilience against damage or component failure.
They are not the world’s most protected armour; they would undoubtedly need to be fitted with RPG protection (Tarian nets would be favourite) and would benefit from being fitted with ABBS VGAM blast protection system; they are not spacious; the turreted vehicles are not armed with MBT guns. Being armoured they are not as light as soft-skinned vehicles and transport under CH-47 would be a challenge for most and impossible for the larger types, but then compromises must be made.
These are simply nimble, small, highly mobile, and reasonably well protected useful vehicles.
Underlying all the designs is a firm principle to engineer the different vehicle types from common components – common engines and drive systems, common air filtration systems, common instrumentation and controls, for the wheeled vehicles common suspension, steering, wheels and tyres, for the tracked vehicles common suspension, idlers, roadwheels and track type – with a sharp focus on simple affordability.
Rather than designing a single complex all-encompassing multi-role vehicle, individual simpler designs focused on their prime role have been created, but each based upon the same subsystems and components resulting in very high commonality to ease support burden. As each vehicle type is freed from the burden of meeting the needs of many different roles, they become more compact, lighter, and affordable.
Affordability improves if more types are brought into service as the common support brings benefits in maintenance training, spares inventory, diagnostic aids, even maintainer currency. This can perhaps best be illustrated by repeating the earlier graphic of the breadth of UK armour, this time with the above described AEC vehicles replacing current incumbents:
The shading behind the vehicles shows common support. Consider what such broad common support means; much more accurate spares scaling, streamlined maintainer training, much-improved maintainer currency, leading to greater maintenance efficiency, lower maintenance cost, and greater vehicle availability. Common support makes sense.
One family of many different forms, large and small, tracked and wheeled, this is the sort of joined-up thinking the Army and the MOD needs.
These designs are by no means the limit of possibilities. Given current technology, assume a wheeled vehicle maximum weight of 17t or so, for tracked vehicles that may be increased to somewhere near 28t. This is due to driveline capability, the lower maximum weight for wheeled vehicles down to the larger diameter of wheel/tyre which demands greater torque to achieve acceptable performance. Note though that the designs undertaken for tracked vehicles have been substantially less than 20t, mostly because this is where the projected UK capability is weak but also because of the self-imposed C-130 transportability constraint. There is no reason why lighter heliportable vehicles could not be designed as long as lower protection was accepted.
There are challenges not yet met for amphibious operation, articulation, integration of major hydraulic powered systems (cranes, diggers, winches, lifts) and high recoil force systems (large bore mortar, SP gun), but there are no fundamental reasons why these should be more difficult than in any other armoured vehicle design.
An Echo from the Past
Before Ajax, FRES. MRAV and TRACER, there was the Future Family of Light Armoured Vehicles, FFLAV. Here is what the Alvis team offered for FFLAV:
One view of this offering is to see it in the light of where the British Army is now. In place of VBL, the UK has Panther FCLV. In place of CV90, we have Ajax, remembering, of course, CV90 was the other FRES-SV contender. In place of BMR, we will have MIV.
Was FFLAV visionary? Well, probably not, but it was blindingly obvious good honest robust common sense. So blindingly obvious that thirty years down the line, the original FFLAV solution is roughly what the Army has selected.
There are differences though. Ajax, as delivered, is far heavier than the 1990 FFLAV version of CV90. MIV is likely to be far heavier and bigger than BMR. And of course where the FFLAV proposal focused on upgraded and developed CVR(T) and Stormer vehicles, these are now due to retire from UK service.
Taking an alternative view, compare the FFLAV offerings to the AEC family described in the text above. VBL roles are covered by Raðe scout and Rǽs utility. BMR is covered in exactly the same weight range by the various versions of Ox. Stormer and Rǽde APCs are direct equivalents. Scorpion is matched by Rapier. And while CV90 is heavier than the Raven concepts, there is no technical reason why the Raven driveline couldn’t be used on tracked vehicles up to 28t. And in addition to covering the FFLAV bases there are also the Ræcc and Raccoon armoured cars, and Ram assault gun, and providing driveline technology develops there is the Rival armoured logistics truck too. And there is VERDI-2 envisioned capability in Ræcc Raccoon and Rapier. And the design approach could deliver many more types of light armour for additional roles too.
The AEC family of armoured vehicles aligns exceptionally well to the FFLAV vision. Except for the one attribute that FFLAV couldn’t deliver – common support throughout the entire range.
Options for Advancing the Project
The original design, Raven, was first briefed to the appropriate MOD desk officer late in 2010. Several other briefings have been made since as the text above notes, and the designs have been changed where advice from Users was offered.
The most challenging aspect has been the MoD’s procurement process. Although the MoD has a number of initiatives in certain product sectors for SME engagement, major vehicle projects tend to be placed only with the larger and established companies. It was suggested at one briefing by a DSTL engineer that would be a good idea to generate a prototype of one of the AEC vehicles to test the concepts, with a view to jointly creating a DSTL owned design for industry to bid to build (very much as Establishments worked) but he failed to convince his colleagues.
The UK still has a broad spectrum of excellent companies, each expert in their domains, despite the low volume market for military equipment. And at all levels too, from stock materials through welding, casting, forging, moulding and fabrication, on through component manufacturers and integrators of specific military systems, to platform level assembly and integration plants to vehicle designers and manufacturers, to complete military product suppliers such as the various divisions of BAE.
The UK has all of this onshore and it would be perfectly feasible to complete the process through to manufacture within the UK.
What this means is that there is a broad range of opportunities for how to turn the AEC designs into fielded combat equipment. The following options are of course predicated on the Authority and the Army deciding they want this sort of capability.
- Government buys the designs outright and either completes the development of the designs in-house and raises a competitive procurement for primes or manufacturers to bid for the production contract, or raises a competitive procurement for a development and production contract. This would be similar to the process used on Establishment designed products. The Government having purchased the designs owns the IP and may change production supplier as needed. The support contract need not rest with the manufacturer and might be competed separately. This gives the Authority the greatest contractual freedom over the course of the equipment service life.
- Government sets up a collaborative design team, containing Authority, Government Scientist, Army and Industry personnel all performing tasks necessary for the designs to reach maturity. Somewhat similar to recreating the Establishments function, except with the use of Industry players in completing the designs the IP would need to be shared or purchased. If the latter, this would need declaring at the start of the project so that contributing businesses knew from the outset that whatever they embody in the design would cease to be their IP at the end.
- Industry adopts the designs either by collaborative development or simply by purchase of the designs by a company of the stature the Authority is prepared to contract, thereafter developing the designs under its own R&D budget. The resulting vehicles would be COTS for future competitive procurements; should the Authority choose to buy them, the IP would remain firmly within the company’s ownership.
Each of these options has advantages and disadvantages but it is probably fair to say the preferred MoD method of standard Competitive Procurement adds significant bid and compliance costs, takes the longest and puts the greatest distance between User and Designer, often allowing User input into the design only at formal infrequent reviews and measuring every User suggested improvement against the contracted Requirement. It also almost guarantees no commonality either to in-service materiel or to other projects in the procurement cycle.
It is hoped that reforms at DE&S may provide some future flexibility that reduces bid costs and allows a more integrated and collaborative approach.
Shorter concept to ‘out of service’ cycles would also have significant competitive and industrial advantages
The AEC concept vehicles described above have all been designed using current technology and were deliberately designed to be as affordable as the technology allows. The Army could benefit from an increase of inventory – more tools in the toolbox – so designing the most affordable solution is in the MoD’s interest. As such they would be ideal candidates for a streamlined low-cost procurement, where the simple adequacy of the vehicles would be matched by a simple and adequate acquisition processes based on free open communication and common teamwork.
It could be revolutionary.