388. On 21 November 2012, the Military Committee agreed the NATO Future Mission Network Concept^[12]. This document is intended to inform training and equipping investments to facilitate a nation or organization to participate in Federated Mission Networking (FMN) activities and to contribute to the generation of federated Mission Networks.

389. The aim of the FMN Profile is to provide a generic minimum set of specifications which enable different members (nations or organizations) to promptly establish a federated environment for exchanging data and information under harmonized security policies across national/organizational boundaries and for providing and using services to and from other members.

390. The FMN Profile provides a suite of interoperability standards and other standardized profiles for interoperability of communications services, core enterprise services and selected community of interest services in a federated mission network in support of multinational (military) operations. It places the required interoperability requirements, standards and specifications, to include the related reference architecture elements, in context for FMN Affiliates. FMN Affiliates are nations or organizations providing for or participating in the FMN capability development. The profile is a generic specification; it allows for independent national technical service implementations, without the loss of essential interoperability aspects.

391. Within the NATO context, this FMN Profile will also support the new MC 593/1 developed by the Land C3 Requirements Tiger Team (LC3R TT) which will provide a more detailed applications and system catalogue. In their development, NHQC3S will ensure that the FMN Concept, the FMN Profile and MC 593/1 remain consistent and mutually supporting.

392. The starting points for development and continuous evolution of the FMN profile are the C3 Classification Taxonomy ^[13], the Afghanistan Mission Network (AMN) Profile^[14], and TACOMS STANAGS^[15]. The C3 Classification Taxonomy is used to identify particular services and associated Service Interoperability Point where two entities will interface, and the standards in use by the relevant systems.