ORKA Dock: Product launch in Germany

Development and reported outcome

CiS formally introduced the ORKA Dock at the Combined Naval Event on May 19 after validating it aboard FLANQ's moving Q-RECON 24 USV during SeaSEC. During the two-week trial, the system automatically launched and recovered the ORKA UAV while the USV was underway at speeds of up to 15 knots. CiS stated that it was moving the system toward full-scale production following the operational validation. (cis-rostock.de)[S1] [S2]

Program, platform and stakeholders

Programme or contract: ORKA Dock. Platform or product: ORKA Dock for FLANQ Q-RECON 24 and other moving USVs. Platform classification: Medium (host Q-RECON24: 7.3 m). Recorded supplier, developer or relevant organization: CiS GmbH (reported headquarters/country: Germany). Recorded customer, operator or intended user: Naval, coastguard and maritime-security customers; no named buyer.[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: Persistent Air-Surface ISR / Autonomous Launch & Recovery. Operating mode: Autonomous Surface Vessel (ASV).

Contract, value and shipment signals

Recorded quantity, delivery, demonstration or volume signal: 1 product family. Delivery schedule, procurement window or milestone status: Product introduced May 19; transition toward full-scale production announced.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: CiS launched ORKA Dock on May 19 after demonstrating autonomous UAS launch/recovery from a moving FLANQ Q-RECON24 USV. Retained as a USV-specific integrated subsystem launch.

Interpretation boundary: A product launch does not, by itself, establish paid orders or operational deliveries.[S1] [S2]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — product unveiling / launch: The Germany USV record for ORKA Dock is best treated as a product availability signal. A launch broadens the visible product offering but does not, without buyer evidence, establish demand or market penetration.

Traceability for buyers: The dataset associates CiS GmbH with Naval, coastguard and maritime-security customers; no named buyer for ORKA Dock for FLANQ Q-RECON 24 and other moving USVs. 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 Persistent Air-Surface ISR / Autonomous Launch & Recovery, the relevant next proof points are marine mission suitability, payload integration and measurable delivery or service outcomes. Seek customer orders, reliable specifications, deliveries and repeat purchases rather than counting exhibited units as sales.[S1] [S2]

Quantitative evidence, calculations and limits

Quantity/scope signal: 1 product family. Counting rule: Reported quantity or scope; article-level stage classification determines whether it is a platform, service, component or prospective count. Delivery/timing evidence: Product introduced May 19; transition toward full-scale production announced. Scheduling language is not independently proof of completion or acceptance.

Keep reported, derived and prospective quantities separate; do not convert activity into installed-base counts without a shipment or acceptance source.[S1] [S2]