As the Army moves to modernize its software procurement processes, a clash looms between its efforts for reform and the actual mechanics of its acquisition practices. Senior officials recently voiced a commitment to streamline the process and collaborate more closely with non-traditional defense firms. However, skeptics argue that the rhetoric isn’t yet reflected in the Army’s actions.
Leo Garciga, the Army CIO, acknowledged the differing business models of non-traditional companies, emphasizing the Army’s efforts to adapt. Industry objections primarily revolve around the Army’s preference for custom software development and its reliance on a Pentagon-specific cost accounting system, which complicates matters for commercial software companies accustomed to off-the-shelf purchasing.
Jennifer Swanson, the Army’s software acquisition chief, highlighted the importance of industry feedback and maintaining opportunities for various companies to bid on software contracts. Yet critics note that while officials express the right intentions, the substance of recent procurement documents reflects a differing reality. Documents such as the March Army Directive 2024-04 and the recent Request for Information (RFI) suggest a departure from custom development but fail to align with the intended growth in collaborative bidding.
Warren Katz, a technology entrepreneur, highlighted a disconnect: while public statements reflect an aversion to inefficient custom projects, the formal documents suggest otherwise. An anonymous industry official mentioned that despite indications of progress, the Army’s adherence to cost-plus contracts over a firm-fixed price model continues to deter non-traditional participants.
Bill Greenwalt, a former congressional staffer involved in acquisition reforms, criticized the Army’s lingering embrace of cost-plus contracting, arguing that it does not align with contemporary software development practices. This contracting method is often inefficient for the tech industry, especially as many developers work in variable environments and do not easily fit into rigid labor categories.
Acknowledging concerns, Swanson noted that the Army intends to revise stringent cost-accounting requirements to better accommodate modern software development; however, she emphasized that cost-plus models still have a place in their strategy. Industry experts counter that the commercial market has ample solutions available at fixed prices, negating the need for costly custom software development.
With a software industry worth trillions and a vast array of existing products, Katz asserted that the Army could likely meet many of its needs through established commercial offerings without the complications introduced by bespoke solutions. The ongoing challenge remains: balancing the Army’s acquisition strategy with the dynamic and rapidly evolving commercial tech landscape.
