190 likes | 388 Views
The NATO HQ need for the Web: How policy requirements are affected by the need to take web development into account. Georges D’hollander Maj Gen, BEAR Director, NHQ C3 Staff, and also Vice-Chairman NC3 Board. Briefing Outline. Background Transformation
E N D
The NATO HQ need for the Web:How policy requirements are affected by the need to take web development into account • Georges D’hollander • Maj Gen, BEAR • Director, NHQ C3 Staff, and also • Vice-Chairman NC3 Board
Briefing Outline • Background • Transformation • Interoperability • Architectures • NATO Maturity Levels • NATO Interoperability Standards and Profiles • Information Management • Information Assurance • Conclusion
Transformation (1) • Dramatic slimming down of NATO command structure • Establishment of: • Allied Command for Operations (Mons, BE) • Allied Command for Transformation (Norfolk, USA) • Establishment of NATO response force: • Small, agile, highly deployable • Multinational composed of contributions from many nations, • some contributions small in size • NATO led operations include force contributions from many NATO and non-NATO nations
Transformation (2) Vulnerabilities Political Dependencies Military Economic Information Links Strengths Nodes Infrastructure Social Relationships Weaknesses • NRF seen as a key catalyst to help transform NATO: • Rotation cycle of 6 months • A challenge to interoperability at all levels • NATO commands adopting an Effects Based Approach to Operations and have identified 7 key Transformational Area (ToAs)
NNEC Strategic Framework NEC National Initiatives and Coordination • NNEC Foundation Document • Political Guidance NNEC Strategic Framework Vision and Concept Business Case Roadmap • NNEC Feasibility Study • Commercial world • Transformation Objective Areas inputs Compendium of NNEC related Architecture Development of other Transformation Objective Areas Detailed Plan
Interoperability • What is interoperability? • Human • Technical • Procurement • Interoperability epochs • Yesterday • Today • Tomorrow
Interoperability - Systems and Standards • Key multinational initiatives: • TACOMS (Post 2000) • Secure Communications Interoperability Protocol (SCIP) • Waveform development • Exploitation of Software Defined Radio • NATO Friendly Force Indicator (NFFI) • Multilateral interoperability Program (MIP) • Core enterprise services • Many of these had been initiated well before the NNEC Feasibility Study, but fit well with the recommendations • But also note: • The good thing about standards is that we have so many to choose from! • So need to focus on idea of net readiness and clear out the old standards • Multiple Commercial Technologies! • Web Services XML, OWL .Net, J2EE • Data Mediation Portals Replication • Intelligent
Briefing Outline • Background • Transformation • Interoperability • Architectures • NATO Maturity Levels • NATO Interoperability Standards and Profiles • Information Management • Information Assurance • Conclusion
NATO Architecture Development NNEC Convergence System of Services Federation of Systems 2010 Service Orchestration 2009 SoSE CP NML Evolution NISP Evolution CP 2008 Service Definition CP CP 2007 CP CP CP CP CP CP 2006 Service Centric System Centric
NNEC Architecture Framework Users & Missions Information Assurance Service Management & Control Funct Serv TOAs Community of Interest SI COP InformationIntegration XML Registry CES Networking & Information Infrastructure (NII) Communications waveforms SDR IP, SCIP Governance • 6 Service areas
Architecture Companions: NML & NISP Service Management & Control User Missions Operations Information Integration Communi cations Community of Interest Information Assurance NML ServiceCategories & Groups Requirements Guide & assess Mission Space Information Applications Technical Infrastructure Aspect Areas NISP Standards & Profiles Abstraction levels Functionality Overarching Architecture Enterprise Reference Architectures Construction Implementation Target Architectures
NRF LAND Layer 5 Users & Missions Layer 5 Users & Missions Layer 5 Users & Missions Layer 4 Functional Area Services Layer 4 Functional Area Services Layer 4 Functional Area Services Layer 3 Information & Integration Services Layer 3 Information & Integration Services Layer 3 Information & Integration Services Layer 2 Communication Services Layer 2 Communication Services Layer 2 Communication Services Layer 1 Vision Policy Architecture Processes Layer 1 Vision Policy Architecture Processes Layer 1 Vision Policy Architecture Processes NISP Emerging Profiles • Service Oriented • Net-Centric & Integrated Information Services for: • Information Sharing with various partners • Support across varying mission classification levels • Interconnected by diverse & transitional communications services • Meshed Functional COIs and Enterprise use • Profiles for Services (e.g. Messaging, Discovery, Collaboration) • Transport Layer Profiles based on IPv6 NRF NATION A NRF NATION B MANAGEMENT SECURITY MANAGEMENT SECURITY WEB BROWSING, MESSAGING, DISCOVERY, COLLABORATION IPV6, TCP, UDP, FIBER OPTIC, ETHERNET, Service Interoperability Point
Briefing Outline • Background • Transformation • Interoperability • Architectures • NATO Maturity Levels • NATO Interoperability Standards and Profiles • Information Management • Information Assurance • Conclusion
Key IM Objectives • Supporttheachievement of Information Superiority • Optimise the use of information resources • Support the identification and preservation of information of permanent value
Increased Information Flow • Achieving interoperability more data can be transferred and more information will be exchanged and available • Different information needs at different command levels
Information Management • What is IM about? • IM aspects: • Industry - Technology • Human • Doctrine • Procedures • Organisation (Chief Information Officer) • Quality • Security
Briefing Outline • Background • Transformation • Interoperability • Architectures • NATO Maturity Levels • NATO Interoperability Standards and Profiles • Information Management • Information Assurance • Conclusion
Information Assurance Challenges • IA Roadmap and IA Business Casein support of NNEC Strategic Framework documents • Secure and Flexible Transport Services • Secure and Dynamic Information Sharing • NII Security Management and Cyber-defence • NEC Security concepts, Policy and Architecture • Information Assurance Subcommittee Response • Cross domain Issues • Technical IA Services • Security Management Infrastructures • Cryptographic Services
Conclusion • Driven by the mission to ensure provision of interoperability allied with transformation and NNEC… • policy and other regulatory documents, including governance are biased by the need to take web development into account