Dr. Vitalij GarberDirector Interoperability

Office of the Under Secretary of DefenseOUSD(AT&L)

Ninth Annual State of Modeling & Simulation

Briefing to Government and Industry May 23, 2000

System of Systems Interoperability- Evolving Capability to Support the Warfighter -

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)23-05-2000

2. REPORT TYPEBriefing

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

4. TITLE AND SUBTITLESystem of Systems Interoperability - Evolving Capability to Support the WarfighterUnclassified

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

6. AUTHOR(S)Garber, Vitalij ;

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

7. PERFORMING ORGANIZATION NAME AND ADDRESSOUSD(AT&L)xxxxx, 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. ABSTRACTWhat is Interoperability? ?Ability of systems, units, or forces to provide services to and accept services from other systems, units, or forces andto use the services so exchanged to enable them to operate effectively together.?15. SUBJECT TERMS16. SECURITY CLASSIFICATION OF: 17. LIMITATION

OF ABSTRACTPublic Release

18.NUMBEROF PAGES20

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

Office of Secretary of Defense

Under Secretary of Defense(Acquisition, Technology & Logistics)

Dr. Jacques S. GanslerPrincipal Deputy

David R. Oliver, Jr

Secretary of DefenseDeputy Secretary of Defense

Director, InteroperabilityDr. V Garber

What is Interoperability?

• Interoperability today is the number one problem in jointforce & combined operations -- CINC’s top issue

• Getting worse, not better, as new coalition partnersdevelop, complex systems are acquired, and “fixes” topast problems are applied in stove-piped fashion

• Joint Vision 2010 calls for increasingly network centricwarfare, dependent upon fully interoperable systems

“Ability of systems, units, or forces to provide services toand accept services from other systems, units, or forcesand to use the services so exchanged to enable them to

operate effectively together.” (JCS Pub 1)

4

Help enable the full range of joint and combinedoperations, through Interoperability and CoalitionWarfare initiatives, providing an acquisition focus,and working with C3I, the Joint Staff, JFCOM/CINCs, the test community, the Defense Agencies,the Services, and Coalition Partners.

MISSION

5

Key Initiatives

• Mission Capability Management (MCM)

• Family of Interoperable OperationalPictures (FIOP)

• Joint Distributed Engineering Plant (JDEP)

6

Mission Capability Management (MCM)The Need to Evolve to MCM

Gulf war, Kosovo, Bosnia, and Y2K all demonstratedthe criticality of systems interoperating within adynamic model

● Improve Interoperabiliity

● Support CINCs Operations

● Improve Coalition Capability

“Key to capitalizing on these assets is interoperability amongthe Services” - Vice Adm. William J. Fallon, Commander of the U. S. Second Fleet and Striking Fleet Atlantic

7

Mission Capability Management (MCM) (Implementing System-of-Systems Capability)

PROCESS

IDENTIFYMISSIONAREAS

IDENTIFYMISSION AREA

LEADERS

DEVELOPSYSTEMS

ARCHITECTURE

IDENTIFYGAPSA

AIDENTIFYMISSIONAREAS

IDENTIFYMISSION AREA

LEADERS

IDENTIFYMISSION AREA

SYSTEMSARCHITECTS

DEVELOP/UPDATESYSTEMS

ARCHITECTURES

IDENTIFYDEFICIENCIES

IDENTIFYGAPSA

A

One-Time Tasks

RecurringTasks

DAB etc.

CIO EB etc.

JROC etc.

IDENTIFYNON-MATERIAL

SOLUTIONS

IDENTIFYDEFICIENCIES

B

B Decisions

8

Mission Capability Management (MCM) (Implementing System-of-Systems Capability)

IMPLEMENTATION

* The Defense Acquisition Board is augmented as necessary by PSAs, Joint Staff, CINCs, and Service representatives to discuss the issues

JointInteroperability

SupportOrganization(Proposed)

Across all Mission Areas

USD(AT&L)(DAB+*)

Mission Area CoordinationJOA Joint Staff Lead

ACCOversight

JTA ASD(C3I) Lead

JOINT POLICY USD(P) Lead

JOINT TTPs J-7/Services Lead

GLOBAL INFO GRID ASD(C3I) Lead

•••

1 2 3 4 5 6 7 8 9 10 11 12 13 ...Joint Staff Mission Areas

Fam

ily o

f Int

erop

erab

leO

pera

tiona

l Pic

ture

s

Sing

le In

tegr

ated

Air

Pict

ure

Join

t The

ater

Air

&M

issi

le D

efen

se

Bat

tle G

roup

as a

Sys

tem

Join

t Str

ike

Figh

ter

Prog

ram

Div

isio

n as

a S

yste

m

JTAMDO/BMDO

DIRMA

DIRMA

DIRMA

DIRMA

DIRMA

JSA(s) OUSD(AT&L)/IO Lead

9

Key Initiatives

• Mission Capability Management (MCM)

• Family of Interoperable OperationalPictures (FIOP)

• Joint Distributed Engineering Plant (JDEP)

10

The Problem (1 of 2):

Interface status * Not a program= Planned, but not imp.= ImplementedSystem status = Implemented = Planned

Key

• The cause: multiple systems, conceived and developed individually• Compounding the problem: systems, TTP, missions are changing continuously, new

coalition partners, and stovepiped intelligence disseminationNon-interoperable operating pictures = fratricide & leakers

No Coherent View of the Battlespace from CINC to Soldier/Sailor/AirmanInability to Prosecute a Coordinated Strategy

USER

CINC

JTF

FiringUnit

CONCEPT CORRESPONDING SYSTEMS

Operational-level pictures

Tactical-levelpictures

Aero,Ground,Maritimepictures

MCS

“AS IS” Systems Connectivity: NON-Interoperable, Operating Pictures

JCTN

JT GCCS

GCCS-AARMY

GCCS-MNAVY

GTACS

GCCS-AF*AIR FORCE

C2PC/MSBL

FBCB2

ADOCS

FA BCS

AD BCS

TBMCS**

ADSI

TAOC

TCO

JTIDS

CSSCSAMDWSFAADC2I

ASAS

AFATDS

DRAFTDRAFT

DDS-CEP(CEC)

DACTKoreaonly

USMC

ARMYNAVYUSAF

JOINT

OmniTRACS

C2PC&D

PassiveTap

The Problem (2 of 2)• Individual system requirements have been

generated vice SoS required capabilities for the“family of pictures”– Ideally, required capabilities should drive

system requirements

• No “big picture” assessment for this family ofrelevant operating pictures has been done in theDepartment

– We need to call attention to it and moveforward!

The Solution (1 of 2)

“A Family of Interoperable Operational Pictures”(FIOP)

– More than just situational awareness - includesbattlespace management, fire support, logistics,intelligence, etc.

– Name is in line with a potential ministerial initiative,synonymous with the Common Relevant OperatingPicture (CROP), JFCOM J9 initiative

COPLevel

JTF/CTPLevel

FiringUnitLevel

ComponentCommandLevel

Division andEquivalentCommandLevel

USMC

ARMY

NAVY

USAF

JOINT

Optimum horizontal and vertical system connectivityacross Service lines and between echelons.

More tactical-levelcross-Service comms

Should be based onrequired capabilitiesat each echelon

“TO BE”: Family of Interoperable Operational Pictures

Allies CoalitionPartners

JCTN

JT GCCS

GCCS-A GCCS-M

GTACS

DACT

DDS-CEP(CEC)

GCCS-AF*

C2PC/MSBL

FBCB2

Omni tracks

CSSCS

AMDWSASAS

AFATDS

ADOCS

AD BCS

TBMCS

TAOC

TCO

JTIDS

MCS

FA BCS

ADSI

The Solution (2 of 2)How to Implement the FIOP Concept

TacticalLevel I/O

ComponentLevel I/O

Add

ition

al In

terf

aces

as

Req

uire

dWhat does “glue” mean?

CINC LevelI/O

C2PC&D

14

Key Initiatives

• Mission Capability Management (MCM)

• Family of Interoperable OperationalPictures (FIOP)

• Joint Distributed Engineering Plant (JDEP)

San DiegoSan Diego - SSC San Diego - SSC San Diego - ICSTF - ICSTF - NCTSI - NCTSI

NSWCNSWC Dahlgren Dahlgren

MultipleAEGIS

Baselines/Live

Sensors/TADILsMultipleAEGIS

Baselines

CV/LHDCDS 0/1DD-963G-7/LHACCS-ME-2C

E-2CMCUCEC

NAWCNAWC Patuxent Patuxent River River

GCCS-MLPD-17

RCS

SSC-CharlestonSSC-Charleston

NSWC PHD Dam Neck NSWC PHD Dam Neck

CV/LHD/LHA

ACDS 0/1DD-

963/FFG-7Live

SensorsTADILs

F-14

LINKHWIL

NAWC Pt NAWC Pt MuguMugu

ACSC Wallops Is.ACSC Wallops Is.

DREN

LES-98

NRLNRL

Distributed Engineering & TestEnvironments

RedstoneArsenalGreenville

Tinker AFB LangleyAFB

CampPendleton

JITC

Melbourne

San Diego

USAFJSTARS

USAFAWACS, ASIT

ArmyPatriot,FAAD,

JTADS,

NSA SISSeniorScoutRivetJoint

NavyACDS,

CV/LDH,MLDS, E-2C,

F-14

USAFMCE, ABCCC,ADSI, RADIC,R/SAOC, ASIT

JCSGCCS

NavyACDSNTDSDD963

DahlgrenDam Neck

NavyAGEIS

USMCTERPES

WoodlandHills

USAFF-15

NavyE-2C

Pax RiverUSMCTAOC,

JTAOM,ADCP,

METCALS,ATACC

NSA SISSeniorTroupe

JITCCentral

TestFacility

Eglin AFB

T1 & Sensor SimulationT1 No Sensor Simulation

JITCJOINT TACTICAL DATA LINK

LABORATORY

NAVY DEP

USMCTBMD

PATRIOTTCS/ICC/E

CS

THAAD

JTAGS

PATRIOTICC/ECS

AWACS /CRC

AFC

TestExercise

ControllerDevelopme

ntal

TestExercise

ControllerOperation

al

THEATER MISSILE DEFENSE SYSTEM EXERCISER

JDEP CONCEPT( Combat Systems/BMC4I Hardware in the Loop)

Built upon Collaborative Engineering Environment,and migrates from DIS to HLA

Sensor / Weapons SIM/STM Connectivity (Ground Truth)

JDEP Ops Center(s)

Tactical Connectivity (JPN,JDN,JCTN)

Collaborative Engineering Environment

Communications

Sensors Weapons

AF Systems

TacticalStim/Driver

Communications

Sensors Weapons

Army Systems

TacticalStim/Driver

Communications

Sensors Weapons

Joint Systems

TacticalStim/Driver

Communications

Sensors Weapons

Marine Systems

TacticalStim/Driver

Communications

Sensors Weapons

Navy Systems

TacticalStim/Driver

Voice

VTC

Shared

Apps Test

Planning

Admin

ToolsScheduler Test

Analysis

Data Tools

Repository

Doc

Mgmt

Network

Mgmt

Process/

WorkflowVisualization

HW &CPIL

2003 JTAMD Family of Systems

GC

CS-

M

GC

CS-

M

GC

CS

GC

CS -

A

GC

CS-

A F

•Test Control•SIM Control•Data Extract•Data Reduction

So, where does M&S come in?

• There is a “blurring of the lines” between real systemsand simulations

• Simulation is the only feasible way to develop & test asystem-of-systems

• M&S interoperability is fundamental to success– Simulation Based Acquisition (SBA) is the future for systems

acquisition– Joint Distributed Engineering Plant (JDEP) is a primary

contributor developing new systems and fixing legacy systems– Both of the above will improve systems interoperability

• Exploiting HLA will aide systems interoperability

Clearly, if we want to achieve 100% of warfightingcapability -- we must develop, test, operate andsustain fully interoperable weapons systems.

•Requirements Analysis•System Design & Test•Legacy System Fix•Certification•Training Exercises•Contingency Planning•Operations

-- Interoperability --What Better Resource Than M&S?

M&SSBA

Collaborative Eng EnvJDEPHLA

Function Essential Tools

19

• Modeling and Simulation Indispensible• “Coalition Friendly” Strategy• Partnership with Industry

Summary

20