22/KPW/BP/2026: Poland procurement notice

Development and reported outcome

On March 10, 2026, KPW Gdynia opened a defence procurement for spare parts supporting the Polish Navy's Głuptak mine-countermeasure system. The requirement supports the existing remotely controlled Głuptak vehicle fleet and does not constitute procurement of new vehicles or explosive payloads. Applications were due March 31, and a separate fleet-support contract with Gdańsk University of Technology followed on June 10.[S1] [S2]

Program, platform and stakeholders

Programme or contract: 22/KPW/BP/2026. Platform or product: Głuptak. Platform classification: Remotely Operated Vehicle. Recorded supplier, developer or relevant organization: Komenda Portu Wojennego Gdynia (reported headquarters/country: Poland). Recorded customer, operator or intended user: Polish Navy (reported headquarters/country: Poland).[S1] [S2]

Mission and technical scope

The following are classifications recorded in the source master, not additional claims of operational deployment: Mission/use-case classification: Mine Neutralization / EOD; Mine Countermeasures.

Contract, value and shipment signals

Original-currency label: PLN. Recorded quantity, delivery, demonstration or volume signal: Spare-parts requirement; vehicle quantity not stated. Delivery schedule, procurement window or milestone status: Spare-parts procurement \| Bid/application deadline: Mar. 31, 2026.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: The procurement launch date is corrected to March 10. This row covers Głuptak spare-parts sustainment and remains distinct from later contract-signing and five-year repair-cycle records.

Interpretation boundary: The tender, notice or request stage does not by itself prove a signed contract, selected supplier, or physical delivery.[S1] [S2]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — procurement requirement / tender: The Poland UUV record for 22/KPW/BP/2026 is best treated as a procurement pipeline signal. A published requirement can indicate addressable demand, but it is not an award, supplier revenue, shipment, or fleet increase.

Traceability for buyers: The dataset associates Komenda Portu Wojennego Gdynia with Polish Navy for Głuptak. This supports stakeholder mapping; supply-chain tier, exclusivity and signed-customer relationships need the underlying source before firm classification.

Client-use interpretation: For intelligence users tracking Mine Neutralization / EOD; Mine Countermeasures, the relevant next proof points are mine-countermeasures requirements, autonomy integration and acceptance milestones. Track the award notice, signed value and accepted delivery quantities before upgrading this demand signal.[S1] [S2]

Quantitative evidence, calculations and limits

Quantity/scope signal: Spare-parts requirement; vehicle quantity not stated. Counting rule: Scope or component count; not a count of procured or delivered unmanned platforms. Delivery/timing evidence: Spare-parts procurement \| Bid/application deadline: Mar. 31, 2026. Scheduling language is not independently proof of completion or acceptance.

Quantified requirements are potential procurement scope, not realised hardware orders or sales.[S1] [S2]