AFICE Technical and Development Philosophy A briefing to SISO Simulation Interoperability Workshop 4

1
AF-ICETechnical and Development Philosophy A
briefing to SISOSimulation Interoperability
Workshop4 April 2006
Aeronautical Systems Center
Dominant Air Power Design For TomorrowDeliver
Today

• Randyll Levine
• ASC/XRA
• Simulation and Analysis Facility (SIMAF)
• Capabilities Integration Directorate
• 937.255.0672
• randyll.levine _at_wpafb.af.mil

2
Overview

• Challenges
• The End State
• OV-1, Philosophy, Analytical Tiers
• JSBE
• Overview, As Is, AF-Core Link
• CORE Model EAAGLES
• Applications
• FY06 Spiral 2 Build
• AF-ICE Network
• Connection Plans, MCSOA
• FY06 Application A Use Case
• Areas of Development
• Summary

3
Strategic MS ChallengesSite Picture leading to
AF-ICE

• Many uncoordinated programs across AF
• ACDD, CDI, JDEP, Diamond Matrix, VTR, JSB
• Many collaborative environmentsdiffering end
  states
• Non-Aligned Resources
• Fractionalized Strategies
• Poor Performance
• Late to Need.every single time
• Failures of Previous MS Programs
• JSIMS, JMASS, JSB, etc.

No Unified MS Leadership or Vision
4
Tactical ChallengesTechnical and Process
Requirements

• Domain Integration Challenges
• Capability Development
• Network Centric Warfare (NCW)
• Electronic Combat (EC)
• Process Challenges
• Accelerated Acquisition
• Proprietary and Intellectual Property challenges
• Other Challenges
• Multi-Level Security (SAR/SAP/Collateral)
• Test Support
• Correlation with Training

5
The End StateA Simple OV-1
Linked live-virtual-constructive
Scalable, multi-resolution models
Persistent, reusable, interoperable, composable,
integrated
6
End State A Development Philosophy
Tool Suite Development
1
Tool Suite Employment
Design for Test
7
The End StateAF-ICE Analytical Tiers
Tier 1 Decision Support
Data flow
Correlation
Tier 2 Localized CBPA
Scalable, multi-resolution
Digital System Model(s)
Data flow
Correlation
Tier 3 Distributed CBPA
8
Joint Service Battlespace Environment (JSBE)

• JSBE Umbrella Program
• Coordinate Service activities to increase
  interoperability and reduce overlap
• Perform experiments and demonstrations to
  determine shortfalls and provide established
  process for fixing shortfalls
• Ensure Joint issues are addressed
• Individual Service Programs
• Develop Service-specific environments
• Instantiate Service models and databases

• Signatures
• Army Materiel Command/CC
• ASC/CC
• NAVAIR/CC

9
Joint Service Battlespace EnvironmentAs-Is
Designed/Built to Support Specific needs and
various interoperability initiatives
Legacy -Models -Simulations -Data
Training -Models -Simulations -Data
GATEWAYS SI3, HLA, DISetc
GATEWAYS SI3, HLA, DISetc
CURRENT USAF CORE
APIs in Various states Of maintenance
EAAGLES -RT Air Players -RT RF/IR Env
SUPPRESSOR -IADS -Ground Threats
AdHoc ICDs
AMBER -EW Radar
DIADS -Manned IADS -Threat C2 -Threat Data Fusion

• Integration
• Common
• Interface

ESAMS -ACQ Rdr -TTR Rdr
Jul 05 Sep 05

DIS, HLA, SI3, etc
DIS, HLA, SI3, etc
VARIOUS VIEWERS, TOOLS
USA 3CE
Future develop (TRADOC)

Acq RDECOM

TE (ATEC)

• Proprietary
• Models
• Simulations
• Data

Commercial -Models -Simulations -Data
GATEWAYS SI3, HLA, DISetc
GATEWAYS SI3, HLA, DISetc
VARIOUS MODELS
10
AF-ICETop Level Description

• A rapidly composable, distributed network for
  development test
• Includes Virtual and Constructive models linked
  with Live systems
• Incrementally built to support customers
• Common tools and processes
• Automated business rules

Integrated Persistent Reusable
11
The AF-ICE Core ApproachOne Designed USAF
Environment
Designed/Built to Support Interoperability for
Network Enabled Warfare
Legacy -Models -Simulations -Data
Training -Models -Simulations -Data
GATEWAYS SI3, HLA, DISetc
GATEWAYS SI3, HLA, DISetc
AF-ICE CORE USAF Air Components USAF C2/ISR USAF
Weapons USAF Link Models USAF CONOPS IADS
Tools Space
Defined ICDs
Defined APIs
Analysis may not Require the use of CORE
capability But instead use Existing
traditional Link methods
CORE TOOL Features Non-Proprietary Government
Owned O-O Designed Scalable Fidelity Designed/Born
Joint
Common CORE Tools Joint C2ISR Stealth Viewer
DIS, HLA, SI3, etc
USN/MC Core Sea Environment Air
Components Surface Components Subsurface
Components CONOPS Link Models C2/ISR Space
USA 3CE CORE USA Ground Environment USA
BMC2 USA Platforms USA CONOPS USA Link Models
USA Air Components USA Weapons
DIS, HLA, SI3, etc
Acquisition DOMAIN

• Proprietary
• Models
• Simulations
• Data

Commercial -Models -Simulations -Data
GATEWAYS SI3, HLA, DISetc
CORE MODELS/TOOLS
GATEWAYS SI3, HLA, DISetc
Network Connectivity
12
The AF-ICE CoreBenefits of this approach
Facilitates
CommonFramework

• Better Distributed Virtual Simulation
  Capabilities throughout Existing Applications
• An Overall Improvement in Capability for Existing
  Applications. Much Easier to Interface, and Much
  Easier to "Load Balance" Computing Power.
• Significant Capability Improvement that Enables
  the Rapid Construction of Completely New
  Simulation Applications.

Air PlayersSIMAF Growing
Other
ETK
ETK
DIADS
ESAMS
ETK
ETK
ETK EAAGLES Tool Kit Real-Time Frame Based
Environment
13
Extensible Architecture for Analysisand
Generation of Linked Simulations

• EAAGLES - Capabilities based design for
• Electronic combat
• Robust air-to-air and air-to-ground
• Support of hundreds of players

• Proven real-time architecture
• Reconfigurable player representation
• Variable and Scalable Fidelity in H/W S/W
• Integration with / reuse of legacy and other
  codes
• Distributed simulation via DIS and HLA Others
• Robust support for Hardware-in-the-Loop
• Optimized for the PC, platform independent
• Affordable Single PC to Networked clusters
• Community developed and owned, government
  managed software

14
What is EAAGLES? the Design

• Toolkit to Build Distributed Simulation
  Applications
• Composable to address a diverse set of
  requirements
• Provides a well thought out framework
  (architecture) for all the tools to talk to
  each other in a safe and reliable manner
• Provides the boilerplate C code so that the
  behavior of new tools are well defined
• Objects must live by certain rules
• Build Applications With the Toolkit
• F16/Reconfigurable Cockpit Station
• MQ-9 air platform and Operator Station
• Link16
• Munitions

15
Applications F-16 Block 30
16
Full-up ApplicationsF-16 and MQ-9
MQ-9 Ground Station gt
lt F-16 in mini-dome
17
Full-up ApplicationsDistributed Environment
lt F-16s inserted to VF-05
The air war environment in the Virtual
Battlespace Management System (VBMS) gt
18
FY06 Spiral 2 and BeyondFitting the Pieces
Together
Integration - Common Interface
Intelligent Agents -Pilot Decision Logic for
Constructive Agents
C2ISR -Incorporation is TBD but must begin In
FY06
FY07/FY08/FY09
USAF CORE
Weapons Integration -Incorporation is TBD but
must begin In FY06
EAAGLES -RT Air Players -RT RF/IR Env
ETK
DIS
VBMS -Visual -Analysis
ETK
LINK16 -Higher Fidelity Link
Feb 05 Sep 05
SPACE -Incorporation began In FY05GIANT... TBD
if GIANT will be CORE Tool
ETK
DIS
AMBER -EW Radar
DIADS -Manned IADS -Threat C2 -Threat Data Fusion

• Integration
• Common
• Interface

ETK

• ONESAF OOS
• -USA BMC2
• USA Ground Pic
• Red Ground
• Forces

ESAMS -ACQ Rdr -TTR Rdr
ETK
ETK
FY06/FY07/FY08
19
AF-ICE Network ResourcesThe Drive toward a
Persistent Network
Resources
ATIC Avionics Test Integration Complex CAOC-X
Combined Air Operation Center Experimental CEIF
Command Control Enterprise Integration
Facility CVC C4ISR Visualization Center DIADS
Digital Integrated Air Defense Simulation DMOC
Distributed Missions Operation Center DSL
Distributed Simulation Lab (SMC/TD) GWEF Guided
Weapons Evaluation Facility SIMAF Simulation
Analysis Facility SPAIF Space Application
Integration Facility TC Transformation Center
Multi-Channel Service Oriented Architecture
(MCSOA) riding on the DREN is the network
Backbone for AF-ICE in FY06/07/08
Industry nodes committed to connect to AF-ICE
20
A Multi-Channel SOA (MCSOA)Whats a MCSOA buy us?

• Channels available on-demand from any
  participating AF-ICE node
• Publish/subscribe as required via a secure,
  persistent, dedicated net
• Integrated solution Voice, Video, Imagery,
  Analysis, Ops, Data Transfer
• Automated discovery services to provide
  up-to-date relevant capability
• Ability to replicate operational integrated C2
  and tactical AN solutions

Integrated solution available to
every participating AF-ICE node
101001010010 010100101010 101110101000 11010110110
1
21
An AF-ICE Use CaseHigh Fidelity LINK16
Generic Ground C2
J-Series Messages
Generic Air C2
Neutral Air
J-Series Messages
Beyond radar range

J-Series msgs
J-Series msgs
Representative red
J-Series msgs
J-Series msgs
air/adversary threat
Constructive
Maneuvering to
exercise network track
management
Simple ground targets
(4) Virtual F-16 Block 30 cockpits (1)
Automatically piloted airborne, air C2 player
with interactive display for air tracks and Blue
force status (1) Automatically piloted airborne,
ground C2 player with interactive display for
viewing and assigning ground tracks (8-16)
Constructive ground targets, including pop-up
targets (2) Constructive, representative red air
targets (2) Constructive neutral air players
22
Areas of Development

• Core models
• LVC Integration
• ST/Developmental Acquisition/Test/Training
• Architecture/Networks
• IP enabled C2 solutions, IP/Other tactical
  datalinks
• DODAF Linkage
• Domain Integration
• Net-Centric USAF Cross Domain Solutions
• MLS Friendly Solutions
• Industry Integration
• Government Industry collaboration
• Intellectual Property Friendly solutions
• Experimentation/Demonstration
• ICE Breakers serve as the test bed for AF-ICE
  capability
• Joint Service Integration
• DoD Cross Domain Solutions
• Alignment of Joint Capability Spinouts/Spirals

23
Summary

• CORE concept is expanding
• DIADS will join EAAGLES, ESAMS in FY06/07
• Other USAF Domains will follow
• Industry is evaluating (Boeing, NG, LM)
• Network is undergoing definition
• Working Group (WG) led by AFCA
• Security WG led by Industry (LM)
• MCSOA experiment will justify SOA
• Use cases must be developed
• FY06 ICE-Breaker in development
• Net Centric Weapon with ISR AN

24
Additional Information
Tim Menke (Briefing Author) Technical Director,
SIMAF ASC/XRE COMM 937.255.1276 DSN
785- Timothy.Menke_at_wpafb.af.mil Denny
Mrozinski AF ICE Development Team
LeadDirectorate of Capabilities IntegrationHQ
Air Force Materiel Command COMM 937.656.3969 DSN
986- Denis.Mrozinski_at_wpafb.af.mil
25
(No Transcript)