defense-contracting

  • |

    The Pentagon’s $500 Million Drone Shield

    ByPhil McCracken

    Washington announced a $500 million drone shield, and my money-trail desk immediately found the box labeled “maximum possible invoice.” The Army’s Joint Interagency Task Force 401 awarded CACI a three-year indefinite-delivery/indefinite-quantity contract for domestic counter-drone work. That contract carries a ceiling of $500 million. It does not mean the government has already spent $500 million, nor does it mean taxpayers have received $500 million worth of protection. In federal contracting, the headline arrives express; the receipt travels by carrier pigeon.

    CACI’s SkyValor system was selected for the first task order, according to the company and the Army. That is a real procurement step, but it is not a performance report, an operational-results report, or a guarantee that every dollar under the ceiling will be used. The distinction matters because “up to” is one of the most profitable phrases in public life. A restaurant cannot serve you an imaginary twelve-course meal and call it dinner, but a defense contract can reserve the table for three years and leave the final bill developing off-site.

    The Pentagon’s argument is speed. Counter-drone threats move quickly, so acquisition needs what officials describe as speed of relevance. Fair enough: nobody wants a security system designed at the pace of a committee hearing about whether the threat exists. An indefinite-delivery structure can give the government flexibility to order equipment and services as requirements develop. But flexibility for the buyer can become fog for the public, especially when the contract ceiling is easier to print than the eventual orders, prices, delivery milestones, and results.

    That is where Phil McCracken follows the invoice through the shrubbery. The concern is not that counter-drone technology is unnecessary, or that CACI has done something improper. The concern is that urgency can become a permission slip to explain the money later. A ceiling is an authorization limit, not a receipt. A first task order is an opening transaction, not proof that the whole promised shield has arrived and works as advertised. Taxpayers deserve to see what gets ordered, what it costs, what shows up, and what performs before the contract’s maximum becomes Washington’s favorite round number.

    America may need a drone shield. It does not need a public accounting shield protecting the invoice from daylight. The country gets protection now, defense contractors get a potentially recurring tab, and the details remain somewhere between “mission accomplished” and “please hold.” In Washington, even homeland security comes with an expandable subscription plan.

    Sources

  • |

    The Pentagon’s $7 Billion Software Subscription Comes With a Free Accountability Question

    ByPhil McCracken

    Phil McCracken looks at a possible $7 billion Pentagon software commitment the way a diner waitress looks at a fake coupon: polite, tired, and already checking the fine print. The Defense Department can call the Oracle agreement a savings plan because it replaces scattered software purchases with one enterprise deal. That may reduce duplication. It does not magically reduce the number of questions attached to a very large bill.

    Federal News Network reports that the agreement could run for 10 years and reach up to $7 billion. The first five-year period is valued at $3.3 billion, with a possible extension worth another $3.6 billion. The Pentagon projects at least $441 million in savings through consolidation. Important word there: projects. That is a forecast, not a check cleared by reality.

    There is nothing inherently foolish about buying software in a more organized way. A government that discovers it has been purchasing the same digital wrench from several counters might reasonably try using one counter. But procurement efficiency and public accountability are different departments, even if both occupy the same enormous federal building. A cheaper arrangement should be demonstrated through verified costs, usable performance, renewal terms, and transparent oversight—not merely announced with the confidence of a man who has found a coupon for 40 percent off a yacht.

    The concentration matters because one vendor could receive a decade-long revenue runway while taxpayers are asked to trust the savings math. That is not evidence of wrongdoing, favoritism, or an illegal contract. It is evidence that a large, centralized commitment deserves more than a victory lap. When government replaces several smaller purchases with one giant agreement, it may simplify billing while increasing dependence on a single supplier. Follow the invoice, then follow the exit door. Someone should know what leaving would cost.

    Washington has apparently placed the projected savings in one column, the potential $7 billion commitment in another, and left the accountability column for the public to fill in with a pencil. The Pentagon may have cleaned up the invoice. Taxpayers still need to know whether the savings survive contact with delivery, renewals, upgrades, and the fine print. A tidier bill is not proof of accountable value; it is simply a tidier bill waiting for an audit.

  • |

    War’s Bill, Contracts’ Paycheck

    ByPhil McCracken

    Follow the invoice and the slogan starts cracking: “war for us” becomes kids, taxes, debt, underfunded veterans’ care, and families getting squeezed—while the other half of the ledger is defense contracting, framed like unavoidable “billions guaranteed.” The pitch is shared sacrifice; the receipts are selective comfort. Somewhere, “security” turns into a subscription plan with upsells for people who don’t have to carry the weight of the consequences.

    And that’s the part I can’t stop seeing on Capitol Hill: the country pays like it’s a community project, then procurement jazz hands the payout into someone else’s bank account. People pay the price. The connected profit. So whose “we” are we talking about—ours, or theirs?

End of content

End of content