47/KPW/BP/2026: Poland procurement notice

Development and reported outcome

On April 9, 2026, KPW Gdynia opened procurement 47/KPW/BP/2026 for training Polish Navy users in operation and employment of the HUGIN autonomous underwater vehicle system. The requirement covers one training service supporting readiness of an existing AUV capability rather than purchase of another HUGIN vehicle. Applications were due April 17, and the procurement later progressed to an award-stage notice on April 28.[S1]

Program, platform and stakeholders

Programme or contract: 47/KPW/BP/2026. Platform or product: HUGIN AUV user training. Platform classification: Autonomous 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]

Mission and technical scope

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

Contract, value and shipment signals

Original-currency label: PLN. Recorded quantity, delivery, demonstration or volume signal: 1 training service.[S1]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Official KPW procurement page supports the April 9 tender and April 17 deadline. One training service is being procured; no additional HUGIN vehicle is being acquired.

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

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — procurement requirement / tender: The Poland UUV record for 47/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 HUGIN AUV user training. 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 Training / Combat Readiness; 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]

Quantitative evidence, calculations and limits

Quantity/scope signal: 1 training service. Counting rule: Requested scope; not a delivery or award total.

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