Category War by Numbers

Summation of our Validation Posts

This extended series of posts about validation of combat models was originally started by Shawn Woodford’s post on future modeling efforts and the “Base of Sand” problem.

Wargaming Multi-Domain Battle: The Base Of Sand Problem

This post apparently irked some people at TRADOC and they wrote an article in the December issue of the Phalanx referencing his post and criticizing it. This resulted in the following seven responses from me:

Engaging the Phalanx

Validation

Validating Attrition

Physics-based Aspects of Combat

Historical Demonstrations?

SMEs

Engaging the Phalanx (part 7 of 7)

This was probably overkill…..but guys who write 1,662 page books sometimes tend to be a little wordy.

While it is very important to identify a problem, it is also helpful to show the way forward. Therefore, I decided to discuss what data bases were available for validation. After all, I would like to see the modeling and simulation efforts to move forward (and right now, they seem to be moving backward). This led to the following nine posts:

Validation Data Bases Available (Ardennes)

Validation Data Bases Available (Kursk)

The Use of the Two Campaign Data Bases

The Battle of Britain Data Base

Battles versus Campaigns (for Validation)

The Division Level Engagement Data Base (DLEDB)

Battalion and Company Level Data Bases

Other TDI Data Bases

Other Validation Data Bases

There were also a few other validation issues that had come to mind while I was writing these blog posts, so this led to the following series of three posts:

Face Validation

Validation by Use

Do Training Models Need Validation?

Finally, there were a few other related posts that were scattered through this rather extended diatribe. It includes the following six posts:

Paul Davis (RAND) on Bugaboos

Diddlysquat

TDI Friday Read: Engaging The Phalanx

Combat Adjudication

China and Russia Defeats the USA

Building a Wargamer

That kind of ends this discussion on validation. It kept me busy for while. Not sure if you were entertained or informed by it. It is time for me to move onto another subject, not that I have figured out yet what that will be.

NYMAS in Manhattan on Friday, 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. The announcement is here: http://www.nymas.org/

The format is that I talk for an hour or so, and then take questions for the next 45 minutes.

There is a presentation on Friday the 12th 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.

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 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.

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.

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.