IT EN
Start a trial

Operational notes Observatory

When the tender document already names the product: the Anduril Pulsar-L case on the Marines’ ACV

7 min read

A sliver of sky between two adjoining tower blocks, an elevated walkway crossing it high up, black-and-white photograph
The space the solution has to fit into — without being told its dimensions.

On 3 August 2026 the Program Manager Advanced Amphibious Assault (PM AAA), within the Portfolio Acquisition Executive – Marine Corps, published notice M67854-26-I-0225 on SAM.gov: intent to sole source the C-sUAS (counter-small Unmanned Aerial Systems) packages for the Amphibious Combat Vehicle (ACV). Supplier: Anduril Industries. Product: the Pulsar Lite MKI-RX/TX 4CH (“Pulsar-L”). It is also a sources sought: anyone with an alternative has until 18 August to prove it. The case matters not for the outcome — likely, defensible — but for how the exclusivity took shape.

The facts

The award is justified “in accordance with 10 U.S.C. §3204 (a)(1), as implemented by… FAR 6.103-1”: only one responsible source, for the Pulsar-L and its accessories, as a Firm-Fixed-Price order under an IDIQ contract for Non-Developmental Items. The passage that matters most: the Marine Corps Capabilities Development Directorate points to an enclosure with the materiel requirement, concept of employment and distribution plan that “identifies the Anduril Pulsar-L as the only viable solution”. It is not the contract that picks the supplier: it is the requirement document, written earlier, that leaves only one box to tick.

The threshold requirements call for a combined omnidirectional sensor-and-jammer package against Group 1 and 2 UAS reliant on GNSS and RF, detection from two to five kilometres, a jamming trigger at 2 km, simultaneous engagement whether the ACV is static or moving, within the vehicle’s size, weight and power constraints. The objective: one box, no more than 35 lbs fully integrated. Required capacity: over fifty packages within twelve months, deliveries from Q1 FY2027.

One constraint is nowhere on the page: “The solution must not exceed the limited amount of space claim nor weight claim available in the ACV FoV… The Government will not disclose the threshold requirements of either the space claim or weight claim.” You must fit a space with no stated measurements: whoever has already integrated a system on that vehicle knows them; whoever starts from zero has to guess. A precedent propagates: “The Army’s existing contracts for vehicular C-sUAS solutions incorporates the Anduril Pulsar-L Packages… with an Other Than Full and Open Competition Justification and Approval (JA-26-DC3oE-0038) dated 05 March 2026.” An exclusivity approved elsewhere becomes the argument for the next one.

Anyone with an alternative must submit, by 18 August, an executive summary of no more than five pages: identity, CAGE, UEI, business size under NAICS 334511, a point-by-point response to the requirements. Unmarked proprietary information is not presumed to be so. Recipients: Contracting Officer Jessica Hathaway and Contract Specialist Matthew Mercer, at Quantico. A practical note: within the same line the text gives two times for the same deadline, “10:00 AM local time” and, immediately after, “1500 Local Time”. Aim for the tighter one.

On 3 June 2026 the same office had published a different notice, M67854-26-I-0175 (deadline 18 June, archived 3 July), citing “10 U.S.C. §3204 (a)(2)… FAR 6.302-2(a)(2)”: “Anduril is the original designer, developer, and producer of the Pulsar-L and the platform cannot be procured from any other source without risk of serious injury to the Government and its interests.”

These are two different doors: §3204(a)(2), June’s, is unusual and compelling urgency; §3204(a)(1), August’s, is only one responsible source. The FAR treats them differently on one point: FAR 6.103-2(c), on urgency, sets that the period of performance “may not exceed one year, including all options, unless the head of the agency determines that exceptional circumstances apply” — a one-year cap. FAR 6.103-1 imposes no equivalent cap. We do not know why the legal basis changed between June and August, and we will not speculate. We write what changes in the text: a door with a deadline, one without.

A note on numbering: 6.103-x is the FAR Overhaul’s, the rewrite of Part 6 under way; the codified FAR in force today still numbers the same cases 6.302-1…6.302-7, which is what June’s notice cites. Searching for “FAR 6.103-1” there finds nothing.

What the FAR says about who has to read those five pages

A sources sought is not a courtesy. 6.103(c) requires soliciting offers from as many sources as practicable. 6.103(d) requires considering all capability statements received, and the justification of 6.104 — the five pages are not a formality. 6.103(b) rules out two excuses: lack of planning, budget concerns. 6.103-1(d) names the mechanism at the heart of this piece: “specification of attributes peculiar to one manufacturer, prevents full and open competition” — unless it is “brand name or equal”, which by definition keeps competition open. Justifications are published within 14 days of award (30 for urgency) and stay public for at least 30 days (6.301).

The Italian mirror

Article 76 of the Public Contracts Code (Legislative Decree 36/2023) shares the same logic. Paragraph 1 requires the negotiated procedure to be justified “in relation to the specific factual situation and to the characteristics of the potentially interested markets” — the American sources sought is exactly this. Paragraph 2, letter b), allows a single supplier where competition is “absent for technical reasons” or for “the protection of exclusive rights”. Paragraph 3 is the line that carries the piece: it applies “only where no other economic operators or reasonable alternative solutions exist, and the absence of competition is not the result of an artificial narrowing of the procurement parameters”. An undisclosed dimensional constraint, read this way, needs a genuine technical reason. Paragraph 4, letter b), adds the propagation mechanism: complementary deliveries from the original supplier, only where switching causes “incompatibility or disproportionate technical difficulty”, and “not exceeding three years”.

The other side, owed in fairness

This is not a piece against Anduril or the Marines. An administration with a genuine capability gap on a recently fielded vehicle, buying a solution another armed service has already integrated, is behaving in an ordinary and defensible way: it does not build from scratch, does not promise dates it cannot guarantee, and still opens a window rather than proceeding in silence. None of the three elements at issue — a named product, an undisclosed constraint, a propagating precedent — is unlawful on its own: it is the sum that matters, the mechanism by which a proprietary architecture becomes a market position. The same pattern, reversed, was the core of the DIA’s ASTRA case: there the requirement was challenged for building bespoke instead of buying ready commercial; here it is written so only one commercial product fits. Same question, opposite answer: whoever writes the requirement decides the supplier.

What to take away

  1. A requirement naming a product is a sole-source award already made: “brand X or equal” is not (FAR 6.103-1(d)).
  2. An undisclosed constraint is a barrier to entry: if it cannot be published, at least publish the method to verify it — a bench test, an interface file under NDA.
  3. Urgency has an expiry — one year under the FAR, “extreme urgency not attributable to the contracting authority” in Italy — and what is bought under urgency should go back to tender, not be extended.
  4. The first integration dictates the next ones: rights to technical data and interfaces belong in the contract before first delivery.
  5. Sole-source justifications are public: they map your sector’s dependencies.
  6. For an alternative supplier the window is the market consultation, not the protest — five pages by 18 August.

The method, applied here

Does this requirement name a product? Is this constraint disclosed? Does this exclusivity hold up against Article 76, paragraph 3? That check is not a legal opinion filed away in a PDF: it is a control run over the client’s specifications before they go out, with the trail ready for an inspection, an auditor or a dispute. The same system holds together specifications, contracts, sole-source justifications, suppliers, deadlines and technical data in a single operating model, on which AI agents execute decisions with a human operator in command — for large enterprises, defence, the public sector and healthcare: a register that tells you whether the alternative exists and when the constraint expires. Always in two modes: on-premise, on autonomous machines that do not require deep integration into the client’s network, or a dedicated cloud with a data centre in Italy — always with shared management.

Need to check whether one of your specifications already names a supplier without your knowing it? The first session comes at no cost.

Sources