NATO’s approach to Enterprise Architecture Integrated EA Conference ‘09 24 February 2009

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

2. Outline • Introduction NATO & NC3A • Enterprise Architecture approach • Services Framework • Architecture means NATO / EAPC Unclassified

3. Diplomacy Dialogue / Consensus Cooperation NATO: Political & Military Alliance A Political organisation A Military organisation Collective Defence Anti-terrorism Operations Crisis Response Operations Maintaining adequate military capabilities Safeguard Security of NATO members and ensure the stability of the Euro Atlantic Area NATO / EAPC Unclassified

4. 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 NATO / EAPC Unclassified

5. NATO Transformation Challenge • NATO Transformation: • Streamlining the Strategic Commands • NATO Response Forces • Prague Capability Commitments • While recognizing: Coherence, Consensus & National sovereignty • NATO Network Enabled Capabilities (NNEC) 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

6. 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 NATO / EAPC Unclassified

7. 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 NATO UNCLASSIFIED

8. 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 Builder’s View What technology needs to support Information Technology: Computer “systems” & Comms dimension NNEC Technical Services NATO UNCLASSIFIED

9. NNEC Services Framework User’s View Operational Services User Information Services Builder’s View NNEC Technical Services NATO/EAPC UNCLASSIFIED

10. Use of Services Framework Concepts, Doctrine & Organization Implementation harmonization NNEC Services Framework Mapping Operational Capabilities Operational Services User Information Services Implementation Objectives Information Requirements NNEC Technical Services Implementation Priorities Candidate Information Services Required Components Required UIS Fan out CoI specific Existing New Common/ shared

11. 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 NATO/EAPC UNCLASSIFIED

12. 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 NATO/EAPC UNCLASSIFIED

13. NATO Architecture Framework (NAF) v3 NATO CAPABILITY VIEW NATO ALL VIEW NATOOPERATIONALVIEW NATOPROGRAMMEVIEW NATO SERVICE ORIENTED VIEW NATOSYSTEM VIEW NATOTECHNICALVIEW NATO/EAPC UNCLASSIFIED

14. Consistent, Coherent & Comprehensive Operational Services Model Types ofLocations Domain FunctionsModel DomainOntology NATO ALL VIEW Working PositionsModel InteractionModel CollaborationsModel Logical ProcessModel NATO CAPABILITY VIEW NATOPROGRAMVIEW Object ClustersModel Types ofLocations Information Model OrganizationChart CommunitiesModel NATO SERVICES VIEW CommunicationFlows Model ImplementationProcess Model Data Model Information SystemsService Architecture Types of Locations Technical Infrastructure Service Architecture NATOOPERATIONALVIEW NATOTECHNICALVIEW Asset Allocation Information SystemsComponent SpecificationArchitecture Technical InfrastructureComponent SpecificationArchitecture NATOSYSTEM VIEW Information SystemsComponent ImplementationArchitecture Technical InfrastructureComponent ImplementationArchitecture Views: appropriate to answer the original question Models: strong rationale, verifiable, repeatable, extendable NATO Architecture Repository NAF V3 Overarching Architecture: Services Framework Reference Architectures: Solution Patterns Based on NATO Meta-Model NMMv1. Links to: DoDAF & MoDAF Target Architectures: Implementation NATO/EAPC UNCLASSIFIED

15. NAR Operational Concept Exchange Mechanism Architecture Data NATO/EAPC UNCLASSIFIED

16. National use and contributions Nations (NATO & EAPC) can: • Receive a copy of any architecture data, adhering to normal infoexchange rules • Provide national data to the NAR, while indicating info sharingconstraints • 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 Exchange Mechanism Architecture Data NATO/EAPC UNCLASSIFIED

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

18. NC3A Brussels Visiting address: Bâtiment ZAvenue du Bourget 140B-1110 BrusselsTelephone +32 (0)2 7074111Fax +32 (0)2 7078770 Postal address:NATO C3 AgencyBoulevard Leopold IIIB-1110 Brussels - Belgium NC3A The Hague Visiting address: Oude Waalsdorperweg 612597 AK The HagueTelephone +31 (0)70 3743000Fax +31 (0)70 3743239 Postal address:NATO C3 AgencyP.O. Box 1742501 CD The HagueThe Netherlands Contacting NATO C3 Agency NATO / EAPC Unclassified