BGen Robert LatiffESC/CV

Enterprise IntegrationUsing Simulation Based

Acquisition

REPORT DOCUMENTATION PAGE Form Approved OMB No.0704-0188

Public reporting burder for this collection of information is estibated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completingand reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burder to Department of Defense, WashingtonHeadquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision oflaw, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS.

1. REPORT DATE (DD-MM-YYYY)01-06-2002

2. REPORT TYPEBriefing

3. DATES COVERED (FROM - TO)xx-xx-2002 to xx-xx-2002

4. TITLE AND SUBTITLEEnterprise Integration Using Simulation Based AcquisitionUnclassified

5a. CONTRACT NUMBER5b. GRANT NUMBER5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S)Latiff, Robert ;

5d. PROJECT NUMBER5e. TASK NUMBER5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME AND ADDRESSUSAF ESC/CVxxxxx, xxxxxxx

8. PERFORMING ORGANIZATION REPORTNUMBER

9. SPONSORING/MONITORING AGENCY NAME AND ADDRESSUnited States Department of DefenseDefense Modeling and Simulation Office1901 N. Beauregard St., Suite 500Alexandria, VA22311-1705

10. SPONSOR/MONITOR'S ACRONYM(S)11. SPONSOR/MONITOR'S REPORTNUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENTAPUBLIC RELEASE,13. SUPPLEMENTARY NOTES14. ABSTRACTThe Challenge Multi-Sensor Command and Control Constellation Architectures Simulation Based Acquisition Enterprise Integration CaseStudy Link-16 Analysis and Engineering Joint Synthetic Battlespace15. SUBJECT TERMS16. SECURITY CLASSIFICATION OF: 17. LIMITATION

OF ABSTRACTPublic Release

18.NUMBEROF PAGES14

19. NAME OF RESPONSIBLE PERSONFenster, Lynnlfenster@dtic.mil

a. REPORTUnclassified

b. ABSTRACTUnclassified

c. THIS PAGEUnclassified

19b. TELEPHONE NUMBERInternational Area CodeArea Code Telephone Number703767-9007DSN427-9007

Standard Form 298 (Rev. 8-98)Prescribed by ANSI Std Z39.18

Slide 2

Objectives

n The Challengen Multi-Sensor Command and Control Constellation

n Architecturesn Simulation Based Acquisitionn Enterprise Integration Case Studyn Link-16 Analysis and Engineering

n Joint Synthetic Battlespacen Conclusion

Slide 3

The Challenge: SystemInteroperability & Integration

CONUSNet

CoalitionNet

Fiber Point of Presence

Op

tical

Fib

er

Joint/Combined Forces

Space Net

Theater Net

DoD ISR Vision 21 Operational Concept

Source: Intelligence, Surveillance, and Reconnaissance Integrated Capstone Strategic Plan,ASD(C3I), 3 Nov 00

“Integrated andresponsive ISR

capabilitiesoperating in acollaborative

enterpriseassuming deliveryof timely, relevantinformation for theNCA and Joint /

Combined forces”

Challenge isGetting there!

Slide 4

The Multi-Sensor C2 ConstellationApproach

• Simulation Enhanced Acquisition• Technology Enablers• Legacy Systems Transition

• Industry Involvement Pivotal• System of Systems Integrator• Teaming Required

PredatorPredator

MC2AMC2A

Global HawkGlobal Hawk

DCGSDCGS

AOCAOC

MC2 ConstellationMC2 Constellation ShootersShootersShooters

MC2AMC2A

SBRSBR

Key Enabler for the Global Strike Task Force Concept

Slide 5

Operational Attributes for MC2A

•• Air Force Air Force•• MT3C MT3C•• BMTC (Cobra Judy) BMTC (Cobra Judy)•• DCGS DCGS•• MP-RTIP MP-RTIP•• Other Other

•• National National

•• Other Service Other Service•• Army (ACS, FCS) Army (ACS, FCS)•• Navy (AEA, MMA) Navy (AEA, MMA)•• CG (Deep Water) CG (Deep Water)•• Other Other

•• Joint Joint•• Coalition Coalition

The challenge is to:• Define / refine the operational “trade space”• Deliver a set of “enterprise solutions”

Slide 6

“Building it right”--Enterprise Integration Begins at the

Architecture View

Slide 7

Systems Architecture—C2ISR Architect’s View

Manage the C2 Enterprise through the nodes.• Each SPO is responsible for managing their node--AWACS, JSTARS, AOC, etc..• Integrated Command & Control SPO manages node integration for interoperability.

Slide 7

Systems Architecture—C2ISR Architect’s View

Manage the C2 Enterprise through the nodes.• Each SPO is responsible for managing their node--AWACS, JSTARS, AOC, etc..• Integrated Command & Control SPO manages node integration for interoperability.

Slide 7

Systems Architecture—C2ISR Architect’s View

Manage the C2 Enterprise through the nodes.• Each SPO is responsible for managing their node--AWACS, JSTARS, AOC, etc..• Integrated Command & Control SPO manages node integration for interoperability.

Slide 6

Operational Architecture—Warfighter View

Node Approach:• Ops Framework• Single Manager• Capability Based

Slide 6

Operational Architecture—Warfighter View

Node Approach:• Ops Framework• Single Manager• Capability Based

Slide 7

What is SBA?

n A process that enables effective systems integration:§ Enterprise Management§ Developmental Planning§ Capabilities/Effects Based Requirements Development

n An initiative within AFMC to provide with integratedsimulations, information technologies and processes to:§ Place the acquisition activity in the warfighter environment§ Reduce cost & time developing & sustaining systems§ Support life cycle product improvement§ Enable information sharing§ Enhance product quality

A Better Product to the Warfighter – Faster!

Slide 8

UCAV

Sensor Craft

GlobalHawk

U2

AWACS

RJ

JSTARSMulti-SensorC2 Aircraft

F15E

JSF AOC

How Should SBA Be Applied?

P3I Upgrades-Sustainment

DT/OTCONOPS/Requirements SystemDesign/Integration

ATD/ACTDs § Throughout Each System’s Life Cycle§ Warfighter/Developer Collaboration—Better Requirements§ Improved Insight to Operational Trades—Supporting CAIV§ Consistent Environment for Design & Test—Reducing Risk

§ Across All Systems§ Real System Interfaces—Ensuring Interoperability§ Family of Systems Considerations—Prioritized Upgrades

Multi-Theater Targeting & Tracking

Capability

A - ConceptDevelopment

B - SystemDevelopment

C - Production/Deployment Support

Slide 9

n Erratic trackingn Dual/multiple track

designationsn Misidentificationsn Track ID conflictsn Frequent track # changesn Frequent track # swapsn Reliance on voice

deconflictionn Operator overload

Air Picture on Link 16 --Today’s Reality

Link 16

JTAOMTAOC

Shooter

Sensor

∩

∩ ∧

∧

TADIL B

ATDL-1

GBDL

SAAWC

RemoteTerminal

Unit

Slide 10

JSF Link 16 M&S Architecture(Remote Host-to-Terminal Interface)

Physical Network (WAN)

Preserves Link 16 network timing including relaysPermits simultaneous multi-net operationsAllows mix of live, virtual & constructive systems

Preserves Link 16 network timing including relaysPermits simultaneous multi-net operationsAllows mix of live, virtual & constructive systems

Host System or Simulation “A”(e.g., TPS-75)

Host System or Simulation “A”(e.g., TPS-75)

Host System orSimulation “D”(e.g., AWACS)

Host System orSimulation “D”(e.g., AWACS)

Host System or Simulation “B”

(e.g., JSF)

Host System or Simulation “B”

(e.g., JSF)

Host System orSimulation “C”(e.g., JSTARS)

Host System orSimulation “C”(e.g., JSTARS)

MASC Link 16 Simulation Federate

Link 16 NetLink 16 NetLink 16 NetLink 16 NetLink 16 Net

Sim’dHost

Sim’dHost

SimulatedLink 16

Terminal

SimulatedLink 16

TerminalSim’dHost

Sim’dHost

SimulatedLink 16

Terminal

SimulatedLink 16

TerminalSimulated

Link 16Terminal

SimulatedLink 16

TerminalSimulated

Link 16Terminal

SimulatedLink 16

Terminal

Slide 11Spiral 2…

SD&D Prod & DeployC

Spiral 1

IOC

Enterprise IntegrationHow to Proceed

Iterative Trades

Schedule

Supportibility& Training

NewSystems

CostTechnology

Performance

Others

CDLCRD

NationalJoint

MT3CMC2A

US Air Force

CONOPs

US Air Force

CONOPs

US Air Force

CONOPs

US Air Force

CONOPs

US Air ForceUS Air ForceUS Air ForceUS Air Force

MNS

MeansM&SMkt Research Govt / Ind

Studies STA & AoAProducts CRD, ORDs, APB, TEMP, Etc

B

Technology

Legacy Sys

CONOPs / MNS / ORD DevelopmentConstellation Concept Development

MNS CRDORDCON

OPS

Enterprise AcquisitionEnterprise Acquisition•• Warfighter needs initiated w/CONOPs Warfighter needs initiated w/CONOPs•• Provide integrated system of systems Provide integrated system of systems•• Driven by Driven by req’d req’d operational effectsoperational effects•• Requirements refined iteratively Requirements refined iteratively•• Non-traditional acquisition strategy Non-traditional acquisition strategy•• Flexible DoD 5000 framework Flexible DoD 5000 framework•• Incremental capabilities delivery Incremental capabilities delivery

LegacySystem

Modernization

Slide 12

WHY?Tactical and Analytical Realism• WarFighter/Developer

Collaboration• Real System Interfaces

(HWIL/SWIL)• Improved Insight to Operational

Trades• Demonstrate Large Scale

Exercises• Interoperability Testing• Family of Systems approach to

System Effectiveness• True Industry/Government

Partnership

Multiple Platforms & Data Links

ValidatedThreats/Scenarios

Distributed Network

Visual RecordingDisplays & Playback

C2ISR

JSBAdvanced Weapons

Warfighterin the Loop

Joint Synthetic BattlespaceA Key Element of SBA

Levels Playing Field Across the Industry-Government Enterprise

Slide 13

Joint Synthetic BattlespaceEnabling Tool for System Acquisition

n Immerses the Acquirer in the Warfighter’s EnvironmentQuicker Fielding – Avoid Redesign/MistakesCost Avoidance – Total Systems SavingsImproved Product – Better Design/Operator Interfaces

• Training

• Mission Rehearsal

• Operations Definition

WARFIGH

TER

• Technology Analysis• Design Trades• Systems Engineering• Integration and Test• Operational Testing

Joint Synthetic Battlespace

• Repeatable

• Variable Resolution/Fidelity

• Verified/Validated/Trusted

• Distributed or Standalone

• “Corporate” Infrastructure

ACQUISITION

JNTF( S W C )

I W C

SMC

O F F U T T A F B ( R J M T )

AFC2TIGF t H o o d ( C C T T )

TACCSFTACCSF

AFRL Mesa5 6 F W

R J1 9 S O S

NCAOC

B e l l

Government Sites

Contractor Sites

Slide 14

Conclusion

n The Challenge: Managing A Complex System ofSystems and ensuring their Interoperability andIntegration

n The Solution: Enterprise Integration usingPrinciples of Simulation Based Acquisitionn With a firm foundation of the Architectural

Perspective grounded in M&S

Enterprise Integration:Achievable Now & Necessary for the Future