"We don't want to do all the development, we want to do the procurement. We want to buy it for the long term," said Maj. Gen. Clair Gill, PAE of Maneuver Air, framing a clear dilemma at the intersection of industry risk and government procurement.
What the Army is asking — and what GE is seeking
Two simple facts frame the moment: the Army is pressing industry to take on more of the development burden, and GE is seeking additional funding for ITEP testing. Those points — stated plainly in reporting and underscored by Maj. Gen. Clair Gill's remarks — set the parameters for an unfolding negotiation over who pays for innovation and how new capabilities move from concept to fleet.
What leaders are saying
Maj. Gen. Clair Gill, identified in reporting as the Program Executive Officer (PAE) of Maneuver Air, described a shift in posture: the service wants to "buy it for the long term" and is returning to manufacturers to negotiate how development costs can be positioned so they are not borne entirely by the government. That quote encapsulates a drive to rebalance development and procurement responsibilities between the Army and industry partners.
Why this matters
- Costs and incentives: Shifting more development expense to manufacturers changes the financial calculus for firms. It may encourage cost-efficiency and faster transitions to production, or it could alter which firms pursue risky advanced work without guaranteed government support.
- Program timelines and testing: If GE is requesting more funding for ITEP testing, the availability of government resources — and the outcome of cost-sharing talks with industry — could affect testing schedules and the pace at which new engines or components are validated.
- Procurement strategy: Maj. Gen. Gill's emphasis on long-term buying suggests the Army is thinking beyond one-off development contracts toward sustained acquisition relationships, which could reshape negotiations over intellectual property, sustainment, and lifecycle costs.
- Stakeholder perspectives: Technologists may welcome clearer procurement commitments that justify investment; policymakers must weigh budget trade-offs; users will watch for impacts on capability delivery; and competitors or observers will note how cost-sharing influences industrial base behavior.
Maj. Gen. Gill's comments make plain a core tension: who should shoulder the risk of transforming prototypes into deployable systems — the government that needs the capability, or the companies that build it? The answer will determine not only budgets but the speed and shape of modernization. As talks continue between the Army and manufacturers, one question remains: when industry and government disagree on who pays, who pays the price of delay?
