Coalition IAMD operating concepts
Operating concepts (also known as ‘operational concepts’) are “generic scheme[s] of maneuver” that describe, at a theatre level, how military assets will be used to prevail in a particular type of engagement. The Air-Land Battle concept employed by the United States in the 1980s, for example, was structured around conflicts with a quantitatively superior opponent, and emphasised close-air support to front-line troops coupled with strikes behind enemy lines to degrade the enemy’s front-line offensive. In the IAMD context, operating concepts are principally concerned with the placement and integration of networks of sensors and shooters, and their ROEs with red team assets in a given scenario.
Following the procedure detailed in the previous section, the TTX generated 16 IAMD architectures involving JASTU assets positioned to defend against various Chinese air and missile attacks under various constraints. The authors analysed these architectures to identify recurring patterns of JASTU operational coordination, which were then formalised into a series of Coalition IAMD operating concepts. Below, we detail the two operating concepts that emerged from the TTX: (1) Latent Link, and (2) Long Sense/Short Defence.
Latent Link
IAMD ‘battle management’ involves the networking of sensors and shooters within an area of operations. Instead of clusters of sensors and shooters operating in isolation, battle management connects all sensors and shooters across the entire theatre, effectively allowing them to ‘talk to eachother.’
At a national level, IAMD battle management offers several advantages. Shooter access to more track data (i.e. from multiple sensors) can improve battlefield awareness, early warning, cueing, and the fidelity of tracks, improving shooter performance. Having multiple, networked sensors closes gaps in coverage and provides redundancy against the failure or loss of individual sensors. And integrating shooters supports inventory management as command can more optimally assign its full range of effectors against individual targets. This theoretically reduces the incidence of: commands uneconomically expending high-cost effectors on low-value targets; blue overkill, where multiple effectors are unnecessarily assigned to the same target; or blue-on-blue incidents in congested areas of operation.
Within the TTX, the demand for battle management at the level of individual jurisdictions was strong: more in-game points were expended on battle management than for any other capability. Interestingly, players also explored how jurisdiction-level battle management systems could be integrated across JASTU. Players reasoned that networking jurisdiction-level battle management systems in this way would supercharge the abovementioned advantages of battle management (inventory management, early warning, etc.), i.e. by increasing the supply and geographic distribution of sensors and shooters.
These discussions centred on integrating a specific function of battle management, namely track sharing. Overall, there was consistent demand for cross-jurisdictionally integrated track sharing. That is, players consistently recommended networking all in-theatre coalition assets (i.e. across JASTU) such that all sensors could feed track data to all shooters (i.e. both within and across partners), whether through the procurement and integration of dedicated battle management systems, or through Link 16, or both. In Scenario 1, for example, all teams that were not restricted from doing so incorporated this cross-partner track sharing capability into their architectures.
As the vignettes progressed and became more complex, the demand for cross-partner track sharing only grew stronger. Even facing financial constraints and higher volumes of air and missile threats that created pressures to procure more effectors, teams consistently prioritised track sharing through the procurement and cross-partner integration of dedicated battle management systems (see, for example, Figure 2). Indeed, in team discussions, establishing such track-sharing arrangements was typically viewed as the ‘start point’ for architecture design. This demonstrated an operational emphasis on countering air and missile threats through improving the performance and effectiveness of existing in-theatre shooters, i.e. through cross-partner track sharing and the associated gains in tracking, targeting, redundancy, inventory management, cueing, and early warning.
FIGURE 2.
TEAM 1'S COALITION IAMD ARCHITECTURE FOR DEFENDING AGAINST AN ATTACK ON OKINAWA
Some in-theatre assets from the TTX were removed for readability.
Political considerations
When challenged on the political feasibility of sharing track data between JASTU militaries, players consistently judged that any political constraints on sharing tracks between JASTU would “disappear into the distance” in the context of a kinetic regional conflict. One participant, for example, posited that “once Japan has been attacked by the PLA, then I think they can change their policy to share information with [Taiwan],” with another participant responding that “I would suggest that Australia would do the same… once the missile firing starts, I think there would have to be a rethink about sharing.”
Unlike integrating fire control (i.e. one partner targeting and launching another’s effectors) — which players judged to be politically infeasible, even in the context of a shooting war in the Indo-Pacific — track sharing through cross-partner, integrated battle management would allow partners to retain ultimate decision-making authority over the use of their own shooters: what one player described as a “sovereign opportunity to use shared data.”
The above support for cross-partner track sharing comes with one major caveat, however: it is contingent upon the existence of, or imminent threat of kinetic conflict. Under pre-conflict conditions, there was less certainty that JASTU would have the political will to share track data. This is problematic as the procurement, testing, training, and policy development around cross-partner track sharing takes time, particularly when such track sharing spans multiple services and militaries. The dilemma left for policymakers is that, by the time the operational need for cross-partner track sharing becomes urgent (i.e. once the shooting starts), it may be too late to put the requisite systems and agreements in place.
One solution to this dilemma is to begin putting in place the requisite systems and agreements now, but in a deactivated, or ‘latent’ form. For example, JASTU might integrate their IAMD assets within battle management systems at the national level — for example with the US Integrated Battle Command System (IBCS) and the Australian Air6500 program — and develop now the data and communications protocols for these partner-level systems to talk to each other. When the shooting starts and politics change, links between these compatible, partner-level systems can be ‘switched on’ to activate coalition track sharing.
The above suggests a credible Coalition IAMD operating concept — which we label ‘Latent Link’ — in which JASTU establishes a cross-partner track sharing capability that is ‘inactive’ in peacetime but can be activated at the outset of a kinetic conflict. Latent Link presents a promising operating concept for JASTU Coalition IAMD in that it is both politically ‘cheap’ and operationally advantageous. It is politically cheap in that track sharing is not active in peacetime, and in that it does not require delegating or sharing fire control to or with other partners. And it is operationally advantageous in that it provides partners with improved inventory management, battlefield awareness, early warning, cueing, track fidelity, and sensor redundancy in wartime.
Requirements
There are two primary capability requirements for Latent Link. The first is the capability to share fire-quality track data between platforms and partners. A 2019 US Army test of IBCS, for example, demonstrated such a capability when it merged data from multiple US sensors (F-35s and PATRIOT, Sentinel, and TPS-59 Radar) and services (US Army, Air Force, and Marine Corps) to track two cruise missile surrogates that were successfully intercepted with PATRIOT Advanced Capability-2 (PAC-2) missiles. Australia’s Air6500 program is aiming for a similar capability through a ‘system-of-systems’ designed to connect “disparate ADF [Australian Defence Force] systems and platforms across all domains.” The second capability requirement is that track-sharing links between partners’ sensors and shooters are regulated such that they are, by default, inactive but can be rapidly activated in wartime.
Latent Link also requires developments in JASTU policy. First, to create demand for, and seize the opportunities of track sharing between platforms and partners, JASTU partners must align their IAMD operational planning around fully integrated sensors and shooters, rather than clusters of sensors and shooters operating in isolation. At the jurisdiction-level, this is already policy in the United States and Australia with IBCS and Air6500, respectively. And Japan, South Korea, and Taiwan are advancing comparable concepts in Japan Aerospace Defense Ground Environment (JADGE), Korea Air and Missile Defense (KAMD), and “T-Dome,” respectively. Second, JASTU partners must prioritise procurement of interoperable platforms. While legacy systems are likely to require ‘translators’ such as those provided by IBCS and Air6500, next-generation IAMD systems may be designed to seamlessly plug into these open architectures. Third, agreements between JASTU partners that preapprove track sharing in a conflict must be sought such that track sharing can be activated at the outset of conflict at a speed of relevance. Fourth, JASTU partners must build interoperability and experience working in cross-partner IAMD operations through joint exercises. And fifth, JASTU partners must establish their own policies regarding firing on tracks provided by partner militaries that take into account, for example, concerns around the comprehensiveness and fidelity of track data.
Long Sense/Short Defence
In constructing regional IAMD architectures, constraints on the forward deployment of assets often emerged. Players were heavily constrained in forward deploying ground-based assets on foreign territories, whether for legal or political reasons. And players judged that jurisdictions would be constrained in forward deploying assets that they would otherwise need to keep close to the homeland in case the conflict escalated, with one player remarking that “You can’t expect the Japanese or the Koreans to send their limited assets that far away from home, because there’s always going to be a threat that the home islands are going to be attacked.” This exposed a dilemma for players: while partners may seek to strengthen deterrence in the Indo-Pacific by contributing to coalition force structures, their ability to do so through forward deployments of IAMD assets would likely be constrained. Teams engaged this problem by establishing a division of labour between (1) point defence, performed by the partner under attack; and (2) long-range sensing, performed by coalition partners not under direct attack.
Point defence
In the IAMD architectures recommended by players, the partner whose territory was being attacked would typically take charge of ground-based deployments for point defence. This was judged to be the most politically expedient as it would sidestep the above mentioned constraints on the forward deployment of ground-based assets on foreign territories.
Importantly, to get on the right side of the cost curve re cost-per-engagement issues, teams typically included in the point defence role low-cost-per-engagement shooters that could engage high-volume, low-cost threats (drone swarms, etc.) at proportionate cost, for example stinger missile, missile and cannon SHORAD, and microwave and laser systems. This allowed high-end systems such as F-35s and air warfare destroyers to reserve their limited effectors for advanced cruise and ballistic missile threats targeting critical assets.
Scenario 1, for example, involved a Chinese drone and cruise missile attack on the Japanese Island of Yonaguni (Figure 1). It began with a massed Chinese drone strike that degraded local defences, leaving the island vulnerable to a follow-up barrage of air-, land-, and sea-launched cruise missiles. Players were quick to point out that relying only on in-theatre, high-end shooters such as the Chu-SAM, DDGs, and F-15 would rapidly exhaust interceptor stockpiles. This led discussions on defending Yonaguni to emphasise cost-effective SHORAD: “If you can handle the missiles or the drones coming in with a SHORAD system, then you’re not wasting AMRAAMs or SM6s or SM2s… This is important in this fight because you will run out in about six weeks. You’re going to run out of all of this stuff.”
Accordingly, teams consistently incorporated into their Scenario 1 point defence architectures ground-based, low-cost-per-engagement shooters on Yonaguni to counter the initial drone swarm and provide an additional layer of defence against the follow-up cruise missile strike. Team 1, for example, emplaced an M-SHORAD and microwave systems on Yonaguni Island (Figure 3). Doing so, it was reasoned, would keep the high-value, in-theatre assets, such as the Japanese Chu-SAM and F-15, safe and with sufficient inventory to respond to the follow-up cruise missile attack. When restricted from purchasing SHORAD assets, teams struggled to manage the drone swarm issue. Team 3, for example, was forced to reassign Chu-SAM and F-15 fires to the drones, which reduced the readiness and inventory of these high-end systems for managing the follow-up cruise missile attack.
FIGURE 3.
TEAM 1'S ARCHITECTURE TO DEFEND YONAGUNI, DEPLOYING LOW-COST-PER-ENGAGEMENT SHOOTERS IN A POINT DEFENCE ROLE WITH MOBILE COALITION SENSORS PROVIDING DEPTH
Long-range sensing
JASTU partners not being attacked directly prioritised long-range and mobile sensors and relays that could either support coalition forces from their home territories, or could be rapidly recalled to their home territories, such as AEW, HALE and MALE, and various unmanned systems. For players, the advantage of acquiring these systems was that they could contribute to coalition force structures at low political cost, both because they were based in or could be readily recalled to their home territories, and because sensing/relay was seen as less politically problematic than shooting.
In Scenario 1, for example, Team 1 recommended that South Korea, the United States, and Australia acquire mobile surveillance systems to circle Yonaguni, providing redundancy to the vulnerable ground-based sensors on the island (Figure 3). In another example involving a Chinese bomber-led attack on Darwin (Scenario 4), Team 2 recommended that Japan, South Korea, Taiwan, and the United States all procure and deploy to the South China Sea airborne sensors — including two long endurance/relay UASs and an autonomous battle management UAS with relay — to provide early warning and feed tracks on the incoming bombers to regional coalition assets (Figure 4). This was critical for focusing Australian combat air patrols, which would otherwise struggle in the north of the country given limited inventory and the massive distances that they need to cover. Thus, even though Japan, South Korea, Taiwan, and the United States did not directly engage Chinese bombers or deploy assets to Darwin, which players judged would be politically challenging or operationally disadvantageous in the scenario, they were able to strengthen Australia’s defence of Darwin through early warning and track sharing with mobile sensors.
The above suggests a credible Coalition IAMD operating concept — which we label ‘Long Sense/Short Defence’ — centring on two elements. The first is that the partner under attack focuses on point defence through a combination of high- and low-cost-per-engagement effectors. The second is that other JASTU partners support point defence through mobile and long-range sensing that provides redundancy and early warning to point defence sensors.
As with Latent Link, Long Sense/Short Defence presents a promising operating concept for JASTU Coalition IAMD in that it is both politically cheap and operationally advantageous. It is politically cheap in that it does not require engaging air and missile threats vectored for other partners, the emplacement of IAMD assets on foreign territories, delegating or sharing fire control to or with other partners, or the long-term deployment of IAMD assets beyond the homeland. And it is operationally advantageous in that it provides partners with cost-effective point defence; improved battlefield awareness, early warning, cueing, and track fidelity; and sensor redundancy and depth. Indeed, the demand for early warning and sensing in-depth will only increase as China ramps up production and deployment of hypersonics, the speed and flight altitude of which will require early detection and OTH sensing.
FIGURE 4.
TEAM 2'S ARCHITECTURE TO DEFEND DARWIN, WITH MOBILE AND LONG-RANGE COALITION SENSORS TRACKING INBOUND CHINESE BOMBERS
Some in-theatre assets from the TTX were removed for readability.
Requirements
As with Latent Link, Long Sense/Short Defence hinges on the ability of JASTU partners to share fire-quality track data between their respective sensors and shooters. Therefore, the capability and policy requirements for Latent Link also apply to the Long Sense/Short Defence operating concept. In addition to these base requirements, the JASTU partner responsible for point defence in a Long Sense/Short Defence posture (i.e. the force element most likely to be targeted) will require two broad capabilities. The first is the capability to absorb an opening salvo of high-volume, low-cost air and missile attacks, specifically through low-cost-per-engagement systems with high magazine depth. Lasers, microwaves, and canon-based SHORAD present compelling options, with cost-per-engagement theoretically as low as “pennies per shot.” The second is the ability to defend against those advanced threats vectored for high-value targets for which low-cost-per-engagement effectors might be ill-suited: hypersonics, submarine-launched ballistic missiles (SLBMs), etc. Here, partners will have a stronger strategic and economic case for utilising exquisite systems such as highly capable surface-to-air and air-to-air missiles (standard missiles, etc.) to intercept these threats.
Those JASTU partners not under direct attack but providing coalition long-range sensing support will require long-range and/or mobile sensing platforms, such as AEW aircraft, HALE UASs, and OTH radar installations that can feed early warning and track data on incoming threats to the point defence partner.
In terms of policy requirements, Long Sense partners must establish policies for pre-positioning and tasking long-range/mobile sensing assets for coalition vulnerabilities. Whereas Short Defence partners must establish ROEs that optimally assign high- versus low-cost-per-engagement effectors to a variety of threats. There will be multiple factors that bear on the economic assignment of effectors to threats, for example threat type, threat volume, threat target, interceptor inventories and supply lines, time-to-impact, and the political status of the conflict.
Lasers, microwaves, and canon-based SHORAD present compelling options, with cost-per-engagement theoretically as low as “pennies per shot.”Source: US Department of War