Federated Mission Networking (FMN) is the NATO framework for building coalition communications networks that enable sharing of information across national C2 systems, sensors, and communication networks. The FMN framework defines a set of technical standards — called Profiles — that nations must implement to connect to an FMN-compliant coalition network. Each successive Spiral release adds new capabilities and tightens existing requirements. FMN Spiral 4 is the current operational baseline, ratified by the NATO Communications and Information Agency (NCIA) and adopted as the reference standard for NATO-led and NATO-partnered exercises and operations from 2024 onward.

The key structural change that Spiral 4 introduces over earlier spirals is the shift from capability-focused requirements to service-level requirements. Earlier spirals defined what data types must be exchangeable; Spiral 4 defines the specific services that must be available, at what performance level, with what security characteristics, and tested against a defined conformance baseline. This shift makes Spiral 4 requirements considerably more demanding to implement — but also considerably more useful for verifying that a system will actually interoperate in a deployed coalition environment.

FMN Architecture: Profiles, Spirals, and the Federation Concept Baseline

The FMN framework is built around the concept of Profiles — standardized specifications for specific coalition services. A Profile specifies: the technical standard the service must implement (e.g., a specific STANAG or NATO standard); the interface definition (API or message format); the security requirements for the service; and the conformance test criteria. Profiles are organized into Capability Packages, each addressing a functional area of coalition networking — Common Operational Picture sharing, messaging, directory services, mapping, logistics, and others.

The Federation Concept Baseline (FCB) is the configuration document for a specific coalition instance. It specifies which Profiles are mandated for that coalition, the network topology and addressing scheme, the agreed classification levels and cross-domain solution requirements, and the conformance testing dates and procedures. Nations connecting to the coalition must demonstrate conformance to each mandated Profile before connection is permitted. The FCB is maintained by the federation owner — typically the lead nation or NATO itself for NATO-led operations.

FMN Spirals are iterative releases of the Profiles library. Spiral 1 (2014) established the FMN concept and a minimal set of core profiles. Spiral 2 (2017) added COP federation and encrypted voice services. Spiral 3 (2020) introduced more rigorous conformance testing and expanded the Profile library. Spiral 4 (2023/2024 operational baseline) introduces the most significant changes in service scope and security requirements since FMN's inception.

Core Spiral 4 Service Requirements

FMN Spiral 4 mandates implementation of services across five core capability areas. The most significant requirements in each area are:

Common Operational Picture (COP) federation. Spiral 4 requires implementation of the Coalition Shared Data (CSD) service based on the JC3IEDM (Joint Consultation, Command and Control Information Exchange Data Model) and its successor the MIM (Multilateral Interoperability Programme Information Model). The specific requirements: a nation's COP system must publish ground unit tracks, positions, and status using the MIM data schema at a minimum update rate of 30 seconds for tracked elements and on-change for status fields. The service must implement the FMN Instant Messaging and Presence (IMP) profile for operator notification and must support subscription-based access to COP data (not just polling).

Mapping and geospatial services. Spiral 4 mandates support for the coalition Web Map Service (WMS) profile using OGC WMS 1.3.0 with NATO-specific extensions for classification marking of map layers. Nations must be able to consume coalition map services and contribute national map layers to the coalition mapping service. All geographic data must use WGS-84 as the reference datum, and positional data must include accuracy estimates following the NATO Positional Accuracy Reporting Standard.

Messaging services. The FMN Spiral 4 messaging profile mandates support for both NATO Message Text Format (NMTF) structured messages and unstructured collaboration messaging (chat and file transfer). The core requirement is the NATO Message Handling System (NMHS) profile, implementing the NATO Military Message Handling System (MMHS) standard for formal military message traffic. Email-based NATO messaging must implement the NATO SMTP profile with mandatory S/MIME encryption and digital signing using PKI certificates issued under the NATO PKI framework.

Directory services. Spiral 4 requires implementation of the FMN Identity Management (IdM) profile for user and system identity management across the coalition. This implements a federated identity model where each nation maintains its own identity provider (IdP) and federates with coalition IdPs using SAML 2.0. The requirement is that a user authenticated by their national IdP should be able to access coalition services without re-authentication, subject to access control policies based on their national identity attributes (clearance level, nationality, role).

Coalition voice and video. Spiral 4 extends voice requirements to include coalition conference calling and video teleconferencing using WebRTC-based services over the coalition IP network, with mandatory end-to-end encryption at the classification level of the coalition network. The voice service must support precedence and preemption (MLPP — Multi-Level Precedence and Preemption) for priority traffic.

Cross-Domain Requirements in Spiral 4

Spiral 4 introduces the most detailed cross-domain solution requirements of any FMN spiral to date. The key additions are:

A mandatory security label format for all data objects transiting the coalition network, following the NATO Security Labelling Specification. Every data object — tracks, messages, documents, map features — must carry a structured security label specifying its classification level, releasability markings, and handling caveats. Systems must enforce these labels when presenting data to users (users should only see data they are authorized to access) and when routing data across network segments with different classification levels.

Formal requirements for CDS performance: the Spiral 4 CDS profile specifies maximum throughput requirements (minimum 10 Mbps for coalition-to-national transfer of structured data) and maximum latency requirements (maximum 2 seconds for single structured data object transfer, maximum 500ms for track updates under normal load). These requirements are testable, and conformance testing includes CDS performance under simulated coalition network load conditions.

Mandatory audit logging for all cross-domain data transfers. Every data transfer through a coalition CDS must generate an audit record containing: timestamp, source classification level, destination classification level, data object identifier, authorized user or system identity, and transfer outcome (success/reject/modified). Audit logs must be retained for a minimum of 90 days and must be accessible to the federation owner for security incident investigation.

Data Model Requirements: MIM and JC3IEDM

The Multilateral Interoperability Programme Information Model (MIM) is the data standard that Spiral 4 mandates for ground force COP data exchange. MIM is the evolution of JC3IEDM and provides a richer attribute set for describing military units, equipment, activities, and locations. The specific Spiral 4 requirement is that any system publishing to the coalition COP service must implement a minimum subset of the MIM — the MIM Core Subset — which covers the unit and organization entity types, the location entity types, the action task entity types, and the equipment entity types, with the mandatory attributes specified in the Spiral 4 Profile documentation.

In practical implementation terms, MIM compliance requires that a national C2 system can export data to MIM-formatted XML or JSON, or can connect to a MIM gateway component that performs the mapping from the national data model to MIM. The MIM mapping is the most commonly under-estimated integration task: national C2 systems often have richer data models than MIM in some areas (particularly for national-specific equipment and organizational structures) and less rich in others (particularly for activity planning and logistics status). Producing a correct MIM mapping requires detailed knowledge of both the national data model and the MIM specification, and testing against a conformance test suite that verifies the mapping produces valid MIM instances.

Tactical Edge Federation: New in Spiral 4

FMN Spiral 4 introduces an entirely new set of requirements for tactical edge federation — the ability to connect deployed, mobile, and bandwidth-constrained nodes to the coalition federation. The tactical edge profile addresses scenarios where a tactical unit (a patrol, a forward operating base, a ship, a tactical aircraft) needs to participate in the coalition COP and messaging services with limited or intermittent connectivity.

The tactical edge requirements specify: a store-and-forward messaging capability that allows messages to be queued locally when connectivity is unavailable and transmitted when connectivity resumes, with guaranteed delivery semantics; a reduced-bandwidth COP synchronization protocol that synchronizes only changed data (delta updates) rather than full COP state; compression requirements for tactical edge transmissions (mandatory STANAG 4406-compatible compression for message traffic); and a disconnected operations mode where the tactical edge node can continue to display the last-synchronized COP state and create new track reports while disconnected, with automatic resynchronization when connectivity is restored.

Key insight: FMN Spiral 4 conformance testing is not optional for NATO-led and EU-led operations — it is a prerequisite for network connection. Nations that have not completed Spiral 4 conformance testing before an exercise or operation are restricted to simplified connectivity modes that limit their ability to contribute to and consume coalition data services. The conformance testing timeline for a national C2 system is typically 6–12 months from initial FMN integration work to successful conformance test completion.

Implementation Pathway for National Systems

The standard implementation pathway for achieving FMN Spiral 4 compliance for a national C2 system has four phases. Phase 1 (Gap Analysis, 1–3 months): compare national system capabilities against each mandated Spiral 4 Profile requirement, documenting gaps in data model support, service interface implementations, and security label handling. Phase 2 (Interface Development, 4–8 months): develop or procure the coalition gateway components that bridge from national system data to FMN Profile service interfaces, including MIM mapping, security label generation, and CDS interface integration. Phase 3 (Integration Testing, 2–4 months): test the coalition gateway components against FMN test harnesses maintained by NCIA and against partner nation systems in bilateral test events. Phase 4 (Conformance Testing, 1–2 months): complete formal conformance testing with NCIA, generating the Conformance Statement that permits connection to FMN-compliant coalition networks.