Jump to content

Federated Mission Networking

From Wikipedia, the free encyclopedia
Federated Mission Networking
Formation2015
PurposeEnabling better command and control, decision making and information sharing by connecting forces in a coalition environment
HeadquartersFMN Secretariat
Location
ProductsFMN Spiral Specifications; Joining, Membership and Exit Instructions (JMEIs)
FieldsStandardization
Membership38 (31 NATO Nations, 6 non-NATO nations, and NATO Command Structure)
OwnerNATO
Websitednbl.ncia.nato.int/FMNPublic/SitePages/Home.aspx
FMN on LinkedIn

Federated Mission Networking (FMN) is a significant initiative to help ensure the interoperability and operational effectiveness of the North Atlantic Treaty Organization. It is a key contribution to the Connected Forces Initiative,[1] helping Allied and Partner forces to better communicate, train, and operate together.[2] This includes the NATO Command Structure as well as the NATO Force Structure. The purpose of FMN is ultimately to support Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) and decision-making in operations by enabling the rapid instantiation of mission networks. Including the NATO Command Structure, 39 nations have joined the FMN initiative as so-called "FMN Affiliates" and work together under the FMN Framework Process to coordinate the design, development, and delivery of operational and technical capabilities required to conduct net-centric operations. Each development increment is referred to as an "FMN Spiral." The respective requirements, architecture, standards, procedures, and technical instructions are documented in the so-called "FMN Spiral Specifications." FMN Spiral Specifications are based on well-known standards and best practices, hence supported by most off-the-shelf products and vendor neutral. TACOMS[permanent dead link‍] standards and profiles specify a common, technology- and topology independent network interoperability layer (or federated core) for federated mission networks.[3][4][5] There is also a rolling 10-year FMN Spiral Specification Roadmap of the envisioned future capabilities. At the same time, the Coalition Interoperability Assurance and Validation (CIAV) process[6][7] ensures that current interoperability issues are being identified and fed back into FMN capability development.

Background

[edit]

NATO Federated Mission Networking arose from the operational requirement in Afghanistan, which necessitated troop-contributing nations to operate in a single information-sharing domain called the Afghanistan Mission Network (AMN).[8][9] Through the experience of ISAF in Afghanistan, the value of a coalition-wide network was made clear: greater situational awareness facilitates more effective decision-making.[10] Based on improved coalition unity of effort and speed of command, Commander ISAF endorsed AMN best practices as the "right model" for future coalition missions and forwarded the requirement to NATO and to the US Chairman of the Joint Chiefs of Staff. On November 21, 2012, the NATO Military Committee agreed to the "Future Mission Network Concept,"[11] later noted by the North Atlantic Council (NAC), as the basis for the development of an implementation plan[12][13] that defines "the implications for NATO and the Nations." The concept provided overarching guidance for establishing a federated mission networking capability that enables effective information sharing among NATO, NATO member nations, and/or non-NATO entities participating in operations.[14] The FMN Concept describes the operational requirements, principles, and implementation considerations for a capability consisting of three components: Governance, FMN framework, and mission Networks.

The FMN Concept envisions a world in which the commander of an operation effectively performs end-to-end processes and shares information in a coalition environment. This ability is enabled through a common understanding of how those processes are described and through access to shared, secure information. The commander must be able to communicate intent and direction down to the tactical level and provide reports and recommendations up to the strategic level. Information must be available throughout the coalition force in any foreseeable operational scenario. The achievement of trust and transparency among mission participants is essential. The FMN concept reflects a clear lesson learned: Operational experience has irrefutably demonstrated that a federated mission network is the best means to create this common, mission-wide data and information sharing environment. The FMN Concept concludes that the ability to generate federated mission network instances is therefore a key and essential capability for NATO, NATO member nations, and/or non-NATO entities participating in operations. In contrast to the AMN, Federated Mission Networking attempts for mission Networks to be:[15]

  • simpler, by reducing the number of joining options
  • more robust, by removing the need for a centralized core and introducing redundant peering (TACOMS[permanent dead link‍])
  • faster to set-up, by providing off-the-shelf template solutions
  • easier to manage, by using common and interoperable IT Service Management practices
  • more flexible, by not having to depend on a single core
  • able to share information with other entities, by introducing data labeling
  • more cost-effective by enabling the cross provisioning of services between mission network participants

In the context of FMN, a federation is an association where each stakeholder retains control of their own capabilities and affairs while accepting and complying with the requirements laid out in pre-negotiated and agreed arrangements in a collective fashion.

To facilitate collaboration and coordination among "FMN Affiliates," NATO has agreed to host an FMN Secretariat, which is composed of liaison officers from each "FMN Affiliate." The FMN Secretariat coordinates the activities of five working groups, which address operational and security requirements, capability planning and specification development, assurance and validation of interoperability, and coordination of change implementation. The working groups forward their products to a flag and general officer-level FMN management group for review and delivery to respective national or organizational governance bodies for consideration, acceptance and implementation.

Command implications

[edit]

The operational commander's requirements are the preeminent driver of each mission Network. The FMN Concept identified six objectives that drive the operational requirements for nearly all mission networks:

  1. Seamless human-to-human communication across the force.
  2. A single view of the battle space across the Mission Network.
  3. Timely provision of a mission Network.
  4. Provision of consistent, secure, accurate and reliable mission data.
  5. Community of Interest (COI) capabilities that align with the mission requirement.
  6. Well-trained staff that can support an effective decision cycle and take full advantage of the systems provided.

A mission network must support the respective chain of command and the execution of relevant mission threads and it must respond to the Commander's battle rhythm during each phase of the operation. FMN defines four different types of environments:[16]

  • Collective training environment (CTE) for preparing forces ahead of a mission.
  • Verification and validation environment (VVE) for testing any changes to procedures, applications and services.
  • Operations planning environment (OPE) for supporting collaborative planning of coalition participants that is conducted prior to deployment.
  • Mission execution environment (MEE) covers the actual deployment and instantiation of a federated mission network to support a specific operation.

The NATO FMN Implementation Plan identified the need for establishing a mission thread approach to provide consistent context for interoperability, training, planning, and mission activities to enhance the effectiveness of future operations and inform FMN implementation.[12] As a result, the NATO Strategic Commands produced the NATO Mission Thread Capstone Concept. The implementation of this concept will impact the development of the doctrine, organization, training, and requires contributions and participation of the operational community.

Industry implications

[edit]

In support of the FMN initiative, the Network Centric Operations Industry Consortium has introduced a new Interoperability Verification (IV) process, intended to support the acquisition of technical products and services for Federated Mission Networking.[17] The IV assessment, based on product testing that takes place as part of the normal quality manufacturing process, looks at how well the technology meets FMN spiral Specifications and can be implemented. The vision is for NATO and its partners to get enhanced capability for the same cost and for vendors to have access to more markets.

National implementation

[edit]

Following the idea of a federation, each FMN affiliate is responsible for implementing its own capabilities that conform to FMN spiral Specifications.

Based on the lessons learned from operations in many coalitions, Belgium decided to formally affiliate with FMN early in March 2016. The implementation of this international initiative is drawn up using a pragmatic and holistic approach following the DOTMLPFI methodology. At this stage (Spiral 2 as of June 2019), Belgium disposes of a capability enabler (the Mission Defense Network), which offers minimum services to allow deployed troops to communicate, share, and exchange information with partners in a secure way, and automatically. Those services will be expanding with the following spiral development.

Canada's C4ISR Vision[18] outlines the importance of interoperability with its Joint, Interagency, Multinational, and Public (JIMP) partners and sets strategic objectives to achieve it within both the enduring and episodic domains of its Military Integrated Information Infrastructure (MI3). Recognizing that FMN concepts and standards are key to achieving its goals, Canada is implementing the FMN Spiral specifications as part of its 'Canadian Deployable Mission Network' (CDMN) design. True operational interoperability takes more than just technology, so Canada champions the use of FMN-capable forces in all appropriate multilateral operations, exercises and events that it participates in as a way to ingrain interoperability as a fundamental aspect of modern operations.

Established in May 2020, the FMN 'French Roadmap for the Interoperability of Systems' in a Multinational Environment (FRISE) is the national FMN implementation programme within the French Ministry of Armed Forces. The main stakeholders from the Defense Staff (État-Major des Armées, EMA) and the Defense Procurement Directorate (Direction générale de l’armement, DGA) aim to align various national capability development activities with the FMN Initiative and contribute to its battle-rhythm.

The initiative 'German Mission Network' aims to create improved command and control capabilities for the German armed forces. The German Mission Network is fully compatible with NATO's Federated Mission Networking and merges the previously physically separated IT systems and services for deployments to a physically and logically interoperable and integrated multinational system of systems. The 'Harmonization of Command and Control Information Systems' program (Harmonisierung der Führungsinformationssysteme, HaFIS) is the first to spearhead this challenge with a planned successive enlargement to other projects over the following years.[19][20]

In 2015, after the formal affiliation with the FMN initiative, Italy approved the governance and management structure of the Italian FMN initiative, aiming to achieve the capability to set up and manage a mission network according to the FMN specifications. In 2016, Italy confirmed the compliance of the Italian FMN Node to FMN Spiral 1 requirements in a number of multinational exercises and has actively contributed to the development of the next set of capabilities. In light of the results achieved in 2016, Italy decided to implement the capability acquired in Afghanistan by deploying an FMN Node federated to the Afghanistan Mission Network (AMN), which is now fully operational. The Italian Defense is also in the process of approving the implementation of an Italian Mission Network to fulfil the needs in terms of Command and Control of a mission or multinational operations (also in the role of "leading nation" of a coalition) or, in a dual-use perspective, in case of an emergency operation for humanitarian aid and disaster relief. Italy is also fully engaged in FMN management with subject matter Experts and representatives in the FMN Secretariat, contributing to the evolution of the NATO FMN initiative.

The Netherlands implemented the first set of agreed FMN capabilities (Spiral 1) within their deployable Theatre Independent Tactical Adaptive Armed Forces Network (TITAAN) which is used by the Dutch armed forces. The next steps include further alignment with FMN capabilities and the implementation of future FMN spiral specifications within TITAAN.[21] The Netherlands acknowledged that the implementation of federated capabilities needs a DOTMLPF-I perspective to be able to reach the next level of interoperability. The German and Dutch armed forces are taking their cooperation to an unprecedented level of integration. It entails the harmonization of requirements, procedures, education, and training.[22] Federating capabilities provided by both nations in the context of the multinational 1 (GE/NL) Corps are a demonstration of the practical implementation of FMN and help nations gain experience and to enhance flexibility and interoperability.

In recognizing that FMN is more than just creating interoperable C2 systems, like the Netherlands, Norway is seeking to adopt the entire concept of Federation and Networking from a DOTMLPF-I perspective. In practical terms this involves other agencies than those traditionally involved with development and implementation of C2 systems. In particular, the engagement of decision makers at Ministry of Defence level and operational planning staff at the highest level of operational command is considered to be essential. Regarding implementation of the FMN technical aspects, Norway has chosen not to create a dedicated implementation programme. Instead, FMN Spiral Specifications will be injected into upgrades of existing systems and emerging projects.

Poland is implementing a Polish Mission Network (PMN) in accordance with FMN Spiral Specifications. It consists of a permanent Polish Mission Network Element to which units can connect their network extensions during national and multinational exercises. For the first time PMN was successfully implemented during Exercise Anakonda 2016 as the main part of a federation based on five Mission Network Elements. PMN instantiation is also being used by NATO's enhanced Forward Presence (eFP) as the capability ready for interoperability with NATO's NRF and VJTF.

In 2016, Sweden announced its intention to become an FMN Affiliate with the level of ambition as a Mission Network Extension participant.[23] FMN constitutes an important basis for interoperability and the Swedish Armed Forces have stated that by 2023, Command and Control information system such as SWECCIS must be fully FMN compatible. Sweden recognize that future FMN spiral specifications will include additional requirements for evolving the Armed Forces' operational command support system to continue to be FMN compatible.

The United Kingdom has built upon its experiences in Afghanistan to develop mission configurable capabilities as described in Strategic Defence and Security Review 2015. This work aligns to FMN with the MAGPIE system utilizing FMN Spiral 1 Specification which is already in service with HQ ARRC. The New Style of IT (NSoIT) programme has subsumed the work initiated by the Information Superiority in Contingent Operations (ISCO) research programme and JACKDAW equipment programme to develop a configurable system that will meet the Spiral 2 specification and be readily updateable to future FMN spirals. Whilst MAGPIE is predominantly a land system, NSoIT will be deployed across the whole of the British Armed Forces.

The United States implementation program is known under the name of 'Mission Partner Environment' (MPE)[24] and it reflects US DoD desire to be an FMN affiliate. From the technical perspective, the US DoD CIO's office has been working on the Mission Partner Environment Information System (MPE-IS), which provides the ability to change things quickly so that networks can be:[25] set up quickly to support the joint force; broken down very quickly; and federated to exchange information in support of the joint force, the DoD and mission partners. MPE-IS aligns with NATO's FMN capability, enhancing the mission and ability to work with mission partners. For continuity of historical references, it is useful to know that both FMN and the US MPE efforts started out under the moniker 'Future Mission Network' but underwent name changes in 2012 to avoid inevitable confusion due to association with something that was 'always in the future' or limited to materiel oriented IT and network solutions.[26]

References

[edit]
  1. ^ "Connected Forces Initiative". www.nato.int. 22 June 2016. Retrieved 7 April 2017.
  2. ^ "Federated Mission Networking". www.act.nato.int. Archived from the original on 28 January 2019. Retrieved 7 April 2017.
  3. ^ Abali, Sezgin; Allen, Richard; Bourgoi, Michel; Luoma, Marko (13 May 2016). "TACOMS+ Project Closure Report" (Report). TACOMS+ International Project Office. TACOMS+/IPO(2016)R-09. Retrieved 5 May 2017.
  4. ^ Frøseth, Ida Marie (June 2016). "Adding network services to Federated Networks" (PDF). Universitetet i Oslos. Archived from the original (Presentation) on 15 April 2017. Retrieved 14 April 2017.
  5. ^ Kidston, David. "Investigations in Software-Defined Networking (SDN)" (PDF). Communications Research Centre Canada. Retrieved 14 April 2017.
  6. ^ Coalition Interoperability Assurance & Validation - What is CIAV?. YouTube. 17 July 2014. Retrieved 7 April 2017.
  7. ^ Rissinger, Todd (15 January 2018). "CIAV Whitepaper". Retrieved 20 January 2018.
  8. ^ Chad C. Serena; Isaac R. Porche III; Joel B. Predd; Jan Osburg; Brad Lossing (2014), Lessons Learned from the Afghan Mission Network: Developing a Coalition Contingency Network, Santa Monica, CA: RAND Corporation, ISBN 978-0-8330-8511-5, retrieved 19 April 2017. Also available in print form.
  9. ^ Veit, Klaus F. (9 November 2011). "The Afghanistan Mission Network (AMN) – A model for network enabled capabilities". www.european-defence.com. Archived from the original on 14 April 2017. Retrieved 13 April 2017.
  10. ^ Stoltenberg, Jens (30 January 2015). "The Secretary General's Annual Report 2014". www.nato.int. Retrieved 28 April 2017.
  11. ^ Military Committee Advice on the Future Mission Network (FMN) Concept (Report). NATO. 7 December 2012. C-M(2012)0096.
  12. ^ a b NATO Federated Mission Networking Implementation Plan (Report). NATO. 29 January 2015. C-M(2015)0003.
  13. ^ Lambert, Nicholas (2 March 2015). "NAC approves NATO Federated Mission Networking Implementation Plan". NCI Agency. Retrieved 29 April 2017.
  14. ^ NATO Federated Mission Networking - effective information sharing during NATO operations. YouTube. NCI Agency. 16 June 2014. Retrieved 7 April 2017.
  15. ^ Friedrich, Gernot (26 March 2014). New Generation C2 Services: From Afghanistan Mission Network to Federated Mission Networking (Presentation). AFCEA. Retrieved 19 April 2017.
  16. ^ Ebbutt, Giles. "Networking future battlelabs". Jane's International Defence Review (September 2013): 62–65.
  17. ^ "Interoperability Verification". www.ncoic.org. Archived from the original on February 16, 2017. Retrieved 7 April 2017.{{cite web}}: CS1 maint: unfit URL (link)
  18. ^ Vice Chief of Defence Staff (March 2016). The Canadian Armed Forces Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) Strategic Vision, Goals and Objectives (Report). Department of National Defence.
  19. ^ Thiele, Ralph D. (7 January 2015). "Relevanz, Attraktivität und Zukunftstüchtigkeit – Bundeswehr 4.0 ante portas" (PDF). ISPSW Strategy Series (30). Institut für Strategie- Politik- Sicherheits- und Wirtschaftsberatung. Retrieved 14 April 2017.
  20. ^ Eisinger, Stefan (17 November 2016). "Data Centric Security Architecture" (Presentation). www.afcea.de. Retrieved 14 April 2017.
  21. ^ Bulk, Andres (April 2017). "Federated Mission Networking (FMN)" (PDF). Intercom (in Dutch). 46 (1). Vereniging Officieren Verbindingsdienst: 27–34. ISSN 1383-0473. Retrieved 16 Dec 2020.
  22. ^ Hennis-Plasschaert, Jeanine Antoinette (28 May 2013). "Address by the Netherlands minister of Defence on the occasion of the Berlin Strategy Conference" (Speech). www.government.nl. Retrieved 17 May 2017.
  23. ^ Beslut - Försvarsmaktens svarsbrev om Federated Misson Networking Affiliation, FM2016-4935:2, 2016-02-29. Stockholm: Försvarsmakten.
  24. ^ Smith, Angela (22 April 2016). "Mission Partner Environment (MPE) / Multinational Information Sharing (MNIS)" (Presentation). www.disa.mil. Retrieved 27 April 2017.
  25. ^ Pomerleau, Mark (22 August 2017). "Coalition interoperability being written into requirements". www.c4isrnet.com. Retrieved 24 August 2017.
  26. ^ Nankervis, John (June 2015). "US MPE/NATO FMN History and Status Update" (PDF). www.apan.org. Archived from the original (PDF) on 13 April 2017. Retrieved 12 April 2017.
[edit]
Retrieved from "https://wiki.riteme.site/w/index.php?title=Federated_Mission_Networking&oldid=1259652673"