The Royal Netherlands Navy (RNLN) has successfully tested and demonstrated a new software system designed to integrate maritime uncrewed systems (MUS) command-and-control (C2) capability. The successful work included using the software to integrate MUS systems with each other and with the combat management system (CMS) onboard the navy\u2019s crewed platforms.<\/strong><\/p>\n The MUS-focused C2 system is called IDUS (Intelligent Distribution of Unmanned Systems). It is a Dutch-made, bespoke software family consisting of several different elements. During the tests and demonstrations, it integrated with a standalone version of the navy\u2019s CAMS\/Force Vision Guardion CMS \u2013 another indigenously developed C2 product.<\/p>\n The IDUS test and demonstration activity occurred in June, during a month-long maritime uncrewed sea trials (MUST) series, conducted from the RNLN\u2019s Den Helder base, that was designed to prove the capabilities and integration of the navy\u2019s new maritime uncrewed task force (MUTF) construct.<\/p>\n \u201cThe main focus for this edition of the MUST series was to prove our software system,\u201d<\/em> Captain Sjoerd Feenstra, head of the RNLN\u2019s uncrewed systems expertise centre, told Naval News<\/em>, onboard the Netherlands\u2019 research vessel MV Geosea<\/em>, during a media day at the conclusion of the MUST activities. The software is designed to manage uncrewed system use, across tasks ranging from autonomous operations to swarming. \u201cThe main goal was to prove that everything we have developed is actually working with the assets at sea in all three domains [air, surface, and sub-surface],\u201d<\/em> said Capt Feenstra.<\/p>\n IDUS has been developed across recent years, and was tested at the Portuguese Navy\/NATO co-hosted \u2018REPMUS\u2019 exercise, in southern Portugal in September 2025. At \u2018REPMUS\u2019, the testing included having two uncrewed aerial vehicles (UAVs) deployed and tasked by another uncrewed system using the software. Following further software development since, for MUST the aim was to test IDUS capability across all three domains; activities included simultaneously ordering and tasking assets from each domain, which were operating in a set area, to work together to complete a mission, Capt Feenstra explained. \u201cYes, we managed to do it,\u201d<\/em> he added.<\/p>\n In this activity, IDUS was also integrated into the Guardion CMS, Capt Feenstra continued. With the CMS deployed widely across the RNLN\u2019s fleet, and with the navy seeking to integrate MUS in all domains and tasks across the fleet\u2019s operations, the navy needs IDUS to be a core Guardion application.<\/p>\n These initial integration steps involved the standalone Guardion version used for MUST. This allowed RNLN operations room personnel in the exercise to create and inject missions and assign MUS assets to them, Capt Feenstra explained.<\/p>\n \u201cSo, we now know that we can actually connect IDUS to Guardion. That has been proved to work over these past five weeks,\u201d<\/em> Capt Feenstra said. Achieving this integration was another primary goal in the MUST process, he added, with the speed of software development for such systems, including harnessing artificial intelligence, being so significant that getting ahead in this field of work is a main focus.<\/p>\n According to the RNLN, the MUST process is designed to help accelerate innovation plus the implementation of new concepts across the fleet, in turn to help prepare the navy for an operational future requiring greater combat power.<\/p>\n The geographical area where MUST took place is also operationally significant for NATO. The North Sea is home to vital maritime infrastructure and access points: the former including critical undersea infrastructure (CUI) on the seabed like oil and gas pipelines, alongside critical national infrastructure on the surface like windfarms; and the latter including chokepoints like the Dover Strait (connecting the English Channel and the North Sea) and the Kattegat\/Skagerrak Straits (connecting the North and Baltic seas).<\/p>\n Thus, the RNLN and other NATO navies have a requirement in this area for the sustained presence and surveillance MUS can bring.<\/p>\n Run by the RNLN and the maritime systems department of the Netherlands\u2019 Ministry of Defence\u2019s (MoD\u2019s) Materiel and IT Command (COMMIT),the MUST trials saw a range of MUS involved across the domains, including:<\/p>\n The Damen patrol vessel DSS Galatea<\/em> was deployed as an at-sea C2 centre. Illustrating the RNLN\u2019s transition towards developing a \u2018hybrid\u2019 force structure integrating crewed and uncrewed platforms, the navy\u2019s amphibious ship HNLMS Johan de Witt<\/em> supported the trials.<\/p>\n According to the RNLN magazine All Hands<\/em>, the trials included the requirement to use MUS to locate, monitor, and track a vessel of interest, encompassing intelligence, surveillance, and reconnaissance (ISR) tasking. One feature of the trials was the USVs sailing in autonomous formations.<\/p>\n For the RNLN, its focus in integrating crewed and uncrewed systems is about generating operational effects across seven warfare areas: naval mine warfare; anti-submarine warfare; integrated air and missile defence; littoral\/amphibious operations; maritime special operations; maritime strike; and territorial protection (including of the North Sea and the Dutch Caribbean). \u201cFor each of these areas, we have described the concept of how to deliver the required effect,\u201d<\/em> Capt Feenstra told Naval News<\/em>. In each instance, this includes defining how MUS in all domains combine to deliver that effect. The navy is not describing what type of system it needs, but rather what effects are needed to deliver what task, and thus how relevant systems should contribute to this, he explained.<\/p>\n Reflecting the need to stay ahead of the requirement, Capt Feenstra described the next steps in developing the MUS systems and their enabling software.<\/p>\n These new objectives encompass integrating the systems more fully into operational settings and scenarios. \u201cGetting these systems as close as we can to actual operational deployment, that\u2019s what we\u2019re going to identify next,\u201d<\/em> Capt Feenstra said. \u201cWe want to bring the systems forward to actually being implemented and participating in their first sets of operational exercises.\u201d<\/em> Such exercise opportunities could include \u2018REPMUS 26\u2019, plus working with close allies like Norway and the UK at bilateral levels.<\/p>\n The RNLN\u2019s MUTF concept was launched in late April, including with the publication of the navy\u2019s Future Vision: Maritime Uncrewed<\/em> document.<\/p>\n The document prescribed the navy\u2019s approach for harnessing MUS capability, which will see the navy transition from fully crewed platforms to a fleet of more lightly crewed platforms paired with uncrewed \u2013 remotely operated, and autonomous \u2013 systems.<\/p>\n As described in the document, a central aim of the navy\u2019s MUTF requirement is to accelerate MUS development and deployment.<\/p>\n Such acceleration will be enabled by collaboration with partners too, such as the UK.<\/p>\n The recently announced Netherlands\/UK plan to build future amphibious transport ships (ATS) together illustrates how collaboration can expand options for deploying MUS capability going forward, and underscores how the \u2018crewed\/uncrewed\u2019 combination helps operationalise \u2018hybrid\u2019 force structures.<\/p>\n![\"\"](\"https:\/\/www.navalnews.com\/wp-content\/uploads\/2026\/07\/NavNews-MUTF2-Geosea-USVs-NL-MoD-1024x683.jpg\")
\n<\/picture>MUST requirement<\/strong><\/h2>\n
\n
Pacing ahead<\/strong><\/h2>\n
Naval News<\/em> comment<\/strong><\/h2>\n