IRIS Capability Overview.

IRIS is a resilient tactical command, control and common operating picture application designed for operations where communications are degraded, intermittent, limited or contested. It provides mapping, live situational awareness, tactical messaging, reports, video metadata overlays, track management and network bridging in a local-first, peer-to-peer architecture.

Unlike server-dependent C2 systems, IRIS is designed to operate at the tactical edge. It can distribute COP data, chat, reports, orders, files and live track updates directly between nodes without requiring central infrastructure, while still supporting gateway and bridge roles where networks need to be connected.

Mapping and Geospatial Features:

IRIS uses Esri ArcGIS technology to provide a full geospatial operating environment, 3D mapping, online and offline map sources, imagery, vector data, elevation, routing, live feeds and tactical overlays. ArcGIS supports dictionary-based military symbology, including MIL-STD-2525D, allowing IRIS to integrate standard-compliant tactical graphics and live entity rendering directly into the map environment.

Online and offline operation

IRIS supports both online map services and dedicated offline map packages. Operators can use mission-specific offline maps when disconnected, while still taking advantage of online map services when network access is available. ArcGIS supports always-connected, occasionally-connected and fully-disconnected map workflows, which aligns with IRIS’s DDIL operating model.

Supported geospatial data

IRIS can ingest and display operational geospatial data, including:

• TIFF and PNG imagery
• KML and KMZ
• GeoPackage
• Shape files
• DTED and elevation data
• Tile packages
• Raster and vector overlays
• Mission-specific offline map packages

Map tools

IRIS includes a suite of map tools for tactical planning and situational awareness:

• Free drawing of points, lines, polygons, circles, rectangles, arrows and freehand shapes
• Image insertion onto the map
• Degrees and MGRS grid display
• Distance, bearing and range measurement
• Route and direction tools using online or offline routing data
• Address search and location lookup
• Line of sight and location viewshed tools
• Range rings and range fans
• Node track history
• Map-based pointer and operator reference tools

Tactical Overlays and MIL-STD-2525D Symbology

IRIS supports the creation, editing, movement, deletion and sharing of MIL-STD-2525D tactical graphics and control measures. Operators can create tactical overlays before transmission, persist them locally and share them with other IRIS nodes where operationally required.

The symbology system supports:

• MIL-STD-2525D symbols and control measures
• Tactical graphics and overlays
• Operator-created symbols
• Persisted tactical map artefacts
• Geofence and area of interest assignment
• JSON-backed symbol selection and editing
• Live track symbology based on received or configured identity data

Live Tracks, PLI and Situational Awareness

IRIS receives and displays position location information and situational awareness data from multiple sources, including:

• Cursor on Target XML
• TAK Protobuf
• NATO Friendly Force Indicator
• Harris SA/PLI
• JSON over multicast or unicast
• GPS sources using NMEA over serial, TCP, UDP or multicast
• Local ownship position reporting
• Sensor-derived tracks and reports

Track Correlation, Decorrelation and Identity Override

IRIS includes a track correlation engine that helps manage live entities from multiple sources. This is important where the same object may be reported by several systems, or where different objects may appear similar because of duplicated callsigns, bridged networks or incomplete source identity data.

The track engine supports:

• Source-to-system-track correlation
• Multiple source UIDs mapped to a single system track
• Manual track merge
• Manual track split/decorrelation
• Negative decorrelation, preventing known-separate tracks from being re-fused
• Kinematic divergence monitoring
• Track quality scoring
• Operator-controlled callsign and SIDC override
• Shared override propagation to other IRIS nodes
• Removal of overrides to return to source-provided identity

This capability improves the reliability of the common operating picture by allowing operators to correct ambiguous or conflicting identity information without corrupting the original source data. Source identity is preserved, while the displayed operational identity can be manually adjusted and shared across the IRIS network.

Geofence and Area of Interest Tools

IRIS supports geofences and areas of interest for monitoring tactical events. A geofence is a virtual boundary around a geographic area. In IRIS, geofences can be used to monitor when tracked entities enter, exit or interact with defined areas.

Geofences and AOIs may be based on:

• Circular areas
• Polygonal areas
• Existing tactical graphics
• Map-drawn control measures
• Mission-defined operational zones

This allows operators to use tactical graphics not only as visual overlays, but also as operational triggers for relevance, alerting and monitoring.

Video and KLV Metadata Support

IRIS supports mission video playback and network video streams, including platform or drone feeds where embedded metadata is available. Where supported by the stream, IRIS can use MISB/KLV metadata to display video-derived information on the map.

KLV-enabled video support includes:

• Network video stream playback
• Mission video recording and playback
• Platform video feed selection
• KLV metadata extraction
• UAV/platform position display
• Camera line of sight
• Frame centre marker
• Sensor footprint overlay
• Chase-camera style map viewpoint
• Terrain-aware frame and line-of-sight display

This allows operators to understand not only the video image, but also where the sensor is located, where it is looking and what area on the ground is represented by the video frame.

Messaging and Collaboration

IRIS includes tactical communications tools for peer-to-peer collaboration. Message types are locally persisted to support review, retrieval and post-activity logging.

Supported messaging features include:

• Group chat
• Private point-to-point chat
• Email-style tactical messaging
• Attachments
• Reply and forward workflows
• File transfer
• OPORD
• SITREP
• OPDEM
• PRIDEM
• Surveillance reports
• Suspicious activity reports
• CASEVAC
• Message logging and retrieval

IRIS messaging is designed as a tactical network workflow, not as a dependency on internet email services. Messages can be exchanged directly between IRIS nodes and retained locally for later review.

TAK, CoT and Interoperability

IRIS supports interoperability with adjacent tactical systems and data formats, including:

• TAK CoT XML
• TAK Protobuf
• TAK GeoChat
• NATO Friendly Force Indicator
• VMF
• Harris SA/PLI
• Cursor on Target replay
• Anduril Lattice integration
• Sensor and detector inputs
• Future or expandable tactical adapter pathways

This allows IRIS to operate as a local common operating picture while still exchanging relevant data with other systems where configured.

Network Architecture and Middleware

IRIS is designed around a serverless, peer-to-peer architecture. It can connect nodes across available network interfaces and can bridge traffic between dissimilar tactical networks without requiring routers or central servers for core IRIS operation.

Network features include:

• Peer-to-peer communication
• Local and global message propagation options
• Site and network bridging
• Multicast and unicast support
• Reliable message handling
• Protobuf-based tactical message structures
• Traffic marking and quality-of-service support
• Interface-bound communication
• Optional bridge and gateway node roles
• Support for MANETs, tactical IP radios, VPNs, VLANs, WAN and SATCOM-style links

WINIDM and MIL-STD-188-220 Bridge Support (Optional)

Where required, IRIS can support WINIDM-enabled bridge bearer concepts for MIL-STD-188-220 carriage. This is intended for gateway or bridge nodes rather than ordinary user nodes.

This allows IRIS to support tactical bridge architectures where the middleware traffic must be carried across specialist radio modem or bridge paths, while still preserving a simpler local IP model for ordinary operators.

Radio and MANET Analysis

IRIS includes tools to support tactical radio and MANET planning. These tools help operators understand network reachability, terrain impacts and possible link constraints.

Capabilities include:

• Terrain-aware radio coverage analysis
• Point-to-point link analysis
• MANET connectivity assessment
• DTED/elevation validation
• Coverage and link visualisation on the map
• Radio profile and equipment-aware analysis workflows

This supports both planning and operational troubleshooting, particularly where network performance depends on terrain, antenna placement, bearer type or relay position.

Platform Support

IRIS is designed for cross-platform tactical use.

Supported platforms include:

• Windows desktop
• Windows tablets
• Linux 
• Android

Minimum System Requirements

• Operating System: 64-bit Microsoft Windows 10
• Processor: x86_64 architecture; quad-core CPU recommended
• Memory (RAM): Minimum 4 GB; 16 GB recommended
• Storage: Minimum 850 MB up to 210 GB of available space. Typical installation requires 20–50 GB of free space
• Display Resolution: Minimum 1366 x 768; 1920 x 1080 recommended
• Android: Android version 12 or higher

Some Initial Australian Defence Land Network Integration Center (LNIC) Comments

• IRIS is simple to configure and deploy. The LNIC Battle-lab used IRIS to quickly confirm the status/health of a multi-hop/multi-echelon tactical radio architecture employed for a synthetic T&E activity. Although the back-end configuration files could have been modified , LNIC had no reason to edit them specifically for the activity.
• IRIS is interoperable with the 82nd airborne NetAgility SBU TAK network. This included key protocols for each battle management system (TAK – both CoT XML and CoT protobuf); Sitaware – STC CoT GW and SHQ CoT GW; and TAK GeoChat – protobuf.
• IRIS did not require any server infrastructure to distribute COP data, emails, OPORDS, and reports. The only system similar to this in the TAK ecosystem is DITTO and/or SHARE – however we do not have sufficient OQE to inform a recommendation on what software would be suitable for these use cases.
• IRIS appeared to have significantly lower data overheads when compared to a TAK-centric network. LNIC would need to conduct further validation utilising representative land systems to provide greater fidelity and assurance on the indicative rates and differences to TAK and other battle management software. 
• IRIS mobile has a useful “network interface ping” button that allowed us to check the connectivity between the EUD and the radio. ATAK requires a separate Network Monitor plugin that is time consuming to configure at scale.
• IRIS mobile allowed for per-node configurations when deploying from a pipeline. This is something ATAK does not natively support unless an Mobile Device Manager (MDM – such as Watchtower) or custom Android Debugging Bridge (ADB) scripts are used post-deployment.

Why choose IRIS

Why choose IRIS paper

Videos

View All available Videos

Android version overview

Android CASEVAC

Android SA/PLI

Android address search and transmission

Android Free Draw

Windows version military symbols

IRIS on Linux

IRIS in Docker Container

Windows version location view

Windows version 3D mapping

Android 3D Scene Layer

Windows version ADSB Feed

Emergency Services Support Videos

Windows Emergency Service example

Android Emergency Service example

Video of IRIS’ Feature and MapServer power

Some Example Offline Maps (Esri tile file .tpkx)

Wellington NZ Map

Newtown Central 3D overlay (.slpk file use with Wellington Map)

Brisbane QLD

Canberra ACT

Pucka

Townsville

Watsonia

Enoggera

Swanbourne

Holsworthy

Email if you require additional maps.

Contact us should you wish to request a demonstration or explore opportunities for live trial activities.