27/KPW/BP/2026; GAVIA servicing 2026-2028: Poland procurement notice

Development and reported outcome

On March 10, 2026, KPW Gdynia opened a restricted defence procurement for servicing Polish Navy GAVIA autonomous underwater vehicle systems during 2026-2028. The requirement concerns repair, maintenance, and technical availability of the existing autonomous fleet rather than acquisition of additional vehicles. Applications were due March 31, and the procurement later progressed to a multi-year contract with Enamor on June 8.[S1] [S2]

Program, platform and stakeholders

Programme or contract: 27/KPW/BP/2026; GAVIA servicing 2026-2028. Platform or product: GAVIA AUV. 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; Sustainment / Combat Readiness.

Contract, value and shipment signals

Original-currency label: PLN. Recorded quantity, delivery, demonstration or volume signal: Service covering existing GAVIA AUVs; fleet quantity not disclosed. Delivery schedule, procurement window or milestone status: Multi-year support requirement \| Bid/application deadline: Mar. 31, 2026.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: MILMAG directly dates the procurement launch to March 10, correcting the previous March 2 working date. This is a service tender for the existing GAVIA fleet.

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 27/KPW/BP/2026; GAVIA servicing 2026-2028 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 GAVIA AUV. 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; Sustainment / Combat Readiness, 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: Service covering existing GAVIA AUVs; fleet quantity not disclosed. Counting rule: Requested scope; not a delivery or award total. Delivery/timing evidence: Multi-year support requirement \| 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]