Tactical Control & Connectivity

NOMAD Tactical Robotic C2

One Operator. Any Standard C2I. Mixed Fleet.

Part of Tactical Control & Connectivity — also see Tactical Video & Teleoperation Suite

Overview

What the NOMAD Tactical Robotic C2 does

A tactical C2I autonomy gateway that sits beneath an existing command system and connects mixed UAV, UGV and quadruped fleets.

NOMAD is a tactical C2I autonomy gateway for heterogeneous unmanned fleets. It sits beneath ATAK, TAK, another CoT-based C2I or a customer interface; translates MAVLink, STANAG 4818, ROS 2, CoT, STANAG 4609 and vendor APIs; and maintains one shared mission picture for UAVs, UGVs and quadruped robots.

NOMAD is not another operator station. It is the integration and autonomy layer beneath the C2I already in use, connecting air, ground and legged robots while preserving one named control owner for each platform.

Platform adapters normalize video, telemetry, metadata, targets and tasking. A target received from STANAG metadata or designated by an operator becomes a common track that can be handed from a UAV to a UGV or robotic dog in the receiving platform's own protocol.

Protocol and modem adapters keep the C2I layer stable as the fleet changes. NOMAD supports RF, SATCOM and cellular transports, and keeps video off the command path so mixed fleets can operate as a coordinated hybrid swarm.

Capabilities

Core capabilities

  • Multi-platform control of air and ground assets
  • Mission assignment by intent
  • Multi-robot coordination and teaming
  • Swarm and hybrid-swarm mission coordination
  • Automatic data sharing between assets
  • Video sharing across operators
  • Target sharing and cross-cueing
  • Common operational picture with live positions
  • Platform health and mission status
  • Human-on-the-loop supervision and approval
  • ATAK and third-party C2 interoperability
  • One named control owner per platform
  • Video separated from the command path
  • Extensible protocol and modem adapters

How it works

How the NOMAD Tactical Robotic C2 works

From sensor input to actionable output in four steps.

Step 01

Connect assets and sensors

UAVs, UGVs and robotic dogs connect through MAVLink, STANAG 4818, ROS 2 or vendor adapters while ATAK, TAK or another C2I remains the operator picture.

Step 02

Build a shared operational picture

NOMAD normalizes video, telemetry, metadata, targets and mission status into a shared operational representation.

Step 03

Task by intent

One named operator keeps control ownership of each platform while the mixed fleet carries out coordinated intent.

Step 04

Cross-cue automatically

NOMAD translates a shared target or task into the protocol understood by the receiving UAV, UGV or robotic dog.

Use cases

Where it's used

Typical situations this system is deployed in, and what it solves in each one.

One person, several robots

Drones, ground robots and robotic dogs appear on one map and are tasked from one screen, so the number of platforms does not multiply the operators.

Find with the air, check on the ground

A drone detection can be passed straight to a ground robot, which is sent to verify what was seen.

Base and perimeter defence

Fixed sensors and moving robots feed one shared picture, with live positions and status for every asset.

Working with the systems already in use

The picture and the tracks can be shared with ATAK and other existing command systems rather than replacing them.

Integration

Interfaces and integration

Built to drop into an existing architecture — standard interfaces, standard hardware, no forced replacement of fielded systems.

  • Asset interfaces: MAVLink for air vehicles, STANAG 4818 for UGV interoperability, ROS 2 for quadrupeds and vendor APIs
  • Sensors: EO/IR observation posts, ground sensors, third-party detectors
  • Interoperability: ATAK / CoT messaging, STANAG 4609 video, customer C2 APIs
  • Transport: DTC RF/mesh, Starlink BLOS SATCOM, Commtact tactical datalink, Creomagic MANET, cellular and customer IP modems
  • Deployment: on-premises and disconnected; no cloud dependency required

FAQ

Common questions about the NOMAD Tactical Robotic C2

Plain-language answers for integrators, procurement teams and operators.

How many robots can one operator supervise?
NOMAD is designed so one operator can task and monitor multiple heterogeneous air and ground assets through a single interface.
Does it require a cloud connection?
No. NOMAD deploys on-premises and in disconnected environments; no cloud dependency is required.
Can it integrate with ATAK?
Yes. NOMAD uses CoT messaging and can share tracks, video and the common operational picture with ATAK and other customer C2 systems.
What is human-on-the-loop supervision?
The operator assigns intent and approves key decisions, while the platforms execute autonomously. The human remains in command without manually piloting every action.
Does it support robotic swarming?
Yes. NOMAD coordinates swarm and hybrid-swarm missions where multiple platforms share a task and act as a team.
What assets work with NOMAD?
NOMAD connects UAVs over MAVLink, UGVs through STANAG 4818 or platform adapters, quadruped robots through ROS 2, and additional systems through vendor APIs.
Does NOMAD replace our existing C2I or operator station?
No. NOMAD sits beneath ATAK, TAK, other CoT-based C2I systems, vendor stations or a customer interface. New platforms are added through adapters without changing the C2I layer.
Which tactical networks and modems can NOMAD use?
The supplied integrations include DTC RF/mesh, Starlink BLOS SATCOM, Commtact tactical datalink, Creomagic MANET and 5G/LTE backup. Other IP modems can be added through an adapter.
How does NOMAD prevent control conflicts in a hybrid swarm?
NOMAD maintains one named control owner for each platform, preserving a human lock on assets that must remain manned while mixed platforms share the mission picture.

Discuss your platform and mission

Tell us the platform, sensor and mission. We will walk you through integration options and arrange a technical demonstration.