Skip to content

Navigation Menu

About

  • Mission and Vision
  • Leadership
  • History
  • Fort Leonard Wood Historic Tour
  • FLW Command Policies and Memorandums of Instruction
  • Fort Leonard Wood Regulations
  • About the Region Video
  • Explore the FLW Region

My Fort Leonard Wood

Visitors Access
Training Information
Graduation Information
Newcomers Information
eGuidon News
Hunting and Fishing
Fort Leonard Wood MWR
Bruce C. Clarke Library
Sexual Harassment Assault Response Prevention (SHARP)
Military Equal Opportunity
Voter Assistance
Army Community Services
Army Emergency Relief (AER)

Contact

  • Crisis Phone Numbers
  • Phone Directory
  • Office of the Inspector General
  • MWR Calendar
  • Feedback (ICE)
  • Public Affairs Office
  • MSCoE Publications
    • Writer's Guide & Submission Guidelines
    • Protection Professional Bulletin
    • Protection Proponent
    • Army Chemical Review
    • Engineer Professional Bulletin
      • Training Challenges in Port Damage Repair for Army Engineer Divers
      • The Impact of Data Deluge on the Task Force Engineer Information Processing Solutions for the Modern Operating Environment
      • Returning the Focus to Being Masters of Terrain: Replacing 12B with 19C in the Turret
      • From Tech to Tactics: Integrating the Multi-Source Positioning (Part 3 of 3)
      • The Technological Fix: Building a Resilient Alternatives to GPS (Part 2 of 3)
      • A System at Risk: America's Strategic Vulnerability in GPS (Part 1 of 3)
      • By Engineers, For Engineers: Reflecting on 20 Years of JEOC
      • Rethinking Survivability
      • 12G AIT Transformation to 12N ASI
      • Battlefield Makerspaces
      • Sustaining Division Engineer Battalions
      • Blast Overpressure: Risk Mitigation for Maximum Performance
      • Maintenance Moving Forward
      • 3D Printing in Multidomain Operations United States Army Engineer Regiment
      • Cold Region Engineer Operations: The Engineer Regiment Needs to Get Comfortable Being Cold
      • The Engineer Coordinator History and Usage
      • Security Engineer For 120A Warrant Officer Basic Course
      • South China Sea: The Need for Army Engineer Amphibious Training and Doctrine
      • Enhancing Joint Logistics Over-the-Shore Operations: Lessons From the Gaza Humanitarian Mission
      • Improving Protection Training: How to Prepare for the Next Conflict
      • Urban Combat and The Gaza Metro: Preparing for War in Modern Megacities
      • The Future of Engineers in the South China Sea
      • Brazilian Army Engineer Instruction Center
      • Regimental Command Sergeant Major
      • Regimental Command Warrant Officer
      • Commandant
      • The Use of ARRK to Develop a COP at AO Victory
      • Engineer Reconnaissance: Technical Skills in the Reconnaissance Fight
      • Junior Engineer Officers Need Better Training
      • The Bureaucratic Bind: How Current Administrative Requirements Hinder Warfighting
      • Open Data Sources in Support of Engineer Reconnaissance
      • Training Junior Engineer Officers: The Way Forward
      • What is HMI?
      • Incorporating LMs into TSOs
      • Engineers, Partnerships, and Recruitment
      • Engineers on the Peninsula: Experience and Legacy of the 52nd BEB During KRF-13
      • Condition Checks: Wet-Gap Crossings
      • Operations Turning Point
      • EAB Engineer Battalion Training at JRTC
      • Should Company Commanders Have Dedicated GIS Assets?
      • Engineer Lessons Learned from the War in Ukraine
      • Planning for Construction of the Perfect Castle
      • Lieutenant Development
      • Reflections from a Deputy District Commander
      • Port Damage Repair Using Army Organic Equipment to Test Developing Mission Sets
      • The Future Role of Engineer Reconnaissance in Large-Scale Combat Operations
      • Data-Driven Risk Management in USACE Construction Contracts
      • Using Open-Source Intelligence to Improve Readiness
      • Hamid Karzai International Airport Prime Power Mission
      • Bridging the Gap Together: Send in the Joint Engineer Support Brigade
      • Implementing Lessons Learned to Build a Better Command Post
      • Where Did the IEDs Go? Thoughts on Strategic and Operational Rear Areas
      • Multidomain Operations: The latest Evolution of Operational Doctrine
      • Strong Point Huff: Building The LSCO Fight
      • Managing Manhattan: A Case Study in Complex Project Management
      • Value of the POP Method in Training
      • Lessons Learned From Defender Europe 2022: The MRBC Perspective
      • Let us try to implement FM 3-0: Challenges of LSCO at the Engineer Company Level
      • Activating an MRBC: Challenges and Opportunities in Mobilizing a Force Multiplication Unit
      • Miniature Excavator
      • Engineer Doctrine Corner
      • Engineer Archives
    • Military Police Professional Bulletin
  • U.S. Army Counterintelligence Command

Units / Tenants

  • U.S. Army Engineer School
  • U.S. Army CBRN School
  • U.S. Army Military Police School
  • 102nd Training Division
  • MSCoE Noncommissioned Officers Academy
  • 43rd AG Reception Battalion
  • 58th Transportation Battalion
  • 763D EOD
  • Homeland Defense Civil Support Office
  • Geospatial Enterprise Office
  • General Leonard Wood Community Hospital
  • U.S. Air Force
  • Marine Corps Detachment
  • Navy Detachment
  • U.S. Army Prime Power School

Search

Home U.S. Army home page
Army.mil
U.S. Army Fort Leonard Wood
U.S. Army Fort Leonard Wood
U.S. Army Fort Leonard Wood

Home of the Maneuver Support Center of Excellence.


NEW!   Check out the new NCO's Barracks Guidebook!
  1. Home
  2. Contact
  3. MSCoE Publications
  4. Engineer Professional Bulletin
  5. Data-Driven Risk Management in USACE Construction Contracts

Data-Driven Risk Management in USACE Construction Contracts

Data-Driven Risk Management in USACE Construction Contracts

By Captain Robert B. Skinker and Captain Timothy J. Naudet

USACE Business Impact

On average, the U.S. Army Corps of Engineers (USACE) currently experiences a 60 percent time overrun and 7 percent budget overrun on construction contracts.[1] These contract overruns cost the government years of construction potential and billions of dollars, adversely affecting training and readiness capabilities.[2]

USACE collects information pertaining to all construction contracts through the Resident Management System (RMS), which tracks contract performance, including data on awards, execution, and closeouts of projects. The data-rich RMS is an untapped resource that represents an opportunity to analyze data to mitigate contract risk—the source of time and budget overrun.

Data-Driven Study

To enhance the ability to determine and predict the performance of projects, the authors, Captain Robert B. Skinker and Captain Timothy J. Naudet, performed a machine learning technical analysis of USACE construction contracts. The goal of the study was to use RMS to measure performance as a percentage of time and budget overrun and to ascertain how to effectively determine and predict project overrun—not to find ways to replace human analysts.

Data Collection and Organization

Initial contract cost vs POP
Figure 1. Initial contract cost (award) versus the original time (POP), separated by type (small business or unrestricted). The dotted red box delineates the region with equal opportunity for the award of either type.

As a starting point, Captain Skinker and Captain Naudet partnered with USACE–Louisville District subject matter experts, who provided 307 completed military construction and multiple award task order contracts for analysis. The dates of all contracts were within the 10-year period from 2009 to 2019.

Next, the data set was pruned from 307 to 186 contracts (admittedly, a relatively small number) to avoid biases that could be introduced by unique or scenario-based situations. The data was then “cleaned” (organized for computation) since computers—much like humans—require strict data organization regimens. For example, whereas English-speaking people read from left to right, computers read data row by row. As a result of the initial data-cleaning efforts, it was recommended that the Louisville District alleviate the use of “free text” in favor of “vetted categorical variables,” thereby preventing the data corruption that occurs when users refer to one entity in multiple ways (“Fort Leonard Wood” versus “Fort Wood” or “FLW,” for example). This would establish a higher standard of “data governance” and streamline future projects. Once the data had been cleaned, it was ready to be analyzed for patterns of overrun.

Data Analysis and Conclusions

Histograms of project procurement methods
Figure 2. Histograms of counts of project procurement methods (DB versus DBB) separated into “buckets” based on overrun. Left: time overruns; Right: cost overruns.

In the investigation of project overrun, the first variable analyzed was the effect of “small business” versus “unrestricted” contracts. A graph illustrating the relationship between the initial contract cost (award) and the original time (period of performance [POP]) for each of these types of contracts indicates that contracts for larger projects tend to be awarded as unrestricted (implying a preference for larger firms), while contracts for smaller projects tend to be “set aside” for small businesses (Figure 1). Such an imbalance in contract awards renders a direct comparison of all awards invalid; however, a “fair comparison window” (within which there is equal opportunity for the award of either type of contract) has been delineated by a dotted red box on the graph in Figure 1. When comparing contract awards within the fair comparison window, this study concluded that, on average, small businesses are just as effective at eliminating overruns as large firms are.

The second variable analyzed in the project overrun investigation was the effect of design-bid-build (DBB) versus design-build (DB) procurement methods. With the DBB procurement method, the design is completed by one firm and another firm bids on and builds the project; in contrast, with the DB procurement method, a single firm designs and builds the project. Histograms depicting cost and time overruns for each of these procurement methods are presented in Figure 2. Based on the data, it was determined that there is only a slight difference in cost overrun and no statistically significant difference in time overrun between the two procurement methods. The study concluded that for eliminating overrun, DB is the more effective of the two procurement strategies—but only slightly so.

Plot showing stability of cost and time overrun over 10 years
Figure 3. Stability of cost and time overrun for the 10 years analyzed.

The next aspect of project overrun that was analyzed was the stability of both time and cost overrun by year. As can be seen in Figure 3, there were relative spikes in time overrun for contracts awarded in 2012 and 2014 and an even more significant time overrun spike for contracts awarded between 2017 and 2019. These time overruns appear to be closely related to environmental variables, which can include laws, regulations, and weather. The spike in time overrun for contracts awarded from 2017 to 2019 is likely due to the administrative effects of the COVID-19 pandemic. Unfortunately, the data set does not contain information about environmental variables that may have affected time overrun of annual projects; it is suggested that SMEs be consulted with regard to the causes of the observed environmental effects. It is also recommended that data governance be restructured to address this information shortfall in the future. The study concluded that when analyzing overrun stability by year, efforts should be focused on time overrun, as cost overrun tends to be predictably stable.

US map of average overrun percentage by state
Figure 4. Map of the United States indicating the average overrun percentage observed across states.

Another project overrun variable that was analyzed in this study was that of geography. Figure 4 contains a heat map showing the average project overrun by state across the United States, with brighter colors indicating states with higher overruns. Based on the data, the North Atlantic Region—comprised of New York, Massachusetts, New Jersey, and New Hampshire—has statistically higher overruns than other regions of the country. It is presumed that the time and cost overruns associated with this region are due to environmental variables; however, the lack of environmental information in the data set requires speculation.

Linear model and real-world overrun classification plots
Figure 5. Actual vs Predicted Overrun Classifications. Right: Real-world classifications vs Award options/POP. Left: Linear model developed to predict the overrun of a contract based on its initial budget and original POP.

The final aspect analyzed in the project overrun study was the relationship between overrun and the two variables of initial contract cost (award) and original time (POP). Contracts were categorized as “low overrun” (if in the lower 50 percent of contract overruns) or “high overrun” (if in the upper 50 percent of contract overruns) and plotted on the graph on the right in Figure 5—with low-overrun contracts depicted in blue and high-overrun contracts depicted in orange. The graph on the right, therefore, represents real-world data (the ground truth).

Upon analysis of this data, a predictive relationship between contract overruns and the two variables (initial cost and original time) was identified; that relationship is defined by the following “Golden Ratio” equation:
Budget overrun = [$10 million x (d/350)] - $4 million; d ∈ {200 . . . 700} days
(which is read as: budget overrun is equal to $10 million multiplied by d/350, where d is the number of days and is an integer inclusively contained between 200 and 700). The plot on the left in Figure 5 is a graphic representation of the linear model, again with low-overrun contracts depicted in blue and high-overrun contracts depicted in orange. The graph demonstrates that for projects with original POPs of 200 to 720 days, contracts with lower initial awards or shorter POPs are more likely to result in overruns. When applied at scale, the model can be used (with 60 percent accuracy) to predict cost and time overruns of contracts and determine whether a particular project is likely to be high-risk (categorized as high-overrun). This is the most significant contribution of the study. It is recommended that the Golden Ratio be applied to future contracts and that, if necessary, contractor adjustments be requested prior to USACE acceptance. The savings could potentially be significant; a savings of 10 percent across all contracts for a given year equates to 10 percent of the budget that can be used for other projects.

Summary of Results

The statistically significant findings of the USACE construction contract study include the following:

  • Contracts awarded to small businesses perform in a manner similar to those of large firms.
  • The DB procurement process is only slightly more effective than the DBB process at eliminating overrun.
  • Environmental variables undoubtedly affect time overrun; however, those variables are not currently captured in the project data set.
  • There is a significant relationship between time overrun and the year of contract award, while cost overrun is independent of the year of contract award.
  • The North Atlantic Region of the United States experiences statistically higher overruns than other regions of the country.
  • The Golden Ratio can serve as a tool to predict cost and time overruns of certain projects with 60 percent accuracy.

These findings should help enable USACE professionals to make data-driven decisions in order to mitigate project overrun; parties who are interested in obtaining a more complete report of the study may reach out to the authors of this article.

The Way Ahead

The machine learning technical analysis of USACE construction contracts is aligned with the recently distributed “Message to the Army Team”[3]—primarily with the continuous transformation policy, as the study meets the criterion of integrating technology as soon as it is useful. However, future goals include obtaining additional data and standardizing data governance, thereby enabling dramatic improvements to predictive model performance. Other USACE districts are encouraged to contact the authors of this article to become involved in future studies.Engineer Watermark Crest

About the Authors

Captain Skinker is the commander of the 50th Multi-Role Bridge Company, 5th Engineer Battalion, Fort Leonard Wood, Missouri. He holds a bachelor of science degree in mechanical engineering from Virginia Tech. He completed work on the study described in this article as a requirement for obtaining a master’s degree in information system management–business intelligence and data analytics from Carnegie Mellon University, Pittsburgh, Pennsylvania. Captain Skinker can be reached by e-mail at <robert.j.skinker.mil@army.mil> or by telephone at 610-533-4380.

Captain Naudet is a data scientist at the U.S. Army Artificial Intelligence Integration Center, Army Futures Command, Pittsburgh. He holds a bachelor of science degree in chemistry from the U.S. Military Academy–West Point, New York. He completed work on the study described in this article as a requirement for obtaining a master’s degree in information system management–business intelligence and data analytics from Carnegie Mellon University. Captain Naudet can be reached by e-mail at <timothy.j.naudet.mil@army.mil> or by telephone at 818-414-0815.

Endnotes:

  1. These estimates are based on data from the USACE–Louisville District; it is reasonable to expect similar numbers throughout USACE. ↩
  2. “U.S. Army Corps of Engineers: FY 2023 Appropriations,” Congressional Research Service, 20 April 2023, https://crsreports.congress.gov/product/pdf/IF/IF12090, accessed on 4 January 2024. ↩
  3. Michael R. Weimer, Randy A. George, and Christine E. Wormuth, “Message to the Army Team,” 27 October 2023, https://www.army.mil/article/271225/october_26_2023_message_to_the_army_team, accessed on 4 January 2024. ↩
Download Original PDF Document
Published 2024
Share this page:

Army.mil

Army.mil


Employment

FOIA

Terms of Use

Accessibility/Section 508

Ready Army


Need Help? Try Army A-Z

My Army Benefits

Warriors Wanted Videos

Page Last Modified: 8/10/26, 3:13 PM

Army CID Submit a Tip / Report a Crime Logo

ManeuverSptCtrOfExce_nobackground.fw.png

Fort Leonard Wood

 

Policies and Regulations

MSCoE MEO and Garrison EEO

SHARP

Provide Feedback

Webmaster

PRIVACY

 

 

Community Resource Guide

https://www.usainscom.army.mil/isalute/iSalute - Report suspicious activity

imcom.army.mil

U.S. ARMY INSTALLATION MANAGEMENT COMMAND


"We Are the Army's Home"

FIND A GARRISON

Survivor Outreach Services | Total Army Sponsorship | Safety

Human Resources | Civilian Expeditionary Workforce

U.S. Army Environmental Command | Assistant Secretary of the Army for Installations, Energy & Environment

Back to Top