System Engineering

Applied to the
Single Integrated Air Picture (SIAP)
Presentation to National Defense Industrial Association

25 October 2000

Robert L. Hobart
Branch Head, System Engineering
Office:CM3/1109 (703) 602-6441 x 207
HobartRL@navsea.navy.mil
JTAMDO: The SIAP vision 2010

2 Known Friendly Fused Radar & Sensor Data

2 Known Hostile
2 Known Cruise Missile
Automatic Correlation
Combined ID Information

2 Known Friendly
2 Known Hostile
2 Known Cruise Missile 2 Known Friendly
2 Known Friendly 2 Known Hostile
2 Known Hostile 2 Known Cruise Missile
2 Known Cruise Missile

2
Complete, Common, Accurate Air Picture & ID 25 OCT 2000
 What the warfighter sees...

• Erratic tracking
• Dual/multiple track
∧ Sensor designations
∩ • Misidentification/Track ID
conflicts
Link 16 • IFF/SIF conflicts
JTAOM
• Reporting responsibility (R2)
SAAWF B B = TADIL B
a = ATDL-1
conflicts
TAOC
a
G = GBDL • Frequent track number
RTU changes and swaps
G • Reliance on voice
∩ deconfliction
∧
• Operator overload
3
Shooter 25 OCT 2000
Problem statement
System A’s View of World
303
306 3055N

01227
02547 2 observed only
1 real aircraft
Not observed 3045N
8025W 8010W 7955W 7940W

System B’s View of the World

306
1227 3055N

2547

303 Looks like a friendly, but its not 3045N

8025W 8010W 7955W 7940W

4
The Facts: Everyone’s NOT on the same sheet of music 25 OCT 2000
SIAP System Engineering Task Force
Charter

• Initial focus of SIAP SE TF is to

– Establish a disciplined system engineering process to
develop and integrate SIAP recommendations

– Develop recommendations for near-term Joint Data Network

(JDN) improvements on the path to a SIAP capability
• Measurable Product: “JDN” Fixes

– Lead development of the system and technical views for the

SIAP component of the TAMD integrated architecture
• Measurable Product: System and Technical Views

5
25 OCT 2000
 The Construct

Joint
Warfighting Capability
Improvements

Documented
in the Process “JDN Tools
Detailed &
Implementation Tune-ups Fixes”
Plan SV

Staffing Funding Infrastructure

Charter MOA
6
25 OCT 2000
System Engineering Process
PROCESS
INPUTS Requirement
and constraint
conflicts
Requirements
Analysis
Requirement
Requirements baseline trade-offs and
impacts Requirements trade
studies and
Requirements assessments
Verification
Decomposition and
Validated requirements baseline requirement allocation
alternatives System
Functional
Analysis
Decomposition/allocation
Functional architecture trade-offs and impacts
Functional trade
studies and
Functional assessments
Verification
Design solution
Verified functional architecture requirements and
alternatives Analysis

Synthesis
Design solution
Physical architecture trade-offs and
impacts Design trade
studies and
Design assessments
Verification

Verified physical architecture

Control

PROCESS OUTPUTS

Ref: IEEE 1220

7
25 OCT 2000
The Technical Challenge

AWACS E-2C Patriot TAOC AEGIS TBS

Common Time Reference
Navigation
Data Registration Critical
Correlation/De-correlation Functions
Combat Identification
TBD

Attacking the problem functionally:

- At a place/scope we can afford;
- That culminates fidelity WRT time 8
25 OCT 2000
 Collaborative Engineering Environment
(CEE)
Design Synthesis and Real-Time Simulations
Analysis Tools

Publish and Subscribe to

Non-persistent, real-time
Access Persistent Simulation Data
Design Data
for Sim Initialization
Create & Access System Info
Persistent Repository M&S Run-time
Design Data Infrastructure
Provide
Simulation
Results

Persistent Data Infrastructure Non-persistent Data Infrastructure

SE tools focus on reuse and interoperability of persistent design type data
M&S Tools focus on real-time publish/subscribe of sim messages like entity state
9
25 OCT 2000
Collaborative Engineering Environment
• Purpose: Define use cases, management approach, operations
and support requirements, stakeholder roles.
• Integration and Interoperability Collaboration Capability -
Supports collaboration across distributed users for file and
document sharing; access to relevant data base repositories;
data, voice and video conferencing.
• Collaborative Engineering Environment (CEE) - Supports
collaboration across distributed users for engineering and
management data at the object level. Will initially be
implemented using commercial tools and object repository as
well as existing simulations and data bases.
• Interoperability Tools – Identify, assess, and deploy selected
complex systems Interoperability assessment and simulation
tools.

10
25 OCT 2000
 Networking Together
Supporting the Warfighter

DEP

NCW
RDT&E JDEP

Training Smart
Sensor
MBC Web
ECCN CHENG
CEE
- Common National Commercial
Tools ATM Networks
Applications DREN SDREN
& Protocols DISN-LES SIPRNET
Near-term approach

• Objectively examine JDN-related processes whose

health is essential to the warfighting mission
– Example: JINTACCS
– Identify ways of improving those processes
• Support “triage” efforts to make what we have all it
can be within limited resources available
• Build, validate and implement a roadmap
– Develop detailed cost estimates
– Trade costs against warfighting benefits
– Allocate resources to fix those problems that yield greatest
“bang for the buck”
– Verify and validate “fixes” using the JDEP

12
25 OCT 2000
 JDEP concept
TAOM MCE
AWACS
AWACS Boeing
Boeing
Boeing JNTF
AEGIS B/L 1-5
Colorado Springs Langley AFB CUBE
Camp AWACS
AWACS
Pendleton Tinker
Tinker AFB
AFB
AFB ATRC Dahlgren
TACCSF
WOC Hanscomb AFB
TPS-59

TPS-75 Boeing
LM Hanscom

LM Syracuse, NY AFB
Seattle
Offut AFB
CECOM/DIL
Ft Monmouth

Syracuse JNTF
Colorado
Springs
Boeing
NRL, MD
NAWC Pax
River, MD
Kirtland AFB
Edwards AFB St. Louis, MO ACSC
NSWC

Eglin AFB NAWC

China Lake
Dahlgren

Redstone
Wallops

Langley
SHORAD
Tinker
AFB
NAWC
Pt. Mugu
Aerojet
Azusa, CA
AFB Arsenal
Huntsville, AL
JBC/JTASC
Suffolk, VA Huntsville, AL
Camp
Pendleton
Kirtland
NSWC-PHD
Dam Neck, VA
JLENS
AFB Eglin AFB

THAAD SSC/ICSTF/
NCTSI
SSC-C
Charleston

C4ISR San Diego

JITC
Fort
Huachuca
Fort
Bliss
El Paso
Raytheon
Greenville, TX
Northrop
Grumman
Melbourne, FL
AEGIS B/L 1-5
Hurlburt AFB

RC-135V
Redstone,
RC-135V JSTARS
SSC-Chasn Arsenal Greenville, TX
Offut AFB Huntsville, AL
JTAGS
JTAGS
Melbourne, FL ACC Dahlgren
JTAGS
JTAGS
F-14D
JITC
JTAGS
JTAGS
JTAGS
JTAGS PATRIOT CV/LHD/DD/FF
Pt Mugu G
Huntsville,
Huntsville,AL
AL Fort Huachucha
Azusa,
Azusa, CA
Azusa,CA
Azusa, CA
CA DIL
PATRIOT E-2C Redstone, Arsenal
Dam Neck, VA
NAWC-AD Ft Monmouth AEGIS B/L 1-5
CV/LHD/DD
Fort Bliss F-15/16
ICSTF San Diego
Edwards AFB ACSC Wallops IS
 JDN Fixes: The Process
SIAP SE SYSCOMs/PEOs/PMs
Service AE
fix

JFCOM inputs Gather Data/

SIAP AE
plus other inputs Conduct Analysis Industry
(e.g. ASCIET, Kosovo Ops) Involvement
JROC
Characterize Problems approval
Patriot Industry
E-2C ABMOC Involvement
Problem and
Root Cause
AWACS TAOC SIAP AE
Operational
Impact
CRC RJ
AEGIS

Identify Prioritize Integration

Forward non- Identify Candidate into the
to materiel Workarounds
Solutions JTAMD
JTAMDO solution
candidates
(JFCOM) process
Develop
Candidate Services/
Materiel SYSCOMs/PEOs/PMs
Solutions Assess costs and
programmatic impact
Industry
Involvement
14
25 OCT 2000
Joint Vision 2010 Pillars

15
25 OCT 2000
SV and TV for the SIAP component of the
TADM Integrated Architecture

• Clinger-Cohen Act requires architecture

• Using C4ISR Framework Document 2.0 as guide
– TAMD OA being generated by JTAMDO
– BMDO generating SV and TV for TAMD Integrated
Architecture (IA)
– SIAP SE TF responsible for SIAP component of TAMD IA
• BMDO and SIAP SE TF have agreed on the following
commercially available tools:
– System Architecture 2001
– Bonapart
– Rationale Rose Suite

16
25 OCT 2000
Controls

• Pressure points -- find and correct problems as early

in the process as possible
– Standards generation and configuration control process
– Allocation of resources for time-phased, synchronized
implementation of changes and fixes to existing shortfalls
– Use configuration status accounting to understand
configurations and operational impacts of configuration
differences
– Assess capability objectively and make fielding decisions
based on that assessment

17
25 OCT 2000
Summary
• Establish collaborative system engineering process
• Ensures early Service participation for creating a Joint
solution
• Lowers life cycle costs by reducing rework to resolve
interoperability problems in fielded systems

• Develop recommendations for near-term Joint Data

Network (JDN) improvements
• Lead development of the system and technical views for
the SIAP component of the TAMD integrated
architecture

“The product of the SIAP SE recommendations will be combat ready,

operationally certified equipment and computer programs that
enable the warfighter to build and maintain a SIAP.” 18
25 OCT 2000
?s
BACK UP SLIDES
Single Integrated Air Picture (SIAP) definition

• “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.”*
– All airborne objects must be detected, tracked, and reported
– Each object must have one and only one track identifier and
associated characteristics
– Scaleable and filterable
– Incorporate the products of the combat identification process
– Derived from NRT and RT data (including fire-control quality
data), provided by JDN and JCTN
– For RT data, the delay time must be no more than 0.5 sec
*Capstone Requirements Document (CRD) for Theater Missile Defense dtd Jul 98 21
25 OCT 2000
 SIAP potential improvements
Sensor

Joint
JointData
DataNetwork
Network
Standardizedacross
Standardized Acrossall
All Systems
Systems Results
Results in in
Satellite Communications !• All
All platforms
platforms having
having common
common
to Extend the Range of and correlated
and correlated track
trackpicture,
picture,
To Other theater Missile thereby reducing track
thereby reducing track
the Joint data Network
Defenses Farther Away confusion, conserving
confusion, conservingresources,
resources,
JSEWG and permitting wider deployment of resources
! and permitting
Higher widerhave
headquarters deployment of resources
same information
• Higher headquarters have same information

Connectivity SET Nav

Computer Tools
Time
to Manage the Corr/Decorr
Joint data CID
Network
Display
More Efficient
Use of the
Capacity of the
Joint Data Network
• !Dynamically
Dynamicallyresponds
responds
totochanging
changingoperations
operations

! Improved coordination
• Improved coordination based
based on
on
intent to
to fire
fire thereby
therebyconserving
Intend
resources
resourcesover
conserving
overprotected
protectedbattle
battle
IFC
SET Contribution
22
With proper investments, tomorrow’s situation meets the warfighter’s needs
25 OCT 2000
SIAP Activities Status

• SIAP “New Start”

– New Start package approved by HAC and SASC
– Further Congressional briefs being scheduled
– Funding delays have slowed progress
• SIAP Charter
– Signed by CIO and VCJCS and on track for
USD (AT&L) approval and DEPSECDEF endorsement
– Produced in coordination with the Services, JTAMDO and
BMDO

23
25 OCT 2000
 Engineering Issues Decision Process

Issue scope
Assign to No
Issue beyond beyond
Lead SET Lead SET?

Yes

Engage
other
SETS

Develop
alternative
solutions and
impacts
No

Implement; Approve Alternatives’ Recommend

Advise SIAP SE scope solution
sufficient

Unresolved

Adjudication 24
Process 25 OCT 2000