08/KPW/TO/2026; TED 336995-2026: Poland procurement notice

Development and reported outcome

On May 18, 2026, KPW Świnoujście launched procurement 08/KPW/TO/2026 for the five-year periodic overhaul of three portable OPM Głuptak mine-countermeasure systems. The scope covers inspection, repair, restoration, and verification of the remotely controlled vehicles in combat and training configurations. The phrase 'five-year repair' describes the periodic maintenance cycle, while the procurement itself anticipated approximately six months of execution and later produced a July contract.[S1] [S2]

Program, platform and stakeholders

Programme or contract: 08/KPW/TO/2026; TED 336995-2026. Platform or product: Portable OPM Głuptak systems. Platform classification: Remotely Operated Vehicle. Recorded supplier, developer or relevant organization: Komenda Portu Wojennego Świnoujście (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

Recorded quantity, delivery, demonstration or volume signal: 3 systems. Delivery schedule, procurement window or milestone status: Planned six-month repair period.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: The procurement concerns three existing portable Głuptak systems. 'Five-year repair' is the maintenance-cycle designation, not a five-year contract duration.

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 08/KPW/TO/2026; TED 336995-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 Świnoujście with Polish Navy for Portable OPM Głuptak systems. 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: 3 systems. Counting rule: Requested scope; not a delivery or award total. Delivery/timing evidence: Planned six-month repair period. Scheduling language is not independently proof of completion or acceptance.

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