TALOS vs Competitor BMS Solutions¶

This page compares TALOS against leading Battlefield Management System (BMS) and situational awareness products. TALOS is part of the LDM SDK — an open, extensible, cross-platform C++20/Qt6 toolkit built for GVA-compliant military vehicles, but equally deployable at a fixed base or on a soldier's device.

Why TALOS?¶

Before the feature-by-feature comparison, the differentiators that matter most for a military programme:

Capability	What it means
Native GVA support	Built on DEF STAN 23-009 GVA from the ground up. TALOS renders directly inside the ATLAS HMI as a third-party session, with full bezel-button control — no wrappers, no emulation.
Vehicle, Base, and Soldier	A single codebase runs on an armoured vehicle crew station (ATLAS HMI), a fixed command post (standalone), or a soldier handheld (Android). No separate products to license or integrate.
Plug-in, data-agnostic architecture	Data connectors (AIS, ADS-B, CoT, NMEA, weather, custom feeds) are discrete, swappable modules. Adding a new data source does not require changes to the core mapping engine.
Cross-platform: Windows · Linux · Android	A Qt6/C++20 build tree produces native binaries on all three platforms from the same source. There is no managed runtime penalty, no browser dependency, and no hidden OS lock-in.
Offline-first, no cloud dependency	The integrated tile server (`gva-tile-server`) caches 50+ open-data map sources before a mission. Operations continue with full map fidelity in a fully air-gapped environment.
Commercial SDK with full source delivery	Full source is delivered under a commercial licence, enabling integrators to inspect, build, and audit every component — critical for TEMPEST and supply-chain assurance requirements.

Feature Comparison Matrix¶

Feature	TALOS	Arcacia Systems	Andril Lattice	Sitaware	ATAK
GVA / DEF STAN 23-009 compliant	✅ Native	❌	❌	❌	❌
Vehicle crew-station HMI integration	✅ ATLAS HMI	Limited	Limited	❌	❌
Standalone base / command-post mode	✅	✅	✅	✅	✅
Soldier / handheld deployment	✅ Android native	❌	❌	Limited	✅ (Android)
Windows support	✅	✅	❌	✅	Limited
Linux support	✅	❌	Limited	Limited	❌
Android support	✅	❌	❌	❌	✅
Offline-first (no cloud required)	✅ Built-in tile server	Partial	Partial	Partial	Partial
Military symbology (APP-6D / MIL-STD-2525D)	✅	✅	✅	✅	✅
AIS vessel tracking	✅	Limited	❌	Limited	Plugin
ADS-B aircraft tracking	✅	Limited	❌	Limited	Plugin
CoT (Cursor-on-Target)	✅	✅	✅	✅	✅
NMEA GPS	✅	✅	✅	✅	✅
SAPIENT (autonomous sensor abstraction)	✅ Native IDL	❌	❌	❌	❌
SPx RADAR (Cambridge Pixel)	✅ Connector	❌	❌	❌	❌
Link 16 / VMF	Via DDS gateway	Limited	Limited	Limited	Limited
ASTERIX (ATC surveillance)	Via DDS gateway	❌	❌	❌	❌
Live weather overlays	✅ RainViewer	❌	❌	❌	Plugin
Plug-in / extensible data connectors	✅ SDK API	Limited	Limited	❌	Plugin ecosystem
DDS pub/sub integration	✅ AstuteDDS	❌	❌	❌	❌
Full source delivery (commercial licence)	✅	❌	❌	❌	✅ (open-source)
C++ native (no managed runtime)	✅	❌	❌	❌	❌
Single licence, all deployment roles	✅	❌	❌	❌	❌

Ratings reflect publicly available information. "Limited" indicates partial or third-party-dependent support. Contact Astute Systems for a detailed technical assessment against a specific programme requirement.

Deployment Roles¶

TALOS is designed from the outset for three distinct deployment contexts — covered by a single codebase and a single licence:

Vehicle (Armoured Crew Station)¶

TALOS runs as a GVA third-party extension inside the ATLAS HMI, rendering on the BMS functional-area screen with full bezel button support (F1–F12). It receives position, threat, and system data over the vehicle DDS backplane using AstuteDDS, with no additional gateway or translation layer.

Competing products that were not designed for GVA typically require a custom integration wrapper, a separate display computer, or a compromise of the GVA partitioning model. TALOS avoids all of these by being a native GVA citizen.

Base / Command Post¶

In standalone mode (--standalone) TALOS presents floating toolbars, draggable semi-transparent panels, and live data-source toggles. It runs on a standard Windows or Linux workstation with no additional runtime dependencies. The same tile server used on the vehicle provides offline map data for the command post, ensuring map consistency across the force.

Soldier / Dismounted¶

The TALOS Qt6 codebase cross-compiles to Android (arm64-v8a). Soldiers carry the same map picture, the same symbology standard (APP-6D), and the same data feeds as the vehicle crew — without a separate product or a separate data model.

This contrasts with ATAK, which is Android-only and carries the overhead of the Android platform and plugin ecosystem for capabilities that TALOS provides natively on all three platforms.

Competitor Notes¶

Arcacia Systems¶

Arcacia produces capable BMS products for command-post environments on Windows. However, it does not integrate natively with GVA vehicle systems, has no published Linux port, and requires proprietary server infrastructure for its collaborative features. TALOS replaces the Arcacia stack on the vehicle and at the command post, using a single data model and a single licence tier.

Andril Lattice¶

Andril Lattice focuses on data-link aggregation and common operating picture tools. Its strength is in high-echelon headquarters integration, not in ruggedised vehicle crew-station delivery. Andril has no native Linux or Android client, and its extensibility model targets enterprise API integration rather than embedded vehicle software. TALOS complements or replaces Lattice at the vehicle and soldier layer while feeding data upward to HQ systems via CoT or other standard connectors.

Sitaware (Systematic)¶

Sitaware is a mature, NATO-fielded BMS with strong C2 capabilities. Its deployment model is heavyweight: it requires the Sitaware server stack, specific operating system configurations, and managed clients. There is no native GVA vehicle integration, and the system is not designed for disconnected or austere environments without significant pre-deployment configuration. TALOS provides a lighter, vehicle-native alternative that does not depend on server availability and integrates directly with the vehicle's DDS backplane.

ATAK (Android Team Awareness Kit)¶

ATAK is an open-source Android application with a large plugin ecosystem, widely used by dismounted forces. Its strengths — open ecosystem, familiar Android UX, broad connector support — are also its limitations on a vehicle crew station: Android is not a GVA-compatible operating system, ATAK has no native Linux or Windows port, and the plugin model adds integration overhead for each new data source. TALOS provides equivalent or superior mapping and CoT capability on Android as well as on Linux (vehicle) and Windows (command post), without requiring the Android platform at all three nodes.

GVA Integration: A Deeper Look¶

The Generic Vehicle Architecture (DEF STAN 23-009) defines a strict partitioning model for vehicle systems. Applications run as third-party sessions within a GVA-compliant HMI, accessing data exclusively through the DDS backplane. This means:

A BMS that was not designed for GVA cannot be "bolted on" without a custom gateway.
GVA defines specific functional-area screens (SA, BMS, WPN, DEF, DRV, SYS, COM, STR); a BMS must register correctly to appear on the right screen.
Bezel buttons are routed through the HMI; a non-native application must emulate this to provide a compliant crew interface.

TALOS handles all of this natively. The gva-app-bms binary:

Registers with the gva-registry service using the GVA resource model.
Publishes a ThirdPartySession DDS topic that the ATLAS HMI discovers automatically.
Receives bezel-button events over DDS and maps them to map controls (zoom, layer toggle, symbol drop).
Renders to the BMS functional-area screen without additional configuration.

No competitor product reviewed above provides this level of GVA integration out of the box.

Extensibility and Data Agnosticism¶

TALOS connectors are discrete, independently compiled modules. Each connector implements a small interface and emits data as Qt signals that the map engine subscribes to. Adding a new data source — for example, a proprietary Link 16 receiver or a custom sensor feed — requires:

Writing a connector class that parses your data format.
Emitting standardised track or point events.
Registering the connector at startup.

The map engine, symbology renderer, layer manager, and HMI integration are entirely unaffected. This contrasts with closed BMS products where data ingestion is tightly coupled to the proprietary data model, requiring vendor involvement to add new sources.

The same extensibility applies to map tile sources: the tile server configuration accepts any XYZ or WMTS-compatible source, and custom military chart providers can be added without modifying the core.

Summary¶

TALOS is the only BMS product in this comparison that:

Is native GVA (DEF STAN 23-009) without a custom integration layer
Runs on Windows, Linux, and Android from a single C++20 codebase
Covers vehicle, base, and soldier deployment with a single licence
Provides offline-first map delivery with a built-in tile server
Delivers full source under a commercial licence for programme assurance and supply-chain auditability

For programme enquiries, integration support, or a live demonstration, contact Astute Systems.