Proposal for Integrating NATO M

1
(Proposal for) IntegratingNATO MS Effortsand
theNATO C3 Technical Architecture

• Dr. Andreas Tolk
• IABG
• Ottobrunn, Germany

2
Presentation

• NATO Modeling and Simulation
• NATO MS Master Plan
• NATO MS Organizations
• NATO C3 Technical Architecture
• NC3TA Technical Reference Model
• NC3TA Common Operating Environment
• NC3TA Interoperability Reference Model
• Common Objectives of NMSMP and NC3TA
• Proposed Solutions
• Findings and Recommendations

3
NATO Modeling and Simulation

• Document AC/323(SGMS)D/2NATO Modelling and
  Simulation Master PlanBrussels, August 1998
• OrganizationNATO RTO Modelling and Simulation
  Group (MSG)
• Recent MS Activities
• Pre-Pathfinder Experiment
• Pathfinder Experiment

4
The NATO Modelling and Simulation Master Plan
(NMSMP), Version 1.0

• 1996 Conference of National Armaments Directors
  (CNAD) established Steering Group on Modelling
  and Simulation (SGMS)
• Governmental Policy Subgroup (GPSG)
• Military Policy Subgroup (MPSG)
• Industrial Policy Subgroup (IPSG)
• SGMS agreed on Version 1.0 in July 1998
• Approved by the North Atlantic Council (NAC) in
  December 1998

5
Scope of the NMSMP

• Defense Planing
• Training
• Exercises
• Support to Operations
• Research
• Technology Development
• Armaments Acquisition

6
Objectives and Subobjectives of the NMSMP
7
NATO MS Organizational Structure
8
NATO C3 Technical Architecture NC3TA

• NC3TA Technical Reference Model
• NC3TA Common Operating Environment (COE)
  Component Model
• NC3TA Interoperability Reference Model

9
NATO Consultation, Command and Control (C3)
Technical Architecture (NC3TA)

• Models within the NC3TA
• NC3TA Technical Reference Model (NTRM)
• NC3TA Common Operating Environment (NCOE)
  Component Model (NCM)
• NATO Common Founded (NCF) Reference Models for
  Functional Configurations (NFC)
• NATO Reference Model for Open Systems Information
  Exchange (NOSI) STANAG 4250
• NC3TA Reference Model for Interoperability (NMI)

10
NC3TA Technical Reference Model (NTRM)

• Conform with IEEE POSIX Open System Environment
  (OSE) Reference Model
• ApplicationSoftwareEntities (ASE)
• ApplicationPlatformEntities (APE)
• ExternalEnvironment (EE)

ASE
ApplicationProgram Interface (API)
APE
ExternalEnvironment Interface (EEI)
EE
11
NC3TA Common Operating Environment (NCOE)
Component Model (NCM)

• Very close to the US Defense Information
  Infrastructure (DII) Common Operating
  Environment (COE)
• Common Support Application Services
• Infrastructure Services
• Kernel Services
• APIs
• Data
• Supporting Services
• Networking Services

12
NC3TA Reference Model for Interoperability (NMI)

• Degree 1 Unstructured Data Exchange
• Network Connectivity
• Document Exchange
• Message Exchange
• Degree 2 Structured Data Exchange
• Network Management
• Graphics Exchange
• Web Access
• Data Object Exchange

• Degree 3 Seamless Sharing of Data
• Formal Messages
• Common Data Exchange
• System Management
• Security Management
• Degree 4 Seamless Sharing of Information
• Common Information
• Distributed Applications

13
Common Objectives

• Systems Development, Procurement, and Acquisition
• Training and Exercises
• Support to Operations

14
Requirements for Merging of CIS and MS Efforts

• All Components must be Part of an Overarching
  Architecture
• Specification of Functionality
• Specification of Interfaces
• Specification of Input/Output Data
• Use of such Components
• SBA Test Requirements for all Components
• TE Use Simulation for Training with real CIS
• Support to Operations ACOA, Applied MOR

15
Proposed Solutions

• Integrating the High Level Architecture (HLA)
  into the US Defense Information Infrastructure
  (DII) Common Operating Environment (COE)
• Data Federations
• Alignment of Architectures, Data Modules, and
  Procedures

16
Integration of HLA into the DII COE

• COE is composed of configurable, layered,
  reusable software components working together
  with specific mission software to perform a task
• HLA software can be segmented and integrated into
  the COE components

• App. ¼ of the C4I Papers of the Spring SIW 2001
  dealt with possible solutions (Theory and
  Applications)
• C4I/SimSys Interoperability Technical Reference
  Model is broadening these aspects (DII COE,
  NC3TA, LISI, ...)gt Reflector on
  http//www.sisostds.org/siw

• SISO-Paper 00F-SIW-035 (M. Hieb, R. Sprinkle)

17
Common C4I and Simulation Operating Environment
RTI
Legend
C4I
Simulation
18
Data Federations

• Data Federations need
• Data Management
• Common Shared Data Modeling
• Data Alignment
• Migration of Data Driven Legacy Systems
• Information Sharing using the same
  Standardized Data Elements (SDE) for C4I as
  well as for SimSys
• SISO-Paper 01S-SIW-011 (A. Tolk)

19
Using a 5-Level-Schema to build a Data Federation
Global Application
External
Federation Services
Export
Export
Component
Component
20
Alignment of Architectures, Data, Modules, and
Procedures
21
Summary

• Reduced Budgets and Resources
• ? Necessity to avoid Double Efforts!
• Technological Progress (Methodologies and Tools)
• ? We are able to merge!
• Military Requirements
• ? We have good reasons to merge!

22
Recommendations

• Evaluate Actual Proposals
• ? HLA into US DII COE? Data Alignment and Data
  Administration? Common Interoperability
  Framework
• Start Gradual Integration
• ? Liaison (SISO, MSG, NC3TA Developers, ...) ?
  Common Reference Documents ? Harmonization ?
  Full Integration