1. NAF v3 Report and update to IPP meeting 24 Jan. 07
Prepared by Svein Olaussen
NAF Revision Syndicate

2. NAF v3 development schedule
Draft
NAF 3 Final
NAF Revision Syndicate Internal releases for Development and Review
Feedback from Review
Q2 07
Feb
Mar
Jul
Aug/Sep
Oct
Nov
THIS IS THE TIMELINE WE presented at the last IPP meeting. A FIRST DRAFT WILL BE AVAILABLE MID JULY. THE DRAFT WILL BE SENT OUT FOR REVIEW TO COMMITTEES AND CENTRAL STAKEHOLDERS LIKE ACT TO HAVE THEIR COMMENTS DURING AUG/SEPT.
WE WILL THEN HAVE A FINAL VERSION LATER IN THE AUTUMN
NAF v3 Initial release for External Review
NAF v3 Final release

3. NAF v3 Ed 0.9 Status

4. Lead nations or organizations
Executive Summary
Cht 1 Introduction
Cht 2 Stakeholders
Cht 3 Arch. Elements
Cht 4 Views & Subviews
Cht 5 NMM
Cht 6 Governance
Cht 7 Terminology, Ontologi
Annex A AEM 2
Annex B NAF NAF 3
Annex C Mapping Views
All
Norway
ACT??
NC3A
Norway?? - NC3A
UK-SW
NHQC3S - NC3A
Belgium
Finland??
ACT

5. Constraints Chapter 5
Spring 2006 UK stated that they could not continue to support requirements from NATO, which were “over and above” UK requirements
Completion of the NAF MetaModel (NMM) should be contracted out in order to deliver the first draft version mid 2006.
Several months passed and NATO was not been able to establish the necessary contractual framework.
This has severely hampered the completion of NAF, and several chapters suffer from an incomplete NMM and harmonization between chapters.

6. Constraints NC3A
Requested support fra NC3A in autumn 2005
Took 4 months to approve
Only 180 KEuro of the original request for 300 KEuro was granted
Without the support of NC3A it would not have been possible to arrive at the current state and deliver a draft version of the NAF version mid July 06.
NRS Stated: ”Continued support from NC3A is vital in order to finish the revision and complete NAF v3 before end of 2006”.

7. Needed support from NC3A to complete NAF
Complete Chapter 3
Resolve remaining issues and harmonize with cht 4 and 5
Complete chapter 4
Complete and add Bandwidth and Spectrum, harmonize with cht 3 and 5
Complete chapter 6
Coordinate with NID and agree on way ahead.
NAF editor function
Ensure coherence and consistence and formatting across all chapters in NAF
Annex A
Update AEM (No cost to NAF)
Total cost estimated to 116 KEuro

8. 100 kEuro for NC3A was in place
Economy - Status
Contract with a UK Company for completion of NMM and chapter 5 is in place. (Same company supports MOD UK)
100 kEuro for NC3A was in place
7 % budget cut
Still 20 kEuro short to Support NAF

9. Architecture Building Blocks
NNEC Architectures OA, ERA, RA, TA
NATO Architecture framework (NAF v3)
Architecture methodology (AEM v2.0)
NATO Architecture Meta-Model and Repository NMM/NAR
NATO has developed a COMPENDIUM OF NNEC ARCHITECTURES AND DESCRIBES THE ABOVE MENTIONED ARCHITECTURE BUILLDING BLOCKS AS ESSENTIAL TO A SUCCESSFUL IMPLEMENTATION OF NNEC
NNEC Maturity Level - Methodology
NATO Interoperability Standards and Profiles (NISP)

10. Management of NMM Norway Meta Model DODAF Meta Model M3 NMM
Commonality
of Meta Models
Nations and organisations have developed Architectural meta-models. At present, they are closely related and have evolved from the MODAF Meta Model M3. For example, the NATO Meta Model is iidentical to the MODAF meta model except that it has definitions for SOA. It is likely that other nations will have additional or differing definitions for example for security, procurement, etc. components to the match
As is Picture of Architecture Meta-Models

11. Management of NMM DODAF Meta Model M3 Reducing Norway Meta Model
Interop over time
Norway Meta Model
NMM
THERE IS A NATIONAL AND NATO AMBITION THAT THESE MODELS CAN BE HARMONIZED OVER TIME AND THAT WE AVOID REDUCING THE INTEROPERABILITY AND COMMON CORE
Management of Meta Models as separate Entities

12. ROADMAP for NATO ARCHITECTURE META MODEL (NMM)
OAv2,5 MM
METIS
NMM
V 1.0
V 3.0 Tool Ind.
NMM v 0.8
AEM v 2.0
NML
NISP
NIE
(ARIS) MARS
IDEAS Ontology MM
Freq. BW. Add
V 2.0 Tool Ind.
OAv3.0
Repository
MODAF
NAF
SOA
V 2.0
NAF V 3.0
NAR
ROADMAP for NATO ARCHITECTURE META MODEL (NMM)
THE FIRST VERSION OF THE NAF METAMODEL IS VERSION 0.8. THIS VERSION IS A NATO VERSION DEVELOPED FROM MODAF METAMODEL (M3) VERSION 1.0, AND DOES NOT CONTAIN ANY OF THE REMAINING ELEMENTS NEEDED TO SUPPORT A HARMONIZED NAF
IN THE FINAL VERSION OF NAF WE WILL DELIVER NMM VERSION 1.0 WHICH WILL INCLUDE OVERARCHING ARCHITECURE METAMODEL V 2.5, MODAF M3 V2.0, MODELS TO SUPPORT AEM V2.0 AND NISP V1.0
WE WILL ESTABLISH A PROJECT TO REALIZE THE NATO ARCHITECTURE REPOSITORY, AS A MAJOR PART OF THIS PROJECT WE PLAN TO INCORPORATE INFORMATION RELATED TO NATO MATURITY LEVEL, NATO INTEROPERABILITY ENVIRONMENT, SUPPORT FOR BANDWITH AND FREQUENCY , IDEAS ONTOLOGY MODELS, AND BUSINESS PROCESS MODELS DONE IN ARIS MODELLING TOOL.

13. Action Items Completed
AI 15/5
AI 15/8
AI 15/16

14. Actions Items Ongoing
AI 15/12
AI 15/20

15. Actions Items to be closed
Following Actions Items will be taken by the NRS and adressed during the final compilation of the NAF, and NRS propose to close them.
15/2
15/3
15/7
15/11
15/19
15/24
For those not closed, at least the enddate must adjusted to end of May 2007.

18. Agile and adaptive Forces, through interoperable Architectures
LADIES AND GENTLEMEN
YOU HAVE KNOW RECEIVED A TASTE OF WHAT CAN BE EXPECTED OF THE NEW NAF
WHAT TYPE OF NEW FUNCTINALITY IT COVERS
UNFORTUNATELY DID THE TIME NOT ALLOW US TO GO INTO MORE DETAILS,
BUT I HOPE YOU AT LEAST HAVE BEEN CURIOUS AND WANT TO KNOW MORE ABOUT NAF AND THE BENEFIT IT CAN PROVIDE.
THANK YOU

21. Chapter 1: Introduction to NATO Architecture Framework
This chapter is dependent on the content of the other chapters. It will be finalized when the other chapters have been finished. It is about 90 percent complete.
Chapter 1 is the scene setter for the NAF. It describes what is in the NAF and how the NAF is used to accomplished NATO and National architecture objectives
Some rework is needed based on missing parts within the other chapters and the harmonization needed between chapters 3, 4, and 5.
It will require about two weeks to complete this chapter once the above mentioned rework has been done.

22. Chapter 2: Architecture Stakeholders
This chapter is essentially complete. It is important that this chapter is thoroughly reviewed by the various stakeholders described in the chapter. This chapter is dependent on chapter 6 for the description of the stakeholders involved in architecture governance
Chapter 2 defines the various architecture stakeholders and communities of interest (COIs) to provide a basis for analyzing the architecture elements addressed by chapters 3, 4, 5, and 6.
Rework is expected once chapter 6 is completed and once feedback from the stakeholders has been received
The amount of time expected to incorporate the changes resulting from a review of this chapter is small

23. Chapter 3: Architecture Concepts and Elements
A full draft of Chapter 3 is included in this release of NAF
This chapter identifies and describes the things that are important and that should be designed and described in an architecture (ingredients of architecture, architecture elements), and gives some reasoning why they are important.
Significant issues were discovered during a review by the NRS and need to be resolved in the next release. The issues mainly highlight inconsistencies between chapter 3 and other chapters
Chapter 3 needs to be harmonized with chapters 4 and 5, possibly leading to further rework of these chapters.

24. Chapter 4: Architecture Views and Subviews
Chapter 4 is an extensive chapter and many subviews, examples and metamodel diagrams still need to be incorporated or modified. The chapter is about 80 percent complete.
This chapter details the views and standard subviews that can be used to describe an architecture and are supported by the NATO metamodel (NMM).
An updated version of the NMM is needed to finish this chapter. Some subviews still need to be described, many examples and diagrams need to be developed or changed, and the Running Example needs to be elaborated and polished. With the chapter 3, 4, and 5 harmonization, it can be expected that several subviews will be changed or added.
The remaining 20 percent of work, not dependent on inputs from the other chapters (other than the NMM), is relatively minor. Harmonizing this chapter with chapters 3 and 5 will require a more substantial amount of rework.

25. Chapter 5: NATO Architecture Metamodel and Architecture Data Exchange Mechanism
The metamodel contained in chapter 5 is NMM v 0.8, which is based on MODAF Metamodel Version 1.0 and includes few of the NATO-derived additions. The NMM is not complete.
MOD UK sponsored development of NMM v0.8, but can no longer support NATO requirements which are “over and above” UK requirements. UK has proposed that NATO finance what is needed to complete the NMM. A Statement of Work (SOW) has been established that describes NATO NAF requirements and products.
This chapter presents the NMM in a way that allows architecture tool vendors and implementers of architecture repositories to capture and support the development of NAF compliant architectures. This chapter describes the concepts that lie underneath and are common to all views, subviews and architecture elements in chapters 3 and 4.
The remaining work essentially revolves around completing the NMM and writing it out in full. Completion of the NMM largely depends on the harmonization of chapters 3, 4, and 5. It can be expected that the NMM will be modified accordingly.

26. Chapter 6: Architecture Governance
Chapter 6 currently contains a listing of essential architecture governance elements in a bulleted format. These elements are not yet related to the main NATO life-cycle processes. This chapter is about 25% complete. There exists a two-way dependency relationship with the NID, which is currently being revised
This chapter focuses on two aspects of architecture governance: it details the essential controls, products, processes, roles and responsibilities, necessary to manage the architecture life-cycle (both products and framework), and describes how these essential elements can be embedded within the main NATO life-cycle processes.
The essential architecture governance elements need to be elaborated upon and related to the NATO life-cycle processes.
The writing out of the essential elements is a minor task. However, the description of the relationships with NATO processes requires a thorough analysis of these processes, and, as such, constitutes a major effort. Finally, this chapter needs to be synchronized with the subsequent version of the NID and chapter 2 of the NAF.

27. Chapter 7: Architecture Definitions, Terminology, Ontology
Chapter 7 currently includes a comprehensive list of architecture-related definitions, abbreviations and acronyms.
The architecture ontology and taxonomy have not yet been addressed
It has been recognized that an ontology is needed to ensure consistency across architectures.
The International Defence Enterprise Architecture Exchange Specification (IDEAS) working group is currently developing, among other things, a defence enterprise architecture ontology to support exchange of architecture information between nations. The aim is to have an international standard which the NAF can incorporate, once it is finished.
The list of definitions, abbreviations and acronyms must be updated once the chapters are completed. This does not require much effort.

28. Annexes
ANNEX A: NC3A Architecture Engineering Methododogy. The existing version of the AEM is specific to the Bi-SC AIS Target Architectures. It is currently being revised and will not be available until later this year. It will not be included in this release of the NAF.
ANNEX B: Transition Guidance NAF v2 to NAF v3. Describes a process for converting a NAF Version 2-developed architecture into one that is compliant with NAF Version 3. This ANNEX will be developed once the NAF Version 3 has been completed. ANNEX B will be provided in a subsequent release of NAF Version 3.
ANNEX C: NATO Architectures. Lists the architecture products suggested by the NATO Interoperability Directive (NID) to describe the various types of NATO architectures. The NID is currently under revision and ANNEX C will be developed in synchronization with the NID. ANNEX C will not be provided in this release.