OSKAR – Opracowanie Systemu Kontroli Autonomicznego Roju: Poland contract and delivery record

Development and reported outcome

On 23-Jul-26, Łukasiewicz-PIMOT advanced OSKAR – Opracowanie Systemu Kontroli Autonomicznego Roju, an R&D, requirements or institutional milestone focused on Autonomous UGV swarm-control system for Polish Armed Forces / MON via NCBR PERUN.[S1]

Program, platform and stakeholders

Programme or contract: OSKAR – Opracowanie Systemu Kontroli Autonomicznego Roju. Platform or product: Autonomous UGV swarm-control system. Recorded supplier, developer or relevant organization: Łukasiewicz-PIMOT (reported headquarters/country: Poland). Recorded customer, operator or intended user: Polish Armed Forces / MON via NCBR PERUN (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: Swarm / collaborative autonomy; multi-robot control. Operating mode: Fully Autonomous.

Contract, value and shipment signals

Original reported amount or scope: PLN 13.4 million funding. Original-currency label: PLN. Recorded quantity, delivery, demonstration or volume signal: R&D programme; quantity not disclosed. Delivery schedule, procurement window or milestone status: R&D programme initiated; detailed delivery dates not disclosed. Recorded contractual start: 23-Jul-26.[S1]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Official NCBR-funded programme; value is R&D funding, not procurement of physical UGV units.

Interpretation boundary: The source-specific record should be used to distinguish award, arrival, commissioning and completed delivery; these stages are not interchangeable.[S1]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — contract / recorded award outcome: The Poland UGV record for OSKAR – Opracowanie Systemu Kontroli Autonomicznego Roju is best treated as a committed commercial activity signal. The recorded award or contract is a stronger transaction signal than a tender; the amount and quantity still need separation into platforms, accessories, support and services.

Traceability for buyers: The dataset associates Łukasiewicz-PIMOT with Polish Armed Forces / MON via NCBR PERUN for Autonomous UGV swarm-control system. 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 Swarm / collaborative autonomy; multi-robot control, the relevant next proof points are ground mobility, autonomy, payload integration and field acceptance. Watch for acceptance or delivery reports, contract modifications and whether the stated amount covers equipment or ancillary work.[S1]

Quantitative evidence, calculations and limits

Financial signal (master transcription): PLN 13.4 million funding. Classification: Financial context as recorded in the master; scope and contract status must follow the underlying source. Quantity/scope signal: R&D programme; quantity not disclosed. Counting rule: Order/award context; not proof that hardware has shipped or entered service. Delivery/timing evidence: R&D programme initiated; detailed delivery dates not disclosed. Scheduling language is not independently proof of completion or acceptance.

Any volume or value must stay tagged to its awarded work package; mixed services, components and platform counts cannot be consolidated as vehicle deliveries.[S1]