Overview#
Ingest, store, and query NATO APP-11 formatted command and staff messages through a single authenticated interface, without building a custom message store or parser.
Coalition headquarters run on structured military messaging. NATO APP-11, the Allied Communications Publication 11 message catalog, defines the standard family of formatted command and staff messages used across allied forces, each with a recognised message type, set identifier, and the addressing and time conventions that allow any participating nation to read traffic the same way. The platform accepts that traffic directly, captures every field of each message, and makes the whole record set available to operators and software integrators through one consistent, organisation-scoped interface.
Each stored record preserves the full message context: message type, set identifier, free-text content, originator, addressee, Date-Time Group (DTG), classification, and secrecy level. Clearance-based filtering is applied at read time so users only ever see records their accreditation permits, every ingestion is written to the audit trail for compliance and after-action review, and message volume is summarised by message type so staff can monitor communications tempo at a glance.
Key Features#
-
APP-11 Message Ingestion. Submit a NATO APP-11 formatted message and have every field captured in one operation. The record preserves message type, set identifier, free-text content, originator, addressee, Date-Time Group, classification, and secrecy level, so nothing from the original signal is lost on the way into the store.
-
Single Authenticated Read Interface. Retrieve stored messages through one organisation-scoped read path, with optional filtering by message type and standard pagination for large volumes. Records are returned newest-first, giving staff an immediate chronological view of recent traffic.
-
Clearance-Based Record Filtering. Each message carries a secrecy level, and a shared interoperability bridge filters the returned record set against the requesting user's clearance at read time. Users below the required level simply do not receive the record, enforcing correct handling in multi-level secure coalition environments.
-
Volume-by-Type Statistics. A dedicated statistics path summarises stored messages grouped by message type and ordered by count, so command staff can monitor communications tempo and spot shifts in message activity without trawling individual records.
-
Automatic Audit Capture. Every ingestion writes an interoperability ingest audit record carrying the source standard, record identifier, secrecy level, message type, set identifier, originator, and the acting user and organisation. Nothing enters the catalog without an immutable trail behind it.
-
Coalition Fusion Emission. On ingestion, each message also emits an operational entity of type mission context into the coalition fusion layer, tagged with its source standard and secrecy level. Formatted messaging traffic therefore contributes to the same shared operational view as other allied data sources rather than living in isolation.
-
Organisation Data Sovereignty. All storage, queries, and statistics are scoped to the authenticated organisation, so coalition partners on the same platform never see one another's message traffic.
-
No Custom Tooling Required. Operators and integrators connect formatted message traffic directly into the platform and consume it through the same interface they use for every other data source, removing the need to commission and maintain a bespoke store, parser, or viewer for APP-11.
Use Cases#
Coalition Headquarters Communications#
A combined joint task force headquarters receives APP-11 formatted command and staff messages from multiple participating nations. Operators route that traffic into the platform and read it through one authenticated path, giving watch staff a single, consistent view of formatted messaging across the coalition without standing up a separate message-handling system.
Communications Tempo Monitoring#
Watch officers use the volume-by-type statistics to track operational tempo across a mission. A rising count of a particular message type can signal a change in activity, and the summarised view surfaces that shift far faster than reading individual messages would allow.
Multi-Level Secure Message Handling#
In an environment mixing clearances, the same message store serves users at different accreditation levels safely. Clearance-based filtering ensures each operator sees only the records permitted by their accreditation, so a single shared catalog can support staff across multiple security levels.
Compliance and After-Action Review#
Because every ingestion is captured in the audit trail with its source standard, message metadata, and acting user, the message catalog provides a complete record for compliance reporting and after-action review. Analysts can reconstruct exactly which messages were received, by whom, and when.
Software Integrator Onboarding#
A software integrator connecting an allied messaging gateway to the platform ingests APP-11 traffic through a documented interface and queries it back through one consistent surface, rather than reverse-engineering a bespoke schema. This shortens integration timelines for partner systems feeding formatted messages into a shared picture.
Integration#
The capability is provided through a GraphQL API. A read path returns stored APP-11 messages for the authenticated organisation with optional message-type filtering and pagination, a second read path returns message counts grouped by message type, and a write path ingests a single APP-11 message. All access is authenticated with OAuth 2.0 bearer tokens in JSON Web Token (JWT) format and scoped to the authenticated organisation, consistent with the platform's identity and authorisation layer.
Messages are ingested as a structured input carrying message type, set identifier, free-text content, originator, addressee, Date-Time Group, classification, and secrecy level. The ingestion response confirms the new record identifier, the message type, and success, so a calling system can immediately reconcile what it sent.
Stored records are held on the platform's normalised message model and surfaced into the coalition fusion layer as mission-context entities tagged with their source standard. Downstream consumers, including the shared operational view, reporting modules, and alerting rules, work with APP-11 records in the same way they work with other coalition and allied data sources. The benefit to a customer is direct: connect a formatted message feed once, and that traffic becomes part of the same picture, audit trail, and clearance model as everything else on the platform, with no custom store or parser to build or maintain.
Open Standards#
- NATO APP-11 (Allied Communications Publication 11). The military message catalog format defining the standard family of formatted command and staff messages used across allied forces. The platform ingests, stores, and queries messages keyed to their APP-11 message type and set identifier.
- NATO STANAG (Standardisation Agreements). Referenced through the APP-11 message taxonomy; the message types and sets the platform captures derive from the NATO standardisation agreements that APP-11 codifies, keeping ingested records aligned with allied messaging conventions.
- DTG (Date-Time Group). The NATO and allied forces time-stamp standard; each stored message preserves its Date-Time Group field so the original signal timing is retained for sequencing, correlation, and after-action reconstruction.
- OAuth 2.0 / JWT. All API access is authenticated using OAuth 2.0 bearer tokens in JSON Web Token format, consistent with the platform's identity and authorisation layer.
Security and Compliance#
Every stored message carries a classification and a secrecy level. Record-level filtering checks the requesting user's clearance before any message is returned, so users in a multi-classification environment cannot read traffic above their permitted level, and records the user is not cleared for are withheld rather than redacted. All storage, queries, and statistics are organisation-scoped, preventing one coalition partner from seeing another's message traffic on a shared platform.
Every ingestion is written to the audit trail with its source standard, record identifier, secrecy level, message metadata, and the acting user and organisation, providing a complete and reviewable history for compliance and after-action purposes. Network separation between classified and unclassified message sources remains the responsibility of the operator: classified messaging traffic should reach the platform over networks physically or cryptographically separated from unclassified infrastructure. The platform enforces classification and clearance policy on stored and queried data; it does not substitute for network-layer separation.
Last Reviewed: 2026-05-26 / Last Updated: 2026-05-26