Mr Ken Hong Fong, US DoD

1
THE NEED FOR INTEROPERABILITY AMONG
OPERATIONAL PICTURES
Mr Ken Hong Fong, US DoD Interoperability
Office Office of the Under Secretary of
Defense (Acquisition, Technology and Logistics)
OMG Technical Conference Paris, France
2
OVERVIEW

• WHAT IS INTEROPERABILITY?
• HISTORY OF THE SHARED TACTICAL GROUND PICTURE
  (STGP) INITIATIVE
• CHALLENGES
• THE PROBLEM
• DoD SOLUTION
• CONCLUSION / QUESTIONS

3
WHAT IS INTEROPERABILITY?
We will connect Information systems and weapons
in new ways President George Bush New York
Times, 25 March 2001
Operations Other Than War
The ability of systems, units, or forces to
provide services to and accept services from
other systems, units, or forces and to use the
services so exchanged to enable them to operate
effectively together (JCS Pub 1)
Focus is on Effective Joint and Combined
Operations
4
HISTORY OF THE STGP INITIATIVE

• BRUSSELS SEP 00
• Participants
• (FR, IT, GE, UK, US, NC3A, NAFAG, Air Group IV)
• Definition Presented
• Desired End State
• Shared Ground Picture Available at All Levels
  of Command
• Tied to Concepts and Doctrine
• Ability to Link Selected Sensor and Shooters in
  Shared Information Grid
• Command and Control (C2) Information exchange
  to include Situational Awareness (SA)
• NC3A to Develop a First Order Analysis
• Strategic Way Ahead

5
HISTORY OF THE STGP INITIATIVE

• MULTI-NATIONAL PRESENTATION OCT 00
• NC3A HOSTED TECHNICAL WORKING GROUPS
• NOV 00 / JAN 01 / FEB 01
• First Order Analysis Developed
• PRINCIPALS MEETING (APR 01)
• Refine and Enhance the First Order Analysis
• ADDITIONAL TECH MEETINGS (MAY /JUN 01)
• PRINCIPALS MEETING (SEP 01p)
• ACTIVITIES BEGIN (NOV 01p)
• DEMONSTRATION OF CAPABILITY (2003p)

6
CHALLENGES

• AGGRESSIVE TIMELINE FOR SUCCESS
• NOT A MATERIAL SOLUTION
• UTILIZE OFF THE SHELF TECHNOLOGIES
• LEVERAGE EXISTING ACTIVITIES (NATO NATIONAL)
• SECURE / CONFIDENT INFORMATION
• TAILORABLE TO CONSUMER
• RAPIDLY DISSEMINATED / REPLICATED / REDUNDANT
• ARCHITECTURE DYNAMIC AND MUDDY
• ABILITY TO FUSE AND CORRELATE
• UTILIZING NATIONAL COMMAND / BATTLE SYSTEMS
• PROVIDE THE WARFIGHTER INCREASED CAPABILITIES

7
THE PROBLEM
No Coherent View of the Battlespace from CINC to
Soldier/Sailor/Airman Inability to Prosecute a
Coordinated Strategy
CORRESPONDING SYSTEMS As-Is / As Planned
AS IS/AS PLANNED Systems Interoperability
NON-Interoperable, Operating Pictures
Intel
Coalition
GCSS
IBS
GCCS-M NAVY
GCCS-AF AIR FORCE
IAS MEF
Korea only
Capability to synch these systems IF identical
COE level SW version w/ COP Synch Tools
TCO (GCCS-M)
ADOCS
DTSS
IAS (GCCS-M)
TBMCS
I3
IOW (C2PC)
AFATDS
ADSI
JTIDS
IMETS
AFATDS
ISYSCON
JCTN
DDS-CEP (CEC)
C2P
DACT (C2PC)
FBCB2
FAADC3I
GCSS-A
Land Warrior
GTACS
CD
DRAFT
TAOC
Interface status
Planned, but not imp.
Implemented
Not a program
Key
System status
Planned
Synchronized
Implemented

• The cause multiple systems, conceived and
  developed individually
• Compounding the problem systems, TTP, missions
  changing continuously, new coalition partners,
  stovepiped intelligence dissemination

Inadequate interoperability fratricide,
leakers, lack of effectiveness
8
US DoD SOLUTION FAMILY OF INTEROPERABLE
OPERATIONAL PICTURES (FIOP)
Horizontal and Vertical System Interoperability
Across Service Lines and Between Echelons
Coherent view of the Battlespace More than
Situational Awareness More tactical-level cross-S
ervice interoperability Based on required
capabilities at each echelon Coherent view of the
Battlespace
COP - Common Operating Picture JTF - Joint Task
Force CTP - Common Tactical Picture
Federating the Battlespace Pictures
9
WHAT IS THE FIOP GLUE?
1. Direction Vector for Relevant Department
Initiatives 2. Federating Data Strategy 3.
Fusion Strategy 4. Information Security
Architecture for 30 Systems
Coalition Partners
Allies
JT GCCS
COP Level
CINC Level I/O
JTF/CTP Level
GCCS-A
GCCS-AF
Component Command Level
Component Level I/O
TCO
ADOCS
Additional Interfaces as Required
CSSCS
ASAS

TBMCS
Division and Equivalent Command Level
AMDWS
C2PC/ MSBL
ADSI
AFATDS
JCTN
JTIDS
FBCB2
FBCB2
FA BCS
DACT
Firing Unit Level
AD BCS
GTACS
Omni tracks
TAOC
Tactical Level I/O
10
A SAMPLE INTEROPERABILITY GLUE RECIPE

• ONE CUP OF SUGAR
• DETAILED PROCESS MODEL THROUGH UML
• INFORMATION AND DATA STRUCTURE UNDERSTANDING
• DEVELOPMENT OF INTERFACE DEFINITIONS, I.E. XML
  / JAVA
• USE OF INDUSTRY STANDARD OBJECT SPECIFICATIONS
  AND INTERFACES
• USE OF ROBUST OBJECT BROKER MODULES
• AGREEMENT ON CONCEPT OF OPERATIONS AND
  INFORMATION SECURITY PARADIGMS
• EVOLUTIONARY DEVELOPMENT, TEST AND DEPLOYMENT
• CONTINUOUS IMPROVEMENT THROUGH STRUCTURED
  RELEASES
• OPTIMIZATION OF TECHNOLOGY ADVANCES
• ADD TWO CUPS OF VISIONARY THINKING
• SPRINKLE LIBERALLY WITH TOP MANAGEMENT SUPPORT
• SIMMER AND STIR OCCASSIONALY
• SERVE HOT WITH HOLIDAY REFRESHMENTS

11
INTEROPERABILITY BUSINESS ISSUES

• HUNDREDS OF DISPARATE SYSTEMS
• THOUSANDS OF OPERATIONAL NODES
• HUNDREDS OF BUSINESS POINTS OF ENTRY
• TWO COMMON THEMES
• INDUSTRY STANDARDS ? OMG
• EXPERIENCE COUNTS
• AWARENESS IS INCREASING EXPONENTIALLY
• FOR GLUE SOLUTIONS

12
CONCLUSION / QUESTIONS

• NEED IDENTIFIED DEFINED
• CHALLENGES
• PROBLEMS
• DoD GLUE SOLUTION
• RECIPE REQUIRES
• OMG / GOVERNMENT PARTNERSHIP
• BUSINESS ISSUES IDENTIFIED
• QUESTIONS?