30
Open Architecture Acquisition Way Ahead
Slide
20
10/27/2005
Configuration
TENTACLE ICMS BL 1.0
Engagement Schedule
RV Action Schedule
Engineering Schedule
Weapon Action
RV Action
Engineering Action
Mission
Assessment
Threat
Assessment
(including
identity)
Assigned
Missions
Action Plans
Plan
C2 Order, Schedule & Event
Tactical
Picture
5.0 Mission Exec.
1.0 Search & Detect
Multi
-
Sensor Correlated
Track
2.0 Data/Information
Services (DIS)
System Track
Composite/Collaborative Track
INTEL
-
Generated Track
Track Repository
1
1
3
3
6
6
2
2
8
8
9.0 Force Planning/Coordination (FP/C)
Joint BF
Orders
Commanders
Estimate
Course Of
Action
BF
Orders
6
6
3.0 Planning, Assessment &
Decision (PAD)
2
2
4
4
6
6
8
8
2
2
3
3
5
5
6
6
4.0 Weapon/Asset
Services  (W/AS)
2
2
3
3
4
4
9
9
ALL
7.0 Common Services
(CS)
Display
Time
NAV
DX/DR
Databases
Environment
3
3
8.0 Training
(TR)
Training
Action Plan
Training
Schedule
Training
Event
Scenario
Simulator
Stimulator
6
6
4
4
8
8
Data Links
SatCom
DDS
Radios
6.0 EXCOMM
Comms
Service Action
Network Schedule
Message Event
2
2
1
1
9
9
3
4
4
6
6
6
6
8
8
5
5
Sensor
Control
Radar Sensor Suite
IFF
Dual Band Radar
Acoustic Sensor Suite
LMRS
Sensor System
Towed Array
Sensor System
Bow  Array
Sensor System
Acoustic Intercept
Sensor (AIS)
ES/Intel Suite
ES
Component
EO/IR Suite
FLIR/LRF
Imagery
Integrated
Bridge
Damage D&A
Engineering Control
TLAM, LASM
ASROC (VLA)
ESSM,  SM
-
2 MR
LRLAP
40 MM
NULKA,Giant,Chaff
Towed Torpedo
Countermeasures
VTUAV
MH
-
60R
Missile Control
LAM Missile
Control
CIGS Control
Torpedo 
Wpn
Control
AGS Control
Decoy Control
VTUAV Vehicle
Control
Helicopter
Control
Engagement Schedule
RV Action Schedule
Engineering Schedule
Weapon Action
RV Action
Engineering Action
Engagement Schedule
RV Action Schedule
Engineering Schedule
Weapon Action
RV Action
Engineering Action
Mission
Assessment
Threat
Assessment
(including
identity)
Assigned
Missions
Action Plans
Plan
C2 Order, Schedule & Event
Tactical
Picture
Mission
Assessment
Threat
Assessment
(including
identity)
Assigned
Missions
Action Plans
Plan
C2 Order, Schedule & Event
Tactical
Picture
5.0 Mission Exec.
1.0 Search & Detect
Multi
-
Sensor Correlated
Track
2.0 Data/Information
Services (DIS)
System Track
Composite/Collaborative Track
INTEL
-
Generated Track
Track Repository
Multi
-
Sensor Correlated
Track
2.0 Data/Information
Services (DIS)
System Track
Composite/Collaborative Track
INTEL
-
Generated Track
Track Repository
1
1
1
1
3
3
3
3
6
6
6
6
2
2
2
2
8
8
8
8
9.0 Force Planning/Coordination (FP/C)
Joint BF
Orders
Commanders
Estimate
Course Of
Action
BF
Orders
6
6
6
6
3.0 Planning, Assessment &
Decision (PAD)
2
2
4
4
6
6
8
8
2
2
3
3
5
5
6
6
4.0 Weapon/Asset
Services  (W/AS)
2
2
3
3
4
4
9
9
ALL
7.0 Common Services
(CS)
Display
Time
NAV
DX/DR
Databases
Environment
3
3
3
3
8.0 Training
(TR)
Training
Action Plan
Training
Schedule
Training
Event
Scenario
Simulator
Stimulator
6
6
4
4
4
4
8
8
8
8
Data Links
SatCom
DDS
Radios
6.0 EXCOMM
Comms
Service Action
Network Schedule
Message Event
2
2
1
1
9
9
3
4
4
6
6
6
6
8
8
5
5
5
5
Sensor
Control
Radar Sensor Suite
IFF
Dual Band Radar
Radar Sensor Suite
IFF
Dual Band Radar
Acoustic Sensor Suite
LMRS
Sensor System
Towed Array
Sensor System
Bow  Array
Sensor System
Acoustic Intercept
Sensor (AIS)
Acoustic Sensor Suite
LMRS
Sensor System
Bow  Array
Sensor System
Acoustic Intercept
Sensor (AIS)
ES/Intel Suite
ES
Component
ES/Intel Suite
ES
Component
EO/IR Suite
FLIR/LRF
EO/IR Suite
TISS.IRST
Imagery
Integrated
Bridge
Damage D&A
Engineering Control
 
ASROC (VLA)
       ESSM - ASM
-
LRLAP
Millenium Gun
NULKA,Giant,Chaff
VTUAV
MH
-
60R
Missile Control
 
Control
CIGS Control
Torpedo 
Wpn
Control
AGS Control
Decoy Control
VTUAV Vehicle
Control
Helicopter
Control
ICMS Open Architecture Design
The ICMS design philosophy is inline with the Navy’s open architecture focus!!!

This design philosophy, from our perspective, is also an extension of the Boyd cycle view of combat systems shown on the previous slide,
In that our goal was to focus on fitting our architecture with our intended functionality,
rather than force fitting architecture according to component selection.

We keep in mind the related goal of avoiding “stovepiped” designs that tend to be either mission, platform, or proprietor unique.