M

1
MS and Weapon Systems Interoperability -
Applying a Robust Capability to a Critical Need -

• Ms. Robin Quinlan
• Deputy Director, Systems Interoperability
• Office of the Secretary of Defense
• 3070 Defense, Pentagon Rm 3C261
• Washington, DC 20301-3070
• quinlarl_at_acq.osd.mil [phone]

2
Office of Secretary of Defense
Under Secretary of Defense (Acquisition,
Technology Logistics) Dr. Jacques S.
Gansler Principal Deputy David R. Oliver, Jr
Director, Interoperability Dr. V Garber
3
Director, Interoperability
Mission

• Help enable the full range of joint operations,
  through Interoperability and Coalition Warfare
  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.

-- Interoperability -- Achieving 100 of
Warfighting Capability
4
What is Interoperability?
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)

• Interoperability today is the number one problem
  in joint force combined operations -- CINCs
  top issue
• Getting worse, not better, as new coalition
  partners develop, complex systems are acquired,
  and fixes to past problems are applied in
  stove-piped fashion
• Joint Vision 2010 calls for increasingly network
  centric warfare, dependent upon fully
  interoperable systems

5
Top 10 Interoperability Issues

• 1. Tactical Data Link Deficiencies
• Many key airborne platforms (USMC F/A-18, EA-6B,
  F-16, HARM targeting systems (HTS-IDM AFAPD) do
  not support Link 16 operation (Kosovo Lessons
  Learned). A common engineering approach to
  bridge legacy systems (Link 11, 11A) to future
  systems (Link 16, IBS) must be determined.
• 2. Combat ID
• To maximize combat effectiveness through enhanced
  battlespace awareness, material CID solutions
  must be interoperable with and have the
  capability to feed directly into command and
  control systems.
• 3. Blue Force Precision Location Information
• Inability to effectively ID friendly troops on
  the ground in dynamic maneuver situations will
  give away many of the tempo related gains of
  JV2010, or will result in fratricide.
• 4. Coalition Warfare Interoperability
• Numerous issues (security, encryption, etc.)
  impede our ability to work effectively with our
  coalition partners, impacting our ability to
  provide shared early warning and tactical
  information.
• 5. Joint Composite Tracking Network (JCTN)
• Establishing a JCTN will enable the track base
  stabilization that is currently missing in the
  JDN, which in turn will improve situational
  awareness and AADC response times.

Source US Joint Forces Command
6
Top 10 Interoperability Issues (contd)

• 6. Joint Collaborative Planning Tools
• Lack of a standardized computer based planning
  tool frustrates JFCs ability to plan
  efficiently. There are many collaboration tools
  in use in the DoD today (COMPASS, JIVA, ODYSSEY),
  none of which are interoperable.
• 7. Joint Air Planning/Execution Tools
• Interoperability problems exist between Area Air
  Defense Coordinator (AADC), Theater Battle
  Management Control Systems (TBMCS), and the Joint
  Targeting Toolkit (JTT).
• 8. US Army/Marine Corps Digitization Efforts
• Army Maneuver Control System (MCS) to USMC
  Tactical Combat Operations (TCO) Systems cant
  exchange digital position information.
• 9. DIICOE-DODIIS Interoperability
• The Defense Information Infrastructure-Common
  Operating Environment (DII COE) and DoD
  Intelligence Information System (DoDIIS) do not
  have adequate levels of interoperability.
• 10. Intelligence Systems Interoperability
• Stovepiped national and service systems are not
  interoperable and impede the exchange and access
  of information to tactical users.

7
Example - 5 Deadly SinsTheater Air Missile
Defense Mission Area
8
Interoperability - The Way Ahead

• Todays Systems
• Tactics/Techniques/Procedures to best use todays
  systems
• Technology/SW fixes to make todays systems more
  interoperable
• Future Systems
• Acquisition processes for new systems and
  upgrades focused on interoperability
  (requirements, standards, development, testing) -
  systems must be born joint

9
Example Joint Systems Engineering Approach--
Single Integrated Air Picture (SIAP) --

• Joint Requirements Oversight Council selected
• Navy as Systems Engineer
• Air Force as Deputy
• Army as Acquisition Executive

The SIAP is the product of fused, near-real-time
and real-time data from multiple sensors to allow
development of common, continuous, and
unambiguous tracks of all airborne objects in the
surveillance area.
10
Evolving Todays Systems - An Example

• Family of Interoperable Operational Pictures
• Evolve the Common Operating Picture (COP)
  Common Tactical Picture (CTP) to provide common,
  relative battlefield management information where
  when needed.

CINC JTF Component and below
Shared Meta Data
11
So, where does MS come in?

• There is a blurring of the lines between real
  systems and simulations
• Simulation is the only feasible way to develop
  test a system-of-systems
• MS 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

12
Top 4 Actions to Implement Simulation Based
Acquisition (SBA)

• Establish a concept of operations for use of
  Distributed Product Descriptions (DPDs)
  throughout the acquisition life cycle
• Establish and resource a process for populating
  and managing an online DoD/Industry repository
• Define, adopt, and develop relevant standard data
  interchange formats (DIFs) for the SBA
  architecture

• Implement appropriate collaborative environments

13
Joint Distributed Engineering Plant
What Geographically dispersed, networked system
engineering sites (systems, hardware, software,
people, simulation/stimulation). Why Address
system interoperability performance at
system-of-systems level in representative
environment. testing and system engineering
of Joint Integrated Air and Missile Defense,
focusing on combat systems, data links and C4I
systems which must be interoperable for effective
Joint Integrated Air Defense operations.
To fight jointly, we need to engineer jointly
14
JDEP Initial Resources
NAVY DEP
THEATER MISSILE DEFENSE SYSTEM EXERCISER
JITC JOINT TACTICAL DATA LINK LABORATORY
15
JDEP CONCEPT( Combat Systems/BMC4I Hardware in
the Loop)
Built upon Collaborative Engineering
Environment, and migrates from DIS to HLA
16
Exploiting HLA

• JDEP
• Use HLA federated systems represented by an array
  of sims, virtual prototypes, HWIL and actual
  combat systems to isolate and fix
  interoperability problems
• HLA Discipline
• Each system and data exchange capability
  documented, building in understanding and
  interoperability issue resolution
• Technical Decoupling separate data exchange
  from the medium, as opposed to tightly coupled
  data/formats/radios typically associated with
  todays systems.
• Link Weapon System Software with HLA
• Improving SW interoperability, pass only needed
  data.

17
Interoperability in Future Systems
REQUIREMENTS
AQUISITION

• Required Planning
• C4I Support Plan
• TE Master Plan

• INTEROPERABILITY
• Key Performance Parameter
• Based on
• Operational View
• Interoperability Exchange Requirements (IERs)

Required Validation All C4I systems, regardless
of ACAT,must be tested and certified. The
CJCS will validate all test certifications
against IERs...
Per CJCSI 3170, 6212
Systems born joint
Outcome based interoperability

• Results
• Validated Requirements
• System-of-Systems Development Test
• Certified System Interoperability

18
THAAD TOP LEVEL IER OPERATIONAL CONCEPT
VIEW/SYSTEM INTERFACE GRAPHIC
UNCLASSIFIED

• IBS
• RIVETJOINT
• UAVs
• JSTARS
• STRATEGIC SENSORS

ABL
AN/APY-2 USG-3
E3 AWACS
E2C HAWKEYE
DSP
AN/APS-145 USG-3
JOINT NETS
THAAD BM/C3I
MEADS
AN/MSQ-XXX AN/MPQ-XXX USG-3
AN/MSQ-XXX AN/MPQ-XXX USG-3
AEGIS
JTAGS
USMC TAOM
AN/SPY-1 USG-2
AN/TYQ-23 AN/TPS-59 MRRS USG-2
AN/TYS-1
CRC/AOC
AN/MSQ-104ECS AN/MSQ-116 ICC AN/MPQ-53 USG-3
AN/TSQ-XXX
AN/TYQ-23 AN/TPS-75 USG-3
UNCLASSIFIED
19
Extract of THAAD IER Matrix
Assembling the multiple system interfaces
required for interoperability, for development
and test, is a job for MS!
20
-- Interoperability -- What Better Resource Than
MS?

• Clearly, if we want to achieve 100 of
  warfighting capability -- we must develop, test,
  operate and sustain fully interoperable weapons
  systems.
• Requirements Analysis
• System Design Test
• Legacy System Fix
• Certification
• Training Exercises
• Contingency Planning
• Operations

Function
Essential Tools
MS SBA Collaborative Eng Env JDEP HLA