84/KPW/BP/2026: Poland procurement notice

Development and reported outcome

On July 14, 2026, KPW Gdynia opened defence procurement 84/KPW/BP/2026 for assembly, commissioning, and user training covering two GAVIA systems. The requirement is an integration and training service applied to two systems and does not itself establish purchase of two newly manufactured AUVs. An offer list was posted July 22, but no public award was independently validated by the research cutoff.[S1] [S2]

Program, platform and stakeholders

Programme or contract: 84/KPW/BP/2026. Platform or product: Two GAVIA AUV systems, assembly / commissioning / 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] [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 Countermeasures; Training / Combat Readiness; Mothership Integration.

Contract, value and shipment signals

Recorded quantity, delivery, demonstration or volume signal: 2 GAVIA systems covered by 1 integration/training service; not evidence of 2 new AUV purchases. Delivery schedule, procurement window or milestone status: Commissioning and training schedule not publicly resolved.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Official KPW transaction supports the July 14 integration/training requirement for two GAVIA systems. The row must not be interpreted as a separate two-AUV acquisition.

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 84/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 Two GAVIA AUV systems, assembly / commissioning / 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 Mine Countermeasures; Training / Combat Readiness; Mothership Integration, 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: 2 GAVIA systems covered by 1 integration/training service; not evidence of 2 new AUV purchases. Counting rule: Scope or component count; not a count of procured or delivered unmanned platforms. Delivery/timing evidence: Commissioning and training schedule not publicly resolved. Scheduling language is not independently proof of completion or acceptance.

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