MTFXML Tactical Message Exchange

Overview#

During a coalition operation, headquarters elements exchange hundreds of structured tactical messages every day: situation reports, artillery fire missions, air tasking orders, and logistics requests. Each one follows a defined format so that receiving systems can parse and act on it without human translation. MTFXML brings NATO Military Text Format messages into XML representation, giving software systems a structured schema to validate, route, and process mission traffic programmatically.

The MTFXML Tactical Message Exchange module provides an operational surface for creating, ingesting, and supervising NATO-style tactical messages in XML form. It gives teams immediate visibility of inbound and outbound traffic volume, active message sets, and the timing of the latest tactical traffic so that structured mission communication stays visible and governable throughout an operation.

Open Standards#

NATO MTFXML (APP-11 / APP-13): The core message format implemented; all tactical messages are serialised and parsed using the NATO MTFXML XML schema, with the canonical namespace http://standards.nato.int/mtfxml applied to every outbound document.
ADatP-3 (Allied Data Publication 3): The NATO publication that defines the structured message sets (SITREP, INTREP, INTSUM, OPREP-3, LOCSTAT, MEDEVAC) that this capability parses and builds, including field naming conventions and mandatory header fields.
VMFCat / Variable Message Format (VMF): The VMF catalogue namespace (http://standards.nato.int/vmfcat) is registered alongside MTFXML, enabling interoperability with coalition systems that map MTFXML to binary VMF for radio transmission.
NATO Date-Time Group (DTG) Format: All messages carry a DTG timestamp in the NATO standard DDHHMMSSZMONYY format, ensuring unambiguous temporal ordering of tactical traffic across coalition partners.
W3C Extensible Markup Language (XML) 1.0 and XML Namespaces: All message documents are well-formed XML with explicit namespace declarations; inbound partner-supplied XML is hardened against XXE and entity-expansion attacks via defusedxml.
GraphQL (June 2018 Specification): The operational interface for querying message history, ingesting inbound XML, and composing outbound messages is exposed as a typed GraphQL API with dedicated query and mutation types.

Last Reviewed: 2026-03-25 Last Updated: 2026-04-14

Key Features#

Inbound and Outbound Traffic Monitoring: Tracks daily message exchange in both directions for immediate awareness of communications tempo and whether traffic levels match expected operational activity.
Message Set Visibility: Shows how many distinct message sets are in current use across the environment, supporting format governance during multi-partner exercises.
Latest DTG Awareness: Surfaces the latest message Date-Time Group so operators can identify stale traffic or recent bursts of activity without searching through logs.
Structured Message Handling: Focuses on formal tactical message exchange rather than informal chat workflows, aligning with NATO message format standards.
Mission Workflow Support: Connects naturally to tactical, messaging, and simulation operations for a complete structured-communications picture.

Use Cases#

Mission Message Supervision: Operators monitor whether tactical traffic is flowing as expected during active operations, spotting gaps before they affect coordination.
Structured Message Ingestion: Teams ingest externally supplied tactical messages into a controlled workflow for review and onward use.
Coalition Interoperability Checks: Interoperability teams verify that message sets and traffic volume match the current exercise or mission context before certifying readiness.
After-Action Communication Review: Supervisors review message volume and recency as part of post-event analysis to identify periods of degraded communications.

Integration#

MTFXML message composition and ingestion workflows
Tactical, communications, and simulation workbenches
Message-routing and interoperability services
Structured operational reporting workflows