Frits Broekema Principal Scientist NATO C3 Agency NATO’s approach to Enterprise Architecture Integrated EA Conference ‘09 24 February 2009 Frits Broekema Principal Scientist NATO C3 Agency NATO / EAPC Unclassified

NATO / EAPC Unclassified Outline Introduction NATO & NC3A Enterprise Architecture approach Services Framework Architecture means Introduction NATO & NC3A: Context: NATO & NC3A NNEC Concept Enterprise Architecture Approach Transformation & Convergence Services as the unifying paradigm (incl SOA) Holistic approach, zoom-in on NATO specifics Services Framework Taxonomy 3 types of services Architecture Means NAF NMM & ADEM NAR NATO / EAPC Unclassified

NATO: Political & Military Alliance A Political organisation A Military organisation Collective Defence Diplomacy Cooperation Dialogue / Consensus Anti-terrorism Operations Crisis Response Operations Maintaining adequate military capabilities NATO is an intergovernmental organisation of 28 member countries that retain their full sovereignty. Al NATO decisions are taken jointly by the member countries on the basis of consensus. NATO’s Tasks Acting as a foundation of stability in the Euro-Atlantic area Serving as a forum for consultation on security issues Deterring and defending against any threat of aggression against any NATO member state Contributing to effective conflict prevention and engaging actively in crisis management Promoting wide-ranging partnership, cooperation and dialogue with other countries in the Euro-Atlantic area Safeguard Security of NATO members and ensure the stability of the Euro Atlantic Area NATO / EAPC Unclassified

NATO Consultation, Command & Control Agency (NC3A) Supporting full C4ISR life cycle: acting as a catalyst, a facilitator, a coherence agent and a delivery agent for many NATO systems and capabilities. C3 Policy, Concept & Architecture NATO Chief Architect Operations Research Communication and Information Systems Command and Control Systems Acquisition Customers: Allied Command Operations Allied Command Transformation NATO HQ Nations Mission NC3A: To support NATO through the seamless provision of unbiased scientific support and common funded acquisition of Consultation, Command, Control, Communications, Intelligence, Surveillance and Reconnaissance (C4ISR) capabilities. NC3A’s areas of expertise, or core competencies, are organized into nine capability area teams: Capability Planning and Architectures Interoperability Exercises and Training Operations Planning and Execution (J3/J5) Intelligence, Surveillance and Reconnaissance Integration Support and VAS Core Services Information Assurance and Service Control Infrastructure Services NATO / EAPC Unclassified

NATO Transformation Challenge Streamlining the Strategic Commands NATO Response Forces Prague Capability Commitments While recognizing: Coherence, Consensus & National sovereignty NATO Network Enabled Capabilities (NNEC) At their meeting in Prague, NATO Heads of State and Government opened a new chapter in the Alliance's history by inviting seven countries to Accession Talks and committing themselves to equip NATO with new capabilities to meet the security threats of the 21st century. Official definition of NNEC (as decided by the NAC): NNEC is the Alliance’s cognitive and technical ability to federate the various components of the operational environment, from the strategic level down to the tactical levels, through a networking and information infrastructure (NII). NNEC is the ability of NATO to deliver precise and decisive military effects with greatly enhanced speed and accuracy as a result of closely linking sensors, decision makers and weapon systems NATO / EAPC Unclassified

Key Architecture Principles Single set of architectural descriptions covering the entire NATO Enterprise, spanning different stages in time Unambiguously defined information as the central subject Operational objectives as the common foundation for Architecture and Capability development Modular Production: Models to capture primitives and their relationships Modular Descriptions: Services as the unifying paradigm Modular Presentation: NAF (and other) Views Modular Delivery: Question-driven architecture products Single set of architectural description 3 types/levels of architecture descriptions: Overarching Architecture (Enterprise level description): Long Term: 10-12 years Reference Architecture (Domain level descriptions): Mid Term: 3-6 years Target Architecture: (Project/System level description): Short Term: 1-2 years Information as the central subject The requirement for NNEC emerges from the need for NATO forces to be able to undertake Effects Based Operations. Key requirements for this are: Better decision making Better shared understanding Better information sharing Modular production Making use of an Architecture methodology, like ADM (TOGAF), AEM (NC3A) NATO / EAPC Unclassified

Purpose of Enterprise Architecture in NATO The Overarching Architecture (OA), which may be thought of as NATO’s Enterprise Architecture, provides consistent context for NATO and associated national architecture development. OA will be linked to all subordinate architectures: this allows architecture to be a more effective tool to support systems development. OA focuses on the interfaces between systems. As a consequence services needs to be designed: NNEC Services Framework The OA provides the context for further architecture development within NATO and for national architecture development. The OA will be the authoritative source for defining the scope of subsequent architectures. RA’s and TA’s. This allows architecture to be a more effective tool to support C3 systems development; thus more responsive to the needs of the operational user and more cost-effective. The current OA focuses on the interfaces between systems. As a consequence User Services, that represent the contents of CIS rather than the external interfaces to other systems, needs to be developed. NATO UNCLASSIFIED

Three classes of Services What the operation needs to achieve NATO Missions: Real-world action and effects Cognitive dimension Operational Services User’s View What CIS needs to provide Users: Human and information dimension User Information Services This line of reasoning leads to three main classes of services: Operational Services capture in a neutral and functional manner the essence of what is happening in NATO operations; User Information Services capture what functionality a user of a CIS needs to have at his disposal in order to fulfil his tasks in an operation; NNEC Technical Services capture what technical functions needs to be implemented in CIS. Stress out that the Operational Services and the User Information Services are defined & described from the point of view of the users. The NNEC technical services are defined & described from the point of view of the builders. What technology needs to support Information Technology: Computer “systems” & Comms dimension NNEC Technical Services Builder’s View NATO UNCLASSIFIED NATO UNCLASSIFIED

NNEC Services Framework User’s View Operational Services User Information Services The services of the three types of services are grouped in the so called NNEC Services Framework. The NNEC Services Framework is a taxonomy of services, that consists of a three areas (one area for each type of service), and within each areas of sub-areas, categories and groups. All three types of services are linked to each other: <click> For each OS is determined which UIS are needed by the user in order to fulfill his task (operational service) <click> For each UIS is determined which NTS (which technology) is required. Builder’s View NNEC Technical Services NATO/EAPC UNCLASSIFIED

Use of Services Framework Concepts, Doctrine & Organization Operational Capabilities Information Requirements Candidate Information Services Required UIS Mapping Fan out CoI specific Common/ shared Implementation Objectives Implementation Priorities Required Components Existing New Implementation harmonization NNEC Services Framework Operational Services User Information Services NNEC Technical Services Build 1 – From a services requirements perspective, there is a need to engage the relevant CoIs to ensure the required User Information Services and associated NNEC Technical Services are validated and reflected in the Services Framework Build 2 – From an implementation planning perspective, there is a need to engage the relevant CoIs to set meaningful services implementation objectives and priorities, and to harmonize services implementation with developments in operational concepts, doctrine and SOPs, etc.

NATO Architecture Framework v3 NC3A is tasked by NATO C3 Board (Nations) to apply the NAF v3 to all its architectural activity, including the maintenance of CIS baselines, and to ensure that all architectural data is stored electronically in an architecture repository (NAR) such that it is available for re-use and export in accordance with the NATO Meta Model & Exchange Data Exchange Mechanism. Tasked NATO CIS Services Agency (NCSA) to utilize NAF v3 and extant NAR data when providing, operating and maintaining CIS services and for the maintenance of their CIS baselines The NATO Communication and Information Systems Services Agency, NCSA, is a service provider to NATO and national customers. Wherever NATO deploys on operations or exercises, NCSA provides communication and information systems (CIS) services in support of the mission. NATO/EAPC UNCLASSIFIED

NATO/EAPC UNCLASSIFIED NAF v3 Principles Wider application of the architecture products, serving a broader audience (Ch 2) Use of 7 types of views and constituting sub-views to communicate architecture descriptions (Ch 4) Contents of the views and sub-views based on architecture elements developed using a methodological modeling approach (Ch 3) Installation, use and maintenance of a NATO-wide repository for architecture data: NAR (Ch 5 & 6) Architecture elements stored in the NAR are defined by the NAF Meta-Model (NMM v1.0) (Ch 5) Exchange of architecture data (elements and views) based on strictly defined specification and mechanism: ADEM (Ch 5 & 6) The data in the NAR is methodology and tool agnostic Use of the NAR, NMM, ADEM does NOT presuppose or require any specific methodology or tool NAFv3 is without classification and is available to all. NATO/EAPC UNCLASSIFIED

NATO Architecture Framework (NAF) v3 CAPABILITY VIEW NATO ALL VIEW NATO OPERATIONAL VIEW NATO PROGRAMME VIEW Three new views (and sub-views) in relation to NAF v2.: NATO Capability View (NCV) NATO Service Oriented View (NSOV) NATO Programme View (NPV) NATO SERVICE ORIENTED VIEW NATO SYSTEM VIEW NATO TECHNICAL VIEW NATO/EAPC UNCLASSIFIED

Consistent, Coherent & Comprehensive Views: appropriate to answer the original question Models: strong rationale, verifiable, repeatable, extendable NATO Architecture Repository Domain Ontology Domain Functions Model Types of Locations Operational Services Model Interaction Model Working Positions Model Logical Process Model Implementation Process Model Organization Chart Asset Allocation Collaborations Model Object Clusters Model Communities Model Communication Flows Model Information Model Data Model Information Systems Service Architecture Information Systems Component Specification Architecture Information Systems Component Implementation Architecture Types of Locations Technical Infrastructure Service Architecture Technical Infrastructure Component Specification Architecture Technical Infrastructure Component Implementation Architecture NATO CAPABILITY VIEW ALL NATO OPERATIONAL VIEW NATO PROGRAM VIEW NATO SYSTEM VIEW NATO TECHNICAL VIEW NATO SERVICES VIEW NAF V3 Target Architectures: Implementation Overarching Architecture: Services Framework Reference Architectures: Solution Patterns Clear separation in NAR between Core data, Models and Views Core data holds all elements and relationships Models use Core data for analysis and to create more, new Core data Views use Core data to make NAF-compliant subviews Based on NATO Meta-Model NMMv1. Links to: DoDAF & MoDAF NATO/EAPC UNCLASSIFIED

NAR Operational Concept Architecture Data Exchange Mechanism The repository is available for several types of “users”: NATO architect/contributor: for creating architecture date, developing models & developing views Users/Reviewers: for defining, extracting and reviewing views For National Architects and Administrator <click>: next slide NATO/EAPC UNCLASSIFIED

National use and contributions Architecture Data Exchange Mechanism Nations (NATO & EAPC) can: Receive a copy of any architecture data, adhering to normal info exchange rules Provide national data to the NAR, while indicating info sharing constraints NAR Configuration Management (NAF v3) will apply in accordance with NAF v3 Ch 6: all new architecture data in accepted in the “Proposed NAR” environment and promoted to the “Approved NAR” environment once made consistent and coherent with existing NAR data All use the Architecture Data Exchange Mechanism National Architects: for extracting architecture data, models & views and to provide national architecture data Administrator: for maintaining and governing the NAR content NATO/EAPC UNCLASSIFIED

Questions? frits.broekema@nc3a.nato.int NATO/EAPC UNCLASSIFIED NATO UNCLASSIFIED 17

Contacting NATO C3 Agency NC3A Brussels Visiting address: Bâtiment Z Avenue du Bourget 140 B-1110 Brussels Telephone +32 (0)2 7074111 Fax +32 (0)2 7078770 Postal address: NATO C3 Agency Boulevard Leopold III B-1110 Brussels - Belgium NC3A The Hague Oude Waalsdorperweg 61 2597 AK The Hague Telephone +31 (0)70 3743000 Fax +31 (0)70 3743239 Postal address: NATO C3 Agency P.O. Box 174 2501 CD The Hague The Netherlands NATO / EAPC Unclassified