2.5. Creating relationships to other concepts and planning objects within NATO

25. Different initiatives and organizations have developed new concepts to govern developments in the interoperability domain. These concepts have logical relationship to the NISP.

2.5.1. Architecture Building Block

26. An Architecture Building block is a constituent of the architecture model that describes a single aspect of the overall model [4].

2.5.1.1. Characteristics

27. ABBs:

  • Capture architecture requirements; e.g., business, data, application, and technology requirements

  • Direct and guide the development of Solution Building Blocks

2.5.1.2. Specification Content

28. ABB specifications include the following as a minimum:

  • Fundamental functionality and attributes: semantic, unambiguous, including security capability and manageability

  • Interfaces: chosen set, supplied

  • Interoperability and relationship with other building blocks

  • Dependent building blocks with required functionality and named user interfaces

  • Map to business/organizational entities and policies

2.5.2. FMN Spiral Specifications

29. Federated Mission Networking (FMN) Spiral[5] Specifications encompass "an evolutionary cycle that will raise the level of maturity of federated mission networking capabilities over time".

30. The FMN spiral specification contain the following sections

  • architecture,

  • instructions,

  • profiles, and

  • requirements specifications.

The Mandatory and Candidate FMN Spiral Profiles, in context for FMN Affiliates, are listed in the NISP Volumes 2 and 3.

2.5.3. Capability Packages

31. Profiles will be referenced in the NISP for specified NATO Common Funded Systems or Capability Packages and may include descriptions of interfaces to National Systems where appropriate.


[4] TOGAF 9.1 Specification

[5] Annex B TO Volume I - Implementation Overview, NATO FMN Implementation Plan v4.0 dated: 23 September 2014, Terms and Definitions