Mystics & Statistics

Combat Adjudication

As I stated in a previous post, I am not aware of any other major validation efforts done in the last 25 years other than what we have done. Still, there is one other effort that needs to be mentioned. This is described in a 2017 report: Using Combat Adjudication to Aid in Training for Campaign Planning.pdf

I gather this was work by J-7 of the Joint Staff to develop Joint Training Tools (JTT) using the Combat Adjudication Service (CAS) model. There are a few lines in the report that warm my heart:

  1. “It [JTT] is based on and expanded from Dupuy’s Quantified Judgement Method of Analysis (QJMA) and Tactical Deterministic Model.”
  2. “The CAS design used Dupuy’s data tables in whole or in part (e.g. terrain, weather, water obstacles, and advance rates).”
  3. “Non-combat power variables describing the combat environment and other situational information are listed in Table 1, and are a subset of variables (Dupuy, 1985).”
  4. “The authors would like to acknowledge COL Trevor N. Dupuy for getting Michael Robel interested in combat modeling in 1979.”

Now, there is a section labeled verification and validation. Let me quote from that:

CAS results have been “Face validated” against the following use cases:

    1. The 3:1 rules. The rule of thumb postulating an attacking force must have at least three times the combat power of the defending force to be successful.
    2. 1st (US) Infantry Divison vers 26th (IQ) Infantry Division during Desert Storm
    3. The Battle of 73 Easting: 2nd ACR versus elements of the Iraqi Republican Guards
    4. 3rd (US) Infantry Division’s first five days of combat during Operation Iraqi Freedom (OIF)

Each engagement is conducted with several different terrain and weather conditions, varying strength percentages and progresses from a ground only engagement to multi-service engagements to test the effect of CASP [Close Air Support] and interdiction on the ground campaign. Several shortcomings have been detected, but thus far ground and CASP match historical results. However, modeling of air interdiction could not be validated.

So, this is a face validation based upon three cases. This is more than what I have seen anyone else do in the last 25 years.

Dupuy’s Verities: Surprise

The Death of Paulus Aemilius at the Battle of Cannae by John Trumbell (1773). [Wikimedia]

The tenth of Trevor Dupuy’s Timeless Verities of Combat is:

Surprise substantially enhances combat power.

From Understanding War (1987):

Achieving surprise in combat has always been important. It is perhaps more important today than ever. Quantitative analysis of historical combat shows that surprise has increased the combat power of military forces in those engagements in which it was achieved. Surprise has proven to be the greatest of all combat multipliers. It may be the most important of the Principles of War; it is at least as important as Mass and Maneuver.

I have already written quite a bit on Dupuy’s conceptualization of surprise so I won’t go into it in detail here. These previous posts provide a summary:

The Combat Value of Surprise

Human Factors In Warfare: Surprise

Dupuy’s analysis focused on how surprise influenced combat power by enhancing the mobility and reducing the vulnerability of the side with surprise, and by increasing the vulnerability of the side that was surprised. In 2004, TDI undertook a study for the late Andy Marshall’s Office of the Secretary of Defense/Net Assessment to measure the historical combat value of situational awareness (more knowledge by one side than the other) and informational advantage (better knowledge by one side than the other) and how each of these factors related to surprise in combat. Chris Lawrence detailed this research and its conclusions in chapters 10 and 11 in his 2017 book, War by Numbers: Understanding Conventional Combat.

In general, the study found that both superior situational awareness and better information enhanced combat power, though perhaps not quite as much as inferred from the relevant literature. It also confirmed that surprise conferred an even greater combat power benefit, above and beyond that provided by battlefield awareness or informational advantages. It also suggested that the primary benefit of a situational or knowledge advantage in combat was not in achieving surprise over an enemy, but in preventing an opponent from achieving surprise itself.

These results, though quite suggestive, were tentative and more research is necessary. However, no follow on studies on this subject have been funded to date.

NYMAS on 26 April

I will be presenting my book War by Numbers at the New York Military Affairs Symposium (NYMAS) on Friday, 26 April, at the Soldiers Sailors Club in New York City. On the 12th there is a presentation of “The Grosse Importance of Kleine Krieg: Logistics, Operations, and ‘Little Wars’ in the late 17th Century Low Countries” by John Stapleton, U.S. Military Academy. The announcement is here: http://www.nymas.org/

Other Validation Data Bases

There have been (only) three other major historical validations done that I am aware of that we were not involved in. They are 1) the validation of the Atlas model to the France 1940 campaign done in the 1970s, 2) the validation of the Vector model using the Golan Heights campaign of 1973, and 3) the validation of SIMNET/JANUS using 73 Easting Data from the 1991 Gulf War. I am not aware of any other major validation efforts done in the last 25 years other than what we have done (there is one face validation done in 2017 that I will discuss in a later post).

I have never seen a validation report for the ATLAS model and never seen a reference to any of its research or data from the France 1940 campaign. I suspect it does not exist. The validation of Vector was only done for unit movement. They did not validate the attrition or combat functions. These were inserted from the actual battle. The validation was done in-house by Vector, Inc. I have seen the reports from that effort but am not aware of any databases or special research used. See Chapter 18 of War by Numbers for more details and also our newsletter in 1996 on the subject: http://www.dupuyinstitute.org/pdf/v1n4.pdf

So, I know of only one useful validation database out there that is not created by us. This is the Battle of 73 Easting. It was created under contract and used for validation of the JTLS (Joint Theater-Level Simulation).

But, the Battle of 73 Easting is a strange one-sided affair. First, it was fought in a sandstorm. Visibility was severely limited. Our modern systems allowed us to see the Iraqis. The Iraqis could not see us. Therefore, it is a very one-sided affair where the U.S. had maybe 6 soldiers killed, 19 wounded ant lost one Bradley fighting vehicle. The Iraqi had been 600-1,000 casualties and dozens of tanks lost to combat (and dozens more lost to aerial bombardment in the days and weeks before the battle). According to Wikipedia they lost 160 tanks and 180 armored personnel carriers. It was a shooting gallery. I did have a phone conversation with some of the people who did the veteran interviews for this effort. They said that this fight devolved to the point that the U.S. troops were trying to fire in front of the Iraqi soldiers to encourage them to surrender. Over 1,300 Iraqis were taken prisoner.

This battle is discussed in the Wikipedia article here: https://en.wikipedia.org/wiki/Battle_of_73_Easting

I did get the validation report on this and it is somewhere in our files (although I have not seen it for years). I do remember one significant aspect of the validation effort, which is that while it indeed got the correct result (all the Iraqi’s were destroyed), it did so having the Americans use four times as much ammunition as they did historically. Does this mean that the models attrition calculation was off by a factor of four?

Anyhow, I gather the database and the validation report are available from the U.S. government. Of course, it is a very odd battle and doing a validation to just one odd one-sided battle runs the danger of the “N=1” problem. Probably best to do validations to multiple battles.

A more recent effort (2017) that included some validation effort is discussed in a report called “Using Combat Adjudication to Aid in Training for Campaign Planning.” I will discuss this in a later blog post.

Now, there are a number of other database out there addressing warfare. For example the Correlates of War (COW) databases (see: COW), databases maintained by Stockholm International Peace Research Institute (SIPRI) (see: SIPRI) and other such efforts. We have never used these but do not think by their nature that they are useful for validating combat models at division, battalion or company level.

Company Commander

I recently re-read Company Commander by the late Charles B. McDonald. I had read it as a kid and picked up a used copy of it for my son. It was a Bantam War Book, specially illustrated edition. It still had the original price tag from 1979 on it: $2.25. My son never read it, so I decided to earlier this month.

What caught my attention on the re-reading was a passage on pages 212 and 215 that stated:

The buildings on either side of us disrupted the weak platoon radios, and I could not contact Sergeant Patton. We moved forward quickly, calling over the radio as we went, until we established contact. They had run into German machine guns in the last scattered house of the town and were having a stiff fight. I said I would send our light machine guns to help and called for them from the weapons platoon. They hurried up the street toward the sound of the firing.

Battalion radioed a change of orders….

I tried to call the platoons, but I could contact only the 1st and 2d, and Sergeant Patton said he did not know if he could disengage himself from the fire fight.

I told him to get out as quickly as he could, “Then move back to the castle and follow us around to the left. You’ll be the support platoon. If you can’t get away soon, we’ll start on up the hill without you. Just leave the Krauts. F company will take care of them.”

We’ve got three prisoners in the basement of a house,” Patton said, “and we have to cross a hundred yards of open field to get back out. We’ll never make it with the prisoners.”

“Roger,” I answered. “Do what you can.”…[page 212]

[page 215] Sergeant Patton’s platoon arrived, tired and dusty from the tiring uphill walk from Bendorf-Sayn. The prisoners were not with them.

Company G today committed a war crime. They are going to win the war, however, so I don’t suppose it really matters. [This paragraph was in italics in the original]

There is also a brief passage on pages 286 and 288:

Colonel Smith sent a messenger to tell me to meet him at a house in the center of the town….

“I just ran into your boy Junior,” Colonel Smith said. “He’s having a little trouble with a German major who claims he’s in command of all the flak defenses around Merseburg and seems quite put out that your men took him prisoner. He kept begging Junior either to shoot him or let him shoot himself. Junior was about to let him have his way when I happened up.” [page 286]

[page 288] “OK, Mac,” the Colonel answered….”By the way,” he added, “you can tell Junior that we finally had to dispense with his German major. He tried to make a run for it.”

Company Commander appears to be a very honest account. These are certainly uncomfortable passages. He did have the option to leave them out.

I did meet with Charles Macdonald back in the late 1980s. Him and Hugh Cole were consultants to the Ardennes Campaign Simulation Data Base (ACSDB).

Validation Data Bases Available (Ardennes)

I still recall our conversations with him, particularly about the American nurse and German General Fritz Bayerlein at Bastogne, but that is the subject of another post.

Other TDI Data Bases

What we have listed in the previous articles is what we consider the six best databases to use for validation. The Ardennes Campaign Simulation Data Base (ACSDB) was used for a validation effort by CAA (Center for Army Analysis). The Kursk Data Base (KDB) was never used for a validation effort but was used, along with Ardennes, to test Lanchester equations (they failed).

The Use of the Two Campaign Data Bases

The Battle of Britain Data Base to date has not been used for anything that we are aware of. As the program we were supporting was classified, then they may have done some work with it that we are not aware of, but I do not think that is the case.

The Battle of Britain Data Base

Our three battles databases, the division-level data base, the battalion-level data base and the company-level data base, have all be used for validating our own TNDM (Tactical Numerical Deterministic Model). These efforts have been written up in our newsletters (here: http://www.dupuyinstitute.org/tdipub4.htm) and briefly discussed in Chapter 19 of War by Numbers. These are very good databases to use for validation of a combat model or testing a casualty estimation methodology. We have also used them for a number of other studies (Capture Rate, Urban Warfare, Lighter-Weight Armor, Situational Awareness, Casualty Estimation Methodologies, etc.). They are extremely useful tools analyzing the nature of conflict and how it impacts certain aspects. They are, of course, unique to The Dupuy Institute and for obvious business reasons, we do keep them close hold.

The Division Level Engagement Data Base (DLEDB)

Battalion and Company Level Data Bases

We do have a number of other database that have not been used as much. There is a list of 793 conflicts from 1898-1998 that we have yet to use for anything (the WACCO – Warfare, Armed Conflict and Contingency Operations database). There is the Campaign Data Base (CaDB) of 196 cases from 1904 to 1991, which was used for the Lighter Weight Armor study. There are three databases that are mostly made of cases from the original Land Warfare Data Base (LWDB) that did not fit into our division-level, battalion-level, and company-level data bases. They are the Large Action Data Base (LADB) of 55 cases from 1912-1973, the Small Action Data Base (SADB) of 5 cases and the Battles Data Base (BaDB) of 243 cases from 1600-1900. We have not used these three database for any studies, although the BaDB is used for analysis in War by Numbers.

Finally, there are three databases on insurgencies, interventions and peacekeeping operations that we have developed. This first was the Modern Contingency Operations Data Base (MCODB) that we developed to use for Bosnia estimate that we did for the Joint Staff in 1995. This is discussed in Appendix II of America’s Modern Wars. It then morphed into the Small Scale Contingency Operations (SSCO) database which we used for the Lighter Weight Army study. We then did the Iraq Casualty Estimate in 2004 and significant part of the SSCO database was then used to create the Modern Insurgency Spread Sheets (MISS). This is all discussed in some depth in my book America’s Modern Wars.

None of these, except the Campaign Data Base and the Battles Data Base (1600-1900), are good for use in a model validation effort. The use of the Campaign Data Base should be supplementary to validation by another database, much like we used it in the Lighter Weight Armor study.

Now, there have been three other major historical validation efforts done that we were not involved in. I will discuss their supporting data on my next post on this subject.

A Comment On The Importance Of Reserves In Combat

An German Army A7V near the Somme on March 26, 1918 [forces.net] Operation Michael was the first of a series of German Army offensives on the Western Front in the spring of 1918. In late March, 74 German divisions employing infiltration tactics created a breach in a sector of the line held by the British Army. The Germans advanced up to 40 miles and captured over 75,000 British soldiers, but the ability of the British and French to redeploy reserves via rail halted the offensive in early April short of strategic success.

In response to my previous post on Trevor Dupuy’s verity regarding the importance of depth and reserves for successful defense, a commenter posed the following question: “Is the importance of reserves mainly in its own right, or to mitigate the advantages of attacker surprise?”

The importance of reserves to both attacker and defender is as a hedge against the circumstantial uncertainties of combat. Reserves allow attacking and defending commanders the chance to maintain or regain initiative in response to the outcomes of battle. The side that commits its last reserves before its opponent does concedes the initiative to the enemy, probably irrevocably.

In Trevor Dupuy’s theory of combat, the intrinsic superiority of the defensive posture (as per Clausewitz) is the corollary to the attacker’s inherent advantage in initiative. When combined with the combat multipliers of favorable terrain and prepared positions or fortifications, the combat power of a defending force is greatly enhanced. This permits a defending commander to reap the benefit of economy of force to create reserves. When arrayed in sufficient depth to prevent an attacker from engaging them, reserves grant flexibility of response to the defender. A linear defense or improperly placed reserves concede this benefit to the attacker at the outset, permitting the attacking commander to exploit initiative to mass superior combat power at a decisive point without reserves to interfere.

A defender’s reserves are certainly useful in mitigating attacker surprise, but in Dupuy’s theories and models, surprise is a combat multiplier available to both attacker and defender. As perhaps the most powerful combat multiplier available on the battlefield, surprise in the form of a well-timed counterattack by a defender can devastate an attacking force. Even an unexpected tactical wrinkle by a defender can yield effective surprise.

Battalion and Company Level Data Bases

Since the collapse of the Soviet Union in 1991, the need and desire to model combat at the division-level has declined. The focus has shifted to lower levels of combat. As such, we have created the Battalion-Level Operations Data Base (BLODB) and the Company-Level Actions Data Base (CLADB).

The challenge for both of these databases is to find actions that have good data for both sides. It is the nature of military organizations that divisions have the staff and record keeping that allows one to model them. These records are often (but not always !!!) preserved. So, it is possible to assemble the data for both sides for an engagement at division level. This is true through at least World War II (up through 1945). After that, getting unit records from both sides is difficult. Usually one or both of the opponents are still keeping their records classified or close hold. This is why we ended up posting on this subject:

The Sad Story Of The Captured Iraqi DESERT STORM Documents

And:

So Why Are Iraqi Records Important?

 

Just to give an example of the difficulty of creating battalion-level engagements, for the southern offensive around Belgorod (Battle of Kursk) from 4-18 July 1943 I was able to created 192 engagements using the unit records for both sides. I have yet to create a single battalion-level engagement from those records. The only detailed description of a battalion-level action offered in the German records are of a mop-up operation done by the 74th Engineer Battalion. We have no idea of who they were facing or what their strength was. We do have strengths at times of various German battalions and we sometimes have strength and losses for some of the Soviet infantry and tank regiments, so it might be possible to work something up with a little estimation, but it certainly can not be done systematically like we have for division-level engagements. As U.S. and British armies (and USMC) tend to have better battalion-level record keeping than most other armies, it is possible to work something up from their records, if you can put together anything on their opponents. So far, our work on battalion-level and company-level combat has been more of a grab-bag and catch-and-catch-can effort that we had done over time.

Our battalion-level data base consists of 127 cases. They cover from 1918 to 1991. It is described here: http://www.dupuyinstitute.org/data/blodb.htm The blurry photo at the start of this blog if from that database.

Our company-level data base is more recent. It has not been set up yet as an Access data base. It consists of 98 cases from 1914 to 2000.

The BLODB was used for the battalion-level validation of the TNDM. This is discussed briefly in Chapter 19 of War by Numbers. These engagements are discussed in depth in four issues of  our International TNDM Newsletter (see Vol. 1, Numbers 2, 4, 5, 6 here: http://www.dupuyinstitute.org/tdipub4.htm )

The CLADB was used for a study done for Boeing on casualty rates compared to unit sizes in combat. This is discussed in depth in Chapter 12: The Nature of Lower Levels of Combat in War by Numbers.

Both databases are in need to expansion. To date, we have not found anyone willing to fund such an effort.

A Genius for War is back in print

While browsing Amazon.com I discovered that Trevor Dupuy’s Genius for War is back in print. It has a new cover.

It was republished last year by a company called Endeavour Media, Ltd. Trevor Dupuy’s works still belong to the family and are managed by one of his sons. The book does have 32 reviews on Amazon.com, a lot of them fairly recent (27 from 2011 and later).

A Genius for War

Also see:

http://www.endeavourmedia.co.uk/our-books/

http://www.endeavourmedia.co.uk/?s=dupuy

They have the following books by Trevor Dupuy for sale:

A Genius of War

The Battle of Austerlitz

Brave Men and Great Captains

Elusive Victory: The Arab-Israeli Wars, 1947-1974

Flawed Victory: How Lebanon became a cauldron of war and hate (co-authored by Paul Martell)

Future Wars: The World’s Most Dangerous Flashpoints

Hitler’s Last Gamble: The Battle of the Bulge

Military Heritage of America

The Compact History of the Revolutionary War

Understanding Defeat: How to Recover from Loss in Battle and Gain Victory in War

World War II: A Combat History (by R. Ernest Dupuy)

 

We also have a number of Trevor Dupuy’s books for sale. See http://www.dupuyinstitute.org/booksfs.htm

The books are:

Understanding War: History and Theory of Combat

Attrition: Forecasting Battles, Casualties and Equipment Losses in Modern War

Elusive Victory: The Arab Israeli Wars, 1947-197

Brave Men and Great Captains

Understanding Defeat

Future Wars

The Harper Encyclopedia of Military Biography

Military Heritage of the America, Volume II (only…but updated)

If War Comes; How to Defeat Saddam Hussein

Hitler’s Last Gamble (two volume Japanese language edition)

The Division Level Engagement Data Base (DLEDB)

The Division Level Engagement Data Base (DLEDB) is one of eight data bases that make up our DuWar suite of databases: See http://www.dupuyinstitute.org/dbases.htm This data base, of 752 engagements, is described in depth at: http://www.dupuyinstitute.org/data/dledb.htm

It now consists of 752 engagements from 1904 to 1991. It was originally created in 2000-2001 by us independent of any government contracts (so as to ensure it was corporate proprietary). We then used it as an instrumental part of the our Enemy Prisoner of War studies and then our three Urban Warfare studies.

Below is a list of wars/campaigns the engagements are pulled from:

Russo-Japanese War (1904-1905): 3 engagements

Balkan Wars (1912-1913): 1 engagement

World War I (1914-1918): 25 engagements

…East Prussia (1914): 1

…Gallipoli (1915): 2

…Mesopotamia (1915): 2

…1st & 2nd Artois (1915): 7

…Loos (1915): 2

…Somme (1916): 2

…Mesopotamia (1917): 1

…Palestine (1917): 2

…Palestine (1918): 1

…US engagements (1918): 5

World War II (1939-1945): 657 engagements

…Western Front: 295

……France (1940): 2

……North Africa (1941): 5

……Crete (1941): 1

……Tunisia (1943): 5

……Italian Campaign (1943-1944): 141

……France (1944): 61

…,,,Aachen (1944): 23

……Ardennes (1944-1945): 57

…Eastern Front: 267

……Eastern Front (1943-1945): 11

…….Kursk (1943): 192

……Kharkov (1943): 64

…Pacific Campaign: 95

…….Manchuria (1938): 1

…….Malayan Campaign (1941): 1

…….Phillipines (1942): 1

…….Islands (1944-1945): 4

…….Okinawa (1945): 27

…….Manila (1945): 61

Arab-Israeli Wars (1956-1973): 51 engagements

…1956: 2

…1967: 16

…1968: 1

…1973: 32

Gulf War (1991): 15 engagements

 

Now our revised version of the earlier Land Warfare Data Base (LWDB) of 605 engagements had more World War I engagements. But some of these engagements had over a hundred of thousand men on a side and some lasted for months. It was based upon how the battles were defined at the time; but was really not relevant for use in a division-level database. So, we shuffled them off to something called the Large Action Data Base (LADB), were 55 engagements have sat, unused, since then. Some actions in the original LWDB were smaller than division-level. These made up the core of our battalion-level and company-level data bases.

The Italian Campaign Engagements were the original core of this database. An earlier version of the data base has only 76 engagements from Italy in them (around year 2000). We then expanded, corrected and revised them. So the database still has 40 of the original engagements, 22 were revised, and the rest (79) are new.

The original LWDB was used for parts of Trevor Dupuy’s book Understanding War. The DLEDB was a major component of my book War by Numbers.

As can be seen, it is possible to use this database for model development and/or validation. One could start by developing/testing the model to the 141 Italian Campaign engagements, and then further develop it by testing it to the 141 campaigns from France and the Battle of the Bulge. And then, to test the human factors elements of your models (which if you are modeling warfare I would hope you would have), one could then test it to the 267 division-level engagements on the Eastern Front. Then move forward in time with the 51 engagements from the Arab-Israeli Wars and the 15 engagements from the Gulf War. There is not a lack of data available for model development or model testing. It is, of course, a lot of work; and lately it seems that the  industry has been more concerned about making sure their models have good graphics.

Just to beat a dead horse, we remind you of this post that annoyed several people over at TRADOC (the U.S. Army’s Training and Doctrine Command):

Wargaming Multi-Domain Battle: The Base Of Sand Problem

Finally, it is possible to examine changes in warfare over time. This is useful to understand it one is looking at changes in warfare in the future. The DLEDB covers 88 years of warfare. We also have the Battles Data Base (BaDB) of 243 battles from 1600-1900. It is described here: http://www.dupuyinstitute.org/data/badb.htm

Next I will describe our battalion-level and company-level databases.