Tag Archives: featured

Developing an Assessment for the IO Environment in Afghanistan

You may be wondering what an article about Afghanistan is doing on a site about maritime security. Well, I found myself asking a very similar questions when, within six months of joining the U.S. Navy and graduating from Officer Candidate School (OCS) in Pensacola, FL, I found myself in a land-locked country serving on a Provincial Reconstruction Team (PRT) conducting counterinsurgency operations. The irony was not lost on me since I had joined very late in life (I was 35 when I went to OCS). The recruiter had said, “Join the Navy and see the world!” Little did I know we’d be starting in alphabetical order …

Meeting the requirements of an “individual augmentee” – (Fog a mirror? Check!) – and having just enough training to know how to spell “IO,” I arrived in Khost province in early 2008. I was fortunate to relieve a brilliant officer, Chris Weis, who had established a successful media and public diplomacy program and laid the groundwork for a number of future programs.

I decided that before setting out to win the “hearts and minds” of the local population, we needed to take stock of where we were and whether our efforts were achieving the effects we desired.

The goal of Information Operations (or “IO”) is to “influence, corrupt, disrupt, or usurp adversarial human and automated decision making while protecting our own.”[i] But how does one know whether the decision process, either human or automated, has actually been influenced in some way? We can assume or surmise that, based on the actions of the target of the IO campaign, some desired effect was achieved or not achieved. But how much of that was based on our IO campaign and how much on other factors, perhaps unknown even to us? We can also attempt to ask the target after the fact whether campaign activities influenced their decision making. But such opportunities might rarely arise in the midst of on-going operations. 

Commanders conducting counterinsurgency operations should have two primary IO targets: the insurgents and the local population. Retired U.S. Army officer John Nagl notes that “persuading the masses of people that the government is capable of providing essential services—and defeating the insurgents—is just as important” as enticing the insurgents to surrender and provide information on their comrades.[ii] A PRT is not charged with directly targeting insurgents. Instead, its mission is to build the capacity of the host government to provide governance, development, and these “essential services” for the local population.[iii]

Information Operations traditionally suffer from a lack of available metrics by which planners can assess their environment and measure the effectiveness of their programs. It may be impossible to show direct causation, or even correlation, between Information Operations and actual effects (i.e., did my influence program actually have its desired effect?). This often places IO practitioners at a distinct disadvantage when attempting to gain the confidence of unit commanders, who are tasked with allocating scarce battlefield resources and who are often skeptical of Information Operations as a whole.

Given these constraints it was clear that the PRT in Khost province, Afghanistan, needed a tool by which the leadership could benchmark current conditions and evaluate the information environment under which the population lived. We hoped that such a tool could help provide clues as to whether our IO (and the overall PRT) efforts were having the intended effects. As a result, we developed the Information Operations Environmental Assessment tool, which can be used and replicated at the unit level (battalion or less) by planners in order to establish an initial benchmark (where am I?) and measure progress toward achieving the IO program goals and objectives (where do I want to go?). 

Since my crude attempt was first published in 2009, the U.S. Institute of Peace (yes, there is such a thing) developed the metrics framework under the name “Measuring Progress in Conflict Environments” or “MPICE.” This project seeks to:

provide a comprehensive capability for measuring progress during stabilization and reconstruction operations for subsequent integrated interagency and intergovernmental use. MPICE enables policymakers to establish a baseline before intervention and track progress toward stability and, ultimately, self-sustaining peace. The intention is to contribute to establishing realistic goals, focusing government efforts strategically, integrating interagency activities, and enhancing the prospects for attaining an enduring peace. This metrics framework supports strategic and operational planning cycles.

No doubt the MPICE framework is far more useful today than my rudimentary attempt to capture measures of effect in 2008, but I hope in some small way others have found a useful starting point. As I learned firsthand, and as practitioners of naval and maritime professions know, what happens on land often draws in those focused on the sea. 

The author would like to thank Dr. Thomas H. Johnson and Barry Scott Zellen, both of the Naval Postgraduate School, for their professional mentorship and constructive advice, and for including my work in their book.

LT Robert “Jake” Bebber is an information warfare officer assigned to the staff of Commander, U.S. Cyber Command. He holds a Ph.D. in public policy from the University of Central Florida and lives with his wife, Dana and son, Vincent in Millersville, Maryland. The views expressed here are not those of the Department of Defense, the Navy or those of U.S. Cyber Command. He welcomes your comments at jbebber@gmail.com.

 


[i] Joint Publication 3-13 Information Operations, p. ix

[ii] Nagl, John A. Learning to Eat Soup With a Knife: Counterinsurgency Lessons from Malaya and Vietnam. Chicago: University of Chicago Press, 2002, p. 93.

[iii] Ibid.

Sea Control 22 – Behind the Curtain

seacontrolemblem(Download: Sea Control 22 – Behind the Curtain, the First.)

A. Denis Clift, former Naval Officer, president emeritus of the National Intelligence University, and Vice President for Operations of USNI, joins us to talk about his reflections on his time in the Antarctic, Cold War intelligence, life, and the United States Naval Institute. This is the first of a bi-monthly series that will be investigating his career during the Cold War.

We are available on Itunes, Stitcher Stream Radio, etc… Remeber to subscribe, leave a comment and a 5-star rating.

The Evolution of Air-Sea Battle

Just as history and past experiences have guided the People’s Republic of China (PRC) on a path towards the deployment of a robust anti-access/area-denial capability (A2/AD), Washington’s own historical narrative will guide its own counter response. Such a response, known as Air-Sea Battle (ASB), has gone through an important evolution–thanks mainly to an important and often times heated debate–over the last four years that many scholars and followers of this operational concept are quick to gloss over or are unaware of. Understanding such an evolution and tracking its progress is key not only for understanding ASB itself but also in monitoring how nations and non-state actors dependent on A2/AD might attempt to adapt or counter such efforts.

ASB: Core Foundations

American planners over the last several years have sought techniques to continue to deploy a superior conventional military capability in spite of growing A2/AD capabilities, retain the ability to mass forces and enter a combat zone decisively while controlling the global commons across all domains (land, air, sea, space, and cyber). Despite carefully worded statements, Washington is clearly trying to negate PRC and in some respects Iran’s A2/AD capabilities along with non-state actors.  The most widely discussed option when it comes to defeating A2/AD strategies is the highly controversial operational concept known as AirSea Battle. Many times confused as a war fighting strategy, in its simplest form, ASB is an effort by America’s military to ensure access to the global commons from any adversary that would contest such access across any and all domains.

The initial phrase ASB is a most likely a borrowed one. It derives its likeness from the Cold War concept of AirLand Battle (ALB). ALB was its own joint warfighting concept; however, that is largely where the similarities stop. As Robert Farley has noted, ALB succeeded Active Defense as U.S. Army doctrine in the early 1980’s. The doctrine primed NATO forces for  combat in Central Europe against the Warsaw Pact, although many of its basic precepts could also apply to other scenarios (like the 1991 Gulf War, for example). Farley explains that “ALB represented an accommodation between the Army and the USAF, providing a respite to the decades of intra and inter-service strife…” The Air Force essentially set aside its own strategic concept in order to provide operational and tactical support for army forces in a protracted struggle with a much larger conventional adversary.

CSBA Version of Air-Sea Battle: ASB 1.0?

The first comprehensive study of ASB and what it could offer U.S. war planners is a widely cited 2010 report from the Center for Strategic and Budgetary Assessments (CSBA) entitled: AirSea Battle – A Point of Departure Operational Concept. To this day, the report is one of the most authoritative documents concerning ASB, even though the concept has evolved dramatically since publication. While the document was developed without Department of Defense support, it provides important detailed operational and strategic guidance of how ASB could be moved from an operational concept into a war-fighting strategy to defeat A2/AD battle networks.

While the CSBA version addresses ASB capabilities at the tactical and strategic levels, it is the operational level that is most important, as ASB is an operational concept—which many scholars confuse. As the CSBA report notes:

Air-Sea Battle must address the critical emerging challenges and opportunities that projected Chinese A2/AD capabilities will present, and to which currently envisioned US forces do not appear to offer a suitable response. In general, since A2/AD capabilities seek to impose ever-greater constraints on US operational freedom of action, an AirSea Battle concept must address how the challenge can be offset or, failing that, how freedom of action can be regained in at least selected temporal/positional aspects for purposes of power projection.

The CSBA version of ASB would see combat take place in two stages. The first stage is detailed as an initial stage, comprised of several distinct lines of operation.  U.S. forces would first withstand an initial attack and limit possible damage. Next, a “blinding campaign” would commence against PLA battle networks. Next, a “suppression campaign” would then commence, focusing on PLA long-range ISR and strike systems. Focus would also be placed to ensure “Seizing and sustaining the initiative in the air, sea, space and cyber domains.” Emphasis would also be placed on “distant blockade operations,” and increased procurement and production of precision guided munitions—among other goals.

ASB would rapidly find acceptance and quickly be adopted by official U.S. war planners as part of an overall strategy to shift U.S. thinking away from COIN based operations to future military challenges—specifically operating in A2/AD environments. During late fall of 2011, it was announced that an Air-Sea Battle office was in the process of being formed to “oversee the integration of air and naval combat capabilities in an age of smaller budgets and leaner forces.”

ASB and the JOAC

ASB continued its evolution as part of a much wider Joint Operational Access Concept, or commonly known as JOAC, in early 2012. Signed by U.S. Chairman of the Joint Chiefs of Staff Martin Dempsey, the goal of this document is to show how U.S. “joint forces will operate in response to emerging anti-access and area-denial security challenges.” The JOAC places the first official U.S. definition of ASB into the public domain:

The intent of Air-Sea Battle is to improve integration of air, land, naval, space, and cyberspace forces to provide combatant commanders the capabilities needed to deter and, if necessary, defeat an adversary employing sophisticated A2/AD capabilities. It focuses on ensuring that joint forces will possess the ability to project force as required to preserve and defend U.S. interests well into the future.

Enter The ASB Office

ASB would again be refined and further sculpted once more in U.S. government documents for public disclosure, this time by the newly formed AirSea Battle office itself. On May 12, 2013, the ASB office released an unclassified version of what was dubbed a “summary” of the ASB operational concept:

A limited objective concept that describes what is necessary for the joint force to sufficiently shape A2/AD environments to enable concurrent or follow-on power projection operations. The ASB Concept seeks to ensure freedom of action in the global commons and is intended to assure allies and deter potential adversaries. ASB is a supporting concept to the Joint Operational Access Concept (JOAC), and provides a detailed view of specific technological and operational aspects of the overall A2/AD challenge in the global commons. The Concept is not an operational plan or strategy for a specific region or adversary. Instead, it is an analysis of the threat and a set of classified concepts of operations (CONOPS) describing how to counter and shape A2/AD environments, both symmetrically and asymmetrically, and develop an integrated force with the necessary characteristics and capabilities to succeed in those environments.

Confusion, Evolution and Revolution?

Even after the ASB offices authoritative documentation, many still confused ASB for a war-fighting strategy against China. Many mistakenly continue to this day cite and attack the CSBA version of ASB. The area of the document that draws the most attention is where it calls for controversial kinetic strikes on mainland China to disrupt important A2/AD C2 and C4ISR that would control PLA A2/AD combat capabilities. Because of this confusion, members of the House Armed Services Committee held a special session on October 10, 2013 in an attempt to remove any ambiguity (I was able to attend). The meeting was described as “for the first time ever, senior leaders from the Navy, Air Force, Marine Corps, Army and Joint Staff discussed the Air-Sea Battle Concept in an open hearing.” As U.S. Navy Rear Admiral James Foggo testified, ASB is:

Designed to assure access to parts of the “global commons” – those areas of the air, sea, cyberspace and space that no one “owns,” but which we all depend on – such as the sea lines of communication.  Our adversaries’ anti-access/area denial strategies employ a range of military capabilities that impede the free use of these ungoverned spaces. These military capabilities include new generations of cruise, ballistic, air-to-air, and surface-to-air missiles with improved range, accuracy, and lethality are being produced and proliferated. Quiet modern submarines and stealthy fighter aircraft are being procured by many nations, while naval mines are being equipped with mobility, discrimination and autonomy. Both space and cyberspace are becoming increasingly important and contested. Accordingly the Air-Sea Battle Concept is intended to defeat such threats to access, and provide options to national leaders and military commanders, to enable follow-on operations, which could include military activities, as well as humanitarian assistance and disaster response. In short, it is a new approach to warfare.

In many respects the debate and confusion around ASB has played a critical role in its evolution and definition in publicly available sources of information. While scholars will surely battle over the abilities of ASB to provide effective solutions to confront the challenge of proliferating A2/AD technologies and strategies, having a correctly understood definition of ASB are crucial to such a debate. As ASB has been misinterpreted, misunderstood, or mistaken for something it is not, those who look to the benefits of ASB have been forced to refine and develop the motivations and aspirations of this operational concept. While issues of national strategy, budgetary politics and public opinion may ultimately cause ASB to become nothing more than an historical curiosity (for the record, I sure hope not) its evolution continues on for those who wish to see it.

Harry J. Kazianis is a non-resident Senior Fellow at the China Policy Institute (University of Nottingham) as well as WSD Handa Fellow at the Center for Strategic and International Studies: PACNET. Mr. Kazianis also serves as Managing Editor for the National Interest. He previously served as Editor of The Diplomat. The views expressed are his alone.

 

Need a New Idea? Try An Old One: Revisiting PAC-10 in the Air-Sea Battle Concept

One does not need to look to far into the history of maritime operations to discern a pattern of importance: you are always attempting to locate and fix your adversary in order to destroy them, while simultaneously, your adversary is attempting the same. The sea provides a certain ubiquity that cannot be reduced in any aim of contestation by the other domains or more directly via control. Yet, when one considers the problems of a domain, there is interplay of practical constraints, which are: tactics, technology, organization, and doctrine. Here, I would briefly like to focus the reader’s attention on the latter item—doctrine—although there will be references to the other aspects throughout. Specifically, I would like to highlight the importance of the 1943 Pacific Fleet Tactical Orders and Doctrine, also known as PAC-10, and its possible relevance to the Air -Sea Battle Concept (ASBC).

The proper usage of naval aviation, and especially its carriers, has been debated since the days of Eugene Ely’s first flights launching and recovering on rudimentary aircraft carriers in 1910-11. During the interwar years between the World Wars there was vast variance in doctrine recursively revised as result of technological improvements, experimentation, and exercises. Doctrinal development and revision did not stop there, even as World War II unfolded in the Pacific, but in 1943, PAC-10 provided both timely clarity and flexibility to commanders in that theater.

Vice Admiral Richard “Terrible” Turner (Wikimedia Commons)
Vice Admiral Richard “Terrible” Turner (Wikimedia Commons)

Prior to World War II, specifically in 1937, U.S. Navy Captain Richard K. Turner presented a lecture at the Naval War College titled “The Strategic Employment of the Fleet,” and produced an associated pamphlet entitled “The Employment of Aviation in Naval Warfare.” While his lecture maintained a decisively Mahanian tenor, Turner’s pamphlet stated that “nothing behind the enemy front is entirely secure from observation and attack,” which provides rhyme to today’s “attack in-depth” in the ASBC.

According to Thomas Hone, before and during 1942, aircraft carrier doctrine focused upon three things: raids, ambushes, and covering invasion forces. Where raids attempted to fix Japanese forces in particular areas, ambushes would seek to attrit Japanese ability to control the seas, and invasion forces sought to add cumulative strategic effect by maneuvering amphibious forces to occupy specific islands for follow-on usage against Japan by joint forces.

A Japanese “Val” Dive-Bomber is shot down over the USS Enterprise on October 26, 1942 during the Battle of Santa Cruz (Wikimedia Commons)
A Japanese “Val” Dive-Bomber is shot down over the USS Enterprise on October 26, 1942 during the Battle of Santa Cruz (Wikimedia Commons)

The major shortfall of the doctrinal precursors to PAC-10 was that, while useful for thinking (and spurring debate) about the control of the maritime domain and maximizing the contest of the air and land domains, they fell short of effectively suggesting to commanders how to best employ aircraft and carriers operationally in task forces. This shortfall came into clear focus during the Battle of the Santa Cruz Islands. Enter the innovation of PAC-10.

In his Naval College Review article entitled, “Replacing Battleships with Aircraft Carriers in the Pacific in World War II,” Thomas Hone described PAC-10 as the following:

PAC-10 was a dramatic innovation. It combined existing tactical publications, tactical bulletins, task force instructions, and battle organization doctrine into one doctrinal publication that applied to the whole fleet. Its goal was to make it “possible for forces composed of diverse types, and indoctrinated under different task force commanders, to join at sea on short notice for concerted action against the enemy without interchanging a mass of special instructions.” PAC-10’s instructions covered one-carrier and multicarrier task forces, and escort- or light-carrier support operations of amphibious assaults. It established the basic framework for the four-carrier task forces—with two Essex-class ships and two of the Independence class—that would form the primary mobile striking arm of the Pacific Fleet. However, it did this within the structure of a combined naval force, a force composed of surface ships— including battleships and carriers….

 PAC-10 solved two problems. First, “the creation of a single, common doctrine allowed ships to be interchanged between task groups.” Second, “shifting the development of small-unit tactical doctrine to the fleet level and out of the hands of individual commanders increased the effectiveness of all units, particularly the fast-moving carrier task forces.”

PAC-10 was truly a watershed moment in operationally considering complement of sea and air capabilities en masse for strategic effect. It moved beyond the oversimplified “duty carrier” (self defense combat air patrol and/or antisubmarine warfare) and “strike carrier” (maritime strike and/or support to land forces ashore) concepts. “Whether a task force containing two or more carriers should separate into distinct groups . . . or remain tactically concentrated . . . may be largely dependent on circumstances peculiar to the immediate situation,” the doctrine stated, where “[no] single rule can be formulated to fit all contingencies.” Unsurprisingly, context was key in the application of PAC-10. Ultimately, PAC-10 focused commanders upon unified effort by maximizing strike, whether that is raids, ambushes, or amphibious attack, while also mitigating the risk of destruction via advanced detection.

Account of the valiant engagements off of Sumar during the Battle of Leyte Gulf. (Wikimedia Commons)
Account of the valiant engagements off of Sumar during the Battle of Leyte Gulf. (Wikimedia Commons)

There are several similarities and differences that need to be drawn from PAC-10 to now for consideration with the ASBC. First, and most importantly, the doctrinal concept did not and could not divine strategic victory. It was neither easy to accomplish, nor did it ignore the necessary requirement for termination to be chosen by the adversary, and furthermore, many heroically died in its use. However, and this is a fundamental truth that cynical detractors of the ASBC chose to ignore, many more would have died had PAC-10 not been developed. Rather, and it was apparent to them at the time, PAC-10 provided commanders an improved tool for use towards strategic effect. So say we all with concern to the ASBC.

U.S. Army Terminal High Altitude Area Defense (THAAD) Launch (SMDC Photo)
U.S. Army Terminal High Altitude Area Defense (THAAD) Launch (SMDC Photo)

Second, and almost as important as the first comparison, PAC-10 was a doctrinal concept that entailed warfare. And although there were no further constraints against escalation in World War II, PAC-10 provided considerable potential for strategic effect. How such an improved tool is used is a matter of decision in either the march towards war or during warfare to be made by policy makers via strategic negotiation, careful signaling, and demonstration. One mustn’t deny the value of PAC-10, or the doctrinal aspects of the ASBC, simply because of an over-wrought conflation of a tool with its purpose.

Tactical proficiency and operational effectiveness, are best measured in peacetime from the potential ideal, with the acknowledgment that fog and friction will chew away at that ideal in exercise and practice; whereas, strategic effect is best measured relative to a status quo and desire for continued advantage. The ASBC is focused clearly upon the former, and will only contribute limited strategic effect towards the latter. Clear-eyed strategists must admit that limited effect may be sufficient, but then again it may not as determined by context. However, neither is cause for rejection of an operational concept like the ASBC as a useful tool.

U.S. Marine Corps Amphibious Assault Force (Wikimedia Commons)
U.S. Marine Corps Amphibious Assault Force (Wikimedia Commons)

Third, the tactical combination of air and sea forces in PAC-10 combined with amphibious land attack, contributed to numerous successes in the Pacific. Similarly, a balanced ASBC, that includes a naval economy of force (relative to World War II), along with concomitant of air and land component forces, will create a complicated problem for mounting a successful defense at any one place; just like the PAC-10 doctrine similarly achieved at the Marcus, Gilbert, and Marshall Islands and elsewhere in World War II. In recent, yet more modern times, fleet defense may have been sufficient with only carrier-based aircraft. But at present, both the smaller number of available carriers, an inability to replenish weaponry while underway in the current submarine and destroyer forces, not to mention the basic prudence of joint capability, means that combined arms by way of only one service is no longer a prerogative that the United States can afford to ignore. Similar to the PAC-10 doctrine of yore, the modern ASBC doctrine of the near-future must be able to more effectively balance all joint forces. Needless to say, even if service prerogative still dominates, using carrier aviation alone will diminish strike potential in fleet defense. Dissimilar to the PAC-10 doctrine of yore, the modern ASBC doctrine of the near future must effectively raise its doctrine above that of the fleet and into the joint realm. This means finding effective ways to use Air Force assets and Army assets in roles of fleet defense and sea control just like disparate forces from various carriers in PAC-10 effectively formed a coherent and formidable task force.

Learning Large LessonsAs a guide for the ASBC, the interoperability between air forces (of all types) and land forces (of both traditional and amphibious focus) have benefited from the development of joint doctrine from the combined capabilities and tactics of the Air Land Battle Concept (ALBC). Despite some cynical “easy war” views of ASBC, the ALBC provides a useful scorecard for joint action. The latter has proven unquestionably effective in both mission success and preserving lives in battle from Operation DESERT STORM to the current fight in Operation ENDURING FREEDOM; but its equal in terms of joint combined effect does not yet exist to the same fidelity in the maritime and littoral environments. Our ability to project power, achieve strategic effect by joint combined arms, and experiment with doctrine costs relatively little compared to operational failure. Instead of playing politics — actual joint thinking costs nothing. After all, history and pragmatic thinking proves the obvious, you can’t finish without access.

Need a new idea? Try an old one. Take a look at Pacific Fleet Tactical Orders and Doctrine (PAC-10), and you might see the future of a balanced Air Sea Battle Concept doctrine.

Major Rich Ganske is a U.S. Air Force officer, B-2 pilot, and weapons officer.  He is currently assigned to the U.S. Army Command and General Staff Officers Course at Fort Leavenworth.  These comments do not reflect the views of the U.S. Air Force or the Department of Defense.  You can follow him on Twitter at @richganske and he blogs via Medium at The Bridge and Whispers to a Wall.  Tip of the hat to “Sugar” for the reference to an old idea (or book).