Open Architecture as an Enabler for FORCEnet

Open Architecture as an Enabler for

FORCEnetPresented by:Tom Hedge

NSWC PHD San Diego25 October 2006

25 October 2006 2

Project Team

• Viviane Deering• Patrick Grates• Tom Hedge• Sein Kung

• Maria Martinez• Percival Mcarthy• Kevin Pugh• Sasha Radojkovic

Advisor - John M. Green, NPS

NSWC PHD Project Team

25 October 2006 3

Agenda

• Objectives• Methodology• Definitions and Models• Battle Space• Engagement Scenarios• Design Principles• Conceptual Design / Architecture• Simulation Model• Conclusions / Recommendations• The Road From Here

25 October 2006 4

Objectives

Project Objective:Evaluate and assess NAVSEA PEO IWS FORCEnet Open Architecture (OA) functional architecture against three (3) air defense engagement scenarios to either validate the model or identify recommended alternatives and / or improvements.

Presentation Objective:Provide overview of project research methodology, including

descriptions of models and architectural frameworks used to bound research, and present recommended model

improvements.

25 October 2006 5

Methodology

• Characterize the Problem / Battle Space – identify operational environment, including actual engagement scenarios, to bound problem space

• Formulate Design Principles – consider operational environment & available FORCEnet / OA models and strategies in formulating principles for architecting OA system with Integrated Fire Control (IFC) capabilities

• Develop Conceptual Design – develop architectural framework for distributed system with automated decision aids for optimally managing warfare resources within the problem space

• Functional Decomposition – develop models and methods to express automated resource collaboration in the context of the FORCEnet/OA architecture domain

• Simulation Modeling – develop computer simulation model to assess proposed functional system architecture against the engagement scenarios

• Analyze Simulation Results – Assess results of simulation to determine validity of previously identified FORCEnet OA model

25 October 2006 6

Definitions

• FORCEnet: operational construct and architectural framework for naval warfare in the information age, integrating warriors, sensors, command and control, platforms, and weapons into a networked, distributed, combat force

• Open Architecture: – Technical and Functional Architectural– Interfaces at system boundaries must be described in detail using

established commercial or DoD standards – Well-defined and easily understandable system boundaries at various

levels– Subsystem descriptions and interface definitions capable of two or

more layers of decomposition using established system engineering practices

– Foundation for 21st Century Combat System Designs

25 October 2006 7

Definitions (cont’d)

• Time-Critical Targeting: ability to detect, track, engage, and assess threats having extremely limited windows of vulnerability or opportunity for detection

• Integrated Fire Control: ability of a weapon system to develop fire control solutions from information provided by one or more non-organic sensor sources, conduct engagements based on these solutions, and either provide mid-course guidance or allow this guidance to be provided by another warfare unit

25 October 2006 8

FORCEnet Information Architecture

Source: FORCEnet Implementation Strategy, National Research Council, 2006

Invariant architectural boundaries with network control system “throttles” to assure the metrics

Networks

Fire-Control Networks*(deterministic latencies)

Collaborative Command-and-Control Networks*(high security)

Collaborative Sensor / Intelligence Networks*(high volume)

Integrated Data

Integrated Displays

(Human-machine-interface)

Kill chains* Networks trace to communities of interest

Legend:

25 October 2006 9

OA Warfare System Domain

MeasurementReport

MeasurementReport

INTEL ReportINTEL Report

Sensor TrackReport

Sensor TrackReport

Sensor ReportSensor Report

Sensor AssetSensor Asset

Eng Control SysEng Control SysEngineeringEngineeringEngineering

DamageDamageDamageBridgeBridgeBridge

RV AssetsRV AssetsAircraftAircraft

Un-Manned VehicleUn-Manned Vehicle

Weapons SystemWeapons SystemAir / Surface MissileAir / Surface MissileAir / Surface Missile

Land Attack MissileLand Attack MissileLand Attack MissileTorpedoTorpedoTorpedo

DecoyDecoyDecoyGunGunGun

BoatBoat

Sensor SchedulerSensor SchedulerNRT INTEL TrackNRT INTEL TrackTrack RepositoryTrack Repository

Attribute DataAttribute DataTrack KinematicsTrack Kinematics

ClassificationClassificationSupporting Source TrackSupporting Source Track

System TrackSystem Track

AssignedMissions

AssignedMissions

ActionPlans

ActionPlans

PlanPlan

MissionAssessment

MissionAssessment

C2 Order, Schedule & EventC2 Order, Schedule & Event

TacticalPicture

TacticalPicture

CapabilityCapability

ThreatAssessment

(Including Identity)

ThreatAssessment

(Including Identity)

Action: Weapon, RV,NAV & Engineering

Action: Weapon, RV,NAV & Engineering

Schedule: Weapon,RV & Engineering

Schedule: Weapon,RV & Engineering

Event: Weapon, RV,NAV & Engineering

Event: Weapon, RV,NAV & Engineering

5.0 Mission 5.0 Mission Execution (ME)Execution (ME)

1.0 Search / 1.0 Search / Detect (S / D)Detect (S / D)

2.0 Data / Information Services (DIS)2.0 Data / Information Services (DIS)

3.0 Planning, Assessment & Decision (PAD)3.0 Planning, Assessment & Decision (PAD)

4.0 Weapon / Asset Services (W / AS)4.0 Weapon / Asset Services (W / AS)

11 22 88 22 11 33 66 33 22 44 66 88 44 22 33 55 66 55 44 88

66 22 33 44

CommunicationsService Action

CommunicationsService Action

NetworkScheduleNetworkSchedule

MessageEvent

MessageEvent

NetworkNetwork

Data LinksData Links

6.0 EXCOMM6.0 EXCOMM

RadiosRadios

SatComSatCom

DisplayDisplay

NAVNAV

TimeTime

DX / DRDX / DR

DatabasesDatabases EnvironmentEnvironment

SyntheticActions

SyntheticActions

SyntheticEntities

SyntheticEntities

SimulatorSimulator ScenarioScenarioSimulatorSimulator

TrainingAction,

Schedule& Event

TrainingAction,

Schedule& Event

7.0 Common Services (CS)7.0 Common Services (CS) 8.0 Training (TR)8.0 Training (TR)88 33 66

Joint BFOrders

Joint BFOrders

CommandersEstimate

CommandersEstimate

COARepository

COARepository

BGOrders

BGOrders

ForceIntegratedScheduler

ForceIntegratedScheduler

ALLALL

66 99

99 669.0 Force Planning / Coordination (FP / C)9.0 Force Planning / Coordination (FP / C) Candidate OA Common Function/Application

Candidate OA Platform-Unique Function / Application

Force Network

Local Network (OACE)

Provided Data

Consumed Data

OA Warfare System DomainOA Warfare System Domain

Source: Combat Identification for Naval Systems in an Open Architecture,Young, 2006

25 October 2006 10

OA Compliance Categories

Source: OACE Technologies and Standards, NSWC, Dahlgren Division, 4 Sep 2003

25 October 2006 11

Legacy Models Considered

Command and Control Force Virtual Sensor

Force Weapons EW and Hard-Kill

LEVEL 0 Signal Detection

Feature Extraction

Level 1

Track Kinematics

& ID

Level 2

Situational Awareness:

Context, CTP

Level 3

Force Threat Evaluation (TEWA) Planning,

Estimating

LEVEL 4 Force Weapons

Assignment (TEWA) Resource Management

Mission Assessment

C2/Information "Net" [e.g., JPN (Non-Real Time), JDN (Near Real Time), CEC/JCTN (Real Time)]

Force Level: * IERs * Info Exchange Effectiveness (IEE)

Kinematics * Position * Velocity ID

Sensor Coordination "Net"(e.g., CEC/JCTN) Unit/Force

Level: Decision Reaction Time

Unit/Force Level: Engagement Decision Effectiveness

Weapons Coordination "Net"

Sensor (Detection)

GridInformation Grid

(e.g., GIG) Force Information

Exchange

Shooter (Engagement)

Grid

LEVEL 1

ObjectAssessment

LEVEL 2

SituationAssessment

LEVEL 3

ImpactAssessment

LEVEL 0

Sub-ObjectAssessment

LEVEL 4

ProcessRefinement(ResourceManage-

ment)

Mea

sure

men

ts

Sign

als/

Feat

ures

Obj

ects

Situ

atio

ns

Situations

Situ

atio

ns/P

lans

Situations/Plans

Plans

Situ

atio

ns

Obj

ects

Sign

als/

Feat

ures

Resources

CONTROLCONTROLDETECT

DCE Sequence

Data Fusion Model

ENGAGE

OBSERVE

OODA Loop

ORIENT DECIDE ACT

Source: A Self-Consistent Context for Unit and Force Level Tactical Decision-Making, Luessen, 2003

25 October 2006 12

Integrated Fire Control

• Fundamental IFC System Characteristics– Dynamically updateable doctrine– Decentralized architecture and synchronized information– Doctrine and decision aids

• Key IFC Capability Requirements– Shared Situational Awareness (SA)– Determining best Course of Action (COA)– Distributed Resource Management (DRM)– Embedded IFC planning

Source: Integrated Fire Control for Future Aerospace Warfare, Young, 2004

25 October 2006 13

Common Identification (ID)

• Objective: accurate, timely, and sustainable characterization and classification of tracks to facilitate early threat and resource awareness, and enable optimal weapon engagement planning

• Current methods: Identification Friend or Foe (IFF), Local sensor data Intelligence, Surveillance, and Reconnaissance (ISR)

• Future Capability Requirements– Centralized geographical database– Shared resource picture– Common CID deterministic results– Common CID functionality– Support Joint Warfare operating environment– Effective CID data strategy– Span Warfare areas– Increased level of automation– Isolate CID processes (OA design)

Source: Combat Identification for Naval Systems in and Open Architecture, Young, 2006

25 October 2006 14

Future Common ID Capability

Source: Future CID Capability, Young, 2006

CID Fusion Engine

- Associate/fuse CID data from various sources per battlespace object- Analyze CID data to make CID determinations- Synchronize CID determinations with those made by other units

Enemy Information (from Intel sources)

Predicted Signatures,Threat Templates,A Priorit Knowledge ofEnemy Locations &CapabilitiesResource

“Picture”

Friendly Force &

Defended Asset “Picture”

Location & Status of Friendly Force Resources

Location & Status of Friendly Force & Defended Assets

IFF ID Data CID-Related Sensor

Data & Track Data

Track Manager System

On-Board & Off-Board Sensors

Sensor Data

Location & Status of Friendly Force Units & Defended Assets via Comm Links, Internet, or Phone

IFF

Other Military & Civilian Units

Radio Transmission Response (contains ID)

Other Military & Civilian Units

Phenomenological Emissions

Battlespace ObjectsActive

Sensor Emissions

Off-Board CID Fusion Engine

CID Result Synchronization (Discrepancy Identification & Resolution

Location & Status of Friendly Force Resources via Comm Links

Other Military Units

Radio Transmission Interrogation

25 October 2006 15

Battle Space Information Realms

CTPCommon Tactical

Picture

COPCommon Operational

Picture

COP ~ Non-Real Time (minutes)- Supports Planning/Force Mgt:

- Deployment- Movement

- Consists of: tactical info, courses ofaction, enemy order of battle info

CTP ~ Near-Real Time (seconds)- Supports Cueing/Force Mgt:

- Maneuver- Asset Control

- Weapon/Sensor Cueing- Target Weapon Pairing

- Consists of: tactical information

FCP ~ Real Time (sub-seconds)- Supports Fire Control:

- Launch & In-Flight Fire Support- Engage on Remote

- Consists of: fire control quality measurements with single threat focus

7616

5230

1177

1162

1156

0000

11627612

1177

FCPFire Control

Picture

The FORCEnet OA operational concept will enable ideal threat/weapon pairings by maintaining BF-wide shared situational awareness across the three information realms

The FORCEnet OA operational concept will enable ideal threat/weapon pairings by maintaining BF-wide shared situational awareness across the three information realms

Source: Naval Network-Centric Sensor Resource Management, Worth/Green, 2006

25 October 2006 16

Engage on Remote

ThreatLauncher

Remote Unit

Firing Unit

Threat Illumination (Semi-Active Missile)

InboundThreat

Radar Track

FCQ Data

Radar Track

Active Missile

Engage on RemoteOV-1

1) Remote unit provides fire control quality threat data

2) Firing unit launches interceptor based on remote threat data

3) Remote unit continues to control engagement (compute and provide interceptor guidance, etc.) based on remote data

25 October 2006 17

Forward Pass

ThreatLauncher

Remote Unit

Firing Unit

Threat Illumination (S

emi-Activ

e Miss

ile)

InboundThreat

Radar Track

Eng

Stat

us /

Cont

rol In

fo

Forward PassOV-1

1) Firing ship launches interceptor based on local threat data

2) Remote unit takes over engagement control (compute and provide interceptor guidance, etc.) based on remote data

Radar Track

25 October 2006 18

Remote Fire

ThreatLauncher

Remote Unit

Firing Unit

Threat Illumination (Semi-Active Missile)

InboundThreat

Radar Track

Firing Order

Radar Track

Active Missile

Remote FireOV-1

1) Both ships maintain fire control quality threat data

2) Remote unit provides launch data and firing order to firing unit

3) Firing unit launches interceptor4) Either remote or firing unit can control

engagement (compute and provide interceptor guidance, etc.) as required

Radar TrackRadar Track

25 October 2006 19

Engage on Remote FFBD

Relay FireControl Solution

InitializeSystem

DetectThreat

CoordinateAssets

ScheduleSensor/Weapon

Relay FiringCommandInformation

FireWeapon

ManageInventory

Relay Engagement

Evaluation Info

Relay Inventory

Info

Evaluate Engagement

SupportEngagement

DetermineFC

Solution

Monitor/Report All

Data

RelayThreat

Info

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

1.0 2.0 3.0 6.0 7.0 8.0 9.0 10.0

13.0 12.0 11.0

14.0

15.0

5.0

4.0


InitializeSystem

DetectThreat

CoordinateAssets



FireWeapon

ManageInventory

Relay Engagement

Evaluation Info

Relay Inventory

Info

Evaluate Engagement

SupportEngagement

DetermineFC

Solution

Monitor/Report All

Data

RelayThreat

Info

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

1.0 2.0 3.0 6.0 7.0 8.0 9.0 10.0

13.0 12.0 11.0

14.0

15.0

5.0

4.0

25 October 2006 20

Forward Pass FFBD

InitializeSystem

DetectThreat

RelayThreat

Info

CoordinateAssets



FireWeapon

ManageInventory

Relay Engagement

Evaluation Info

Relay Inventory

Info

Evaluate Engagement

SupportEngagement


DetermineFC

Solution

Monitor/Report All

Data

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

1.0 2.0 3.0 6.0 7.0 8.0 9.0 10.0

13.0 12.0 11.0

14.0

15.0

5.0

4.0

InitializeSystem

DetectThreat

RelayThreat

Info

CoordinateAssets



FireWeapon

ManageInventory

Relay Engagement

Evaluation Info

Relay Inventory

Info

Evaluate Engagement

SupportEngagement


DetermineFC

Solution

Monitor/Report All

Data

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

1.0 2.0 3.0 6.0 7.0 8.0 9.0 10.0

13.0 12.0 11.0

14.0

15.0

5.0

4.0

25 October 2006 21

Remote Fire FFBD

InitializeSystem

DetectThreat

RelayThreat

Info

CoordinateAssets



FireWeapon

ManageInventory

Relay Engagement

Evaluation Info

Relay Inventory

Info

Evaluate Engagement

SupportEngagement


DetermineFC

Solution

Monitor/Report All

Data

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

1.0 2.0 3.0

5.0

4.0 6.0 7.0 8.0 9.0 10.0

13.0 12.0 11.0

14.0

15.0

InitializeSystem

DetectThreat

RelayThreat

Info

CoordinateAssets



FireWeapon

ManageInventory

Relay Engagement

Evaluation Info

Relay Inventory

Info

Evaluate Engagement

SupportEngagement


DetermineFC

Solution

Monitor/Report All

Data

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

NOT UTILIZED

ALL UNITS

FIRING UNIT

REMOTE UNIT

1.0 2.0 3.0

5.0

4.0 6.0 7.0 8.0 9.0 10.0

13.0 12.0 11.0

14.0

15.0

25 October 2006 22

Representative Sub-Function FFBDs

ID ThreatSelect

Preferred Sensor

EstablishTrack

VerifyThreat

and Intel

UpdateNetwork

DetermineEngagement

Solution

2.1 2.2 2.3 2.4 2.5 2.6

ID ThreatSelect

Preferred Sensor

EstablishTrack

VerifyThreat

and Intel

UpdateNetwork

DetermineEngagement

Solution

2.1 2.2 2.3 2.4 2.5 2.6

CompileData_1

TransmitData_1

VerifyTransmission_1

3.1 3.2 3.3

CompileData_1

TransmitData_1


3.1 3.2 3.3

Request G1Data

Gather G1 Data

ApplyEngagement

Doctrine

FormulateSolution

4.1 4.2 4.3 4.4

Request G1Data

Gather G1 Data

ApplyEngagement

Doctrine

FormulateSolution

4.1 4.2 4.3 4.4

CompileData_2

TransmitData_2


5.1 5.2 5.3

CompileData_2

TransmitData_2


5.1 5.2 5.3

Gather G1Data_2

SelectWeapon

Type

Select Shipfor Sensor

Track

Select Shipfor Weapon

Use

Relay Info toSupporting

Ship

6.1 6.2 6.3 6.4 6.5

Gather G1Data_2

SelectWeapon

Type

Select Shipfor Sensor

Track

Select Shipfor Weapon

Use

Relay Info toSupporting

Ship

6.1 6.2 6.3 6.4 6.5

25 October 2006 23

Simulation Model

Will Engaging

Ship Evaluate

theEngageme

nt?

Will Engaging

Ship Evaluate

theEngageme

nt?

EvaluateEngagement

EvaluateEngagement Threat Kill?Threat Kill? Monitor and

Report All Data

Monitor andReport All

Data

End ThreatEngagementSupport

Engagement

SupportEngagement

Will SchedulingShip Fire Weapon?

Will SchedulingShip Fire Weapon?

Relay FiringCommand

Info

Relay FiringCommand

Info

Fire WeaponFire Weapon

ManageInventory

ManageInventory

RelayInventory

Info

RelayInventory

Info

Will FCS Ship

Coordinate Assets?

Will FCS Ship

Coordinate Assets?

Relay FCSInfo

Relay FCSInfo

CoordinateAssets

CoordinateAssets

ScheduleSensor andor Weapon

ScheduleSensor andor Weapon

Incoming ThreatDetecting

ShipDetermines

FCS?

Detecting Ship

Determines FCS?

Relay ThreatInfo

Relay ThreatInfo

Determine FCS

Determine FCS

Y

N

Y

N

Y

N

Y

N

Y

N

RelayEngagement

Data

RelayEngagement

Data

Detect Threat

Detect Threat

25 October 2006 24

Simulation Model Results

# of Incoming Threats

Threat Interval

(seconds)

% of Successful First-time

Engagements

WIP [Saturation]

(seconds)

Average Total Time (seconds)

Limiting Process #1

Limiting Process #1 Time

(seconds)

Limiting Process #2

Limiting Process #2 Time

(seconds)

1 60 90 0.5166 25.1135 "ID the Threat" 0.3694 "Establish a Track"

0.2561

1 60 100 0.4974 23.4344 "ID the Threat" 0.3551 "Establish a Track"

0.2648

1 30 90 1.2893 34.8877 "ID the Threat" 0.872"Determine an Engagement

Solution"0.5203

1 30 100 1.2033 32.1173 "ID the Threat" 0.8961"Establish a

Track" 0.4846

2 60 90 2.3242 63.4865"Transmit All

Data" 2.0821"Compile Inventory

Data"1.7562

2 60 100 2.2656 59.8616"Transmit All


Data"1.9017

2 30 90 5.8229 120.15"Transmit All


Data"3.0117

2 30 100 5.7013 111.14"Transmit All


Data"3.271

25 October 2006 25

Revised FORCEnet OA Model

PEO IWS OA Warfare System /

Functional Domain

Revised FORCEnet OA System /

Functional Domain

Detect

Search / Detect• Sensor Asset• Sensor Report• Sensor Track Report• INTEL Report• Measurement Report

Search / Detect• Sensor Asset• Sensor Report• Sensor Track Report• INTEL Report• Measurement Report

25 October 2006 26

Revised FORCEnet OA Model (cont’d)


Functional Domain


Functional Domain

Control

Data / Information Services• Sensor Track• Supporting Source Track• Classification• Track Kinematics• Attribute Data• Track Repository• NRT INTEL Track• Sensor Scheduler

Data / Information Services• Sensor Track• Supporting Source Track• Classification• Track Kinematics• Attribute Data• Track Repository• NRT INTEL Track

Planning, Assessment & Decision• Assign Missions• Tactical Picture• Action Plans• Capability• Plan• Mission Assessment• Threat Assessment• C2 Order, Schedule, & Event

Planning, Assessment & Decision• Sensor Scheduler• Assign Missions• Tactical Picture• Action Plans• Capability• Plan• Mission Assessment• Threat Assessment• C2 Order, Schedule, & Event• Schedule: Weapon, RV,

NAV & Engineering• Action: Weapon, RV, NAV

& Engineering

25 October 2006 27



Functional Domain


Functional Domain

Control

Weapon / Asset Services• Action: Weapon, RV, NAV &

Engineering• Schedule: Weapon, RV &

Engineering• Event: Weapon, RV, NAV, &

Engineering

{to Planning, Assessment & Decision}

{to EXCOMM}

25 October 2006 28



Functional Domain


Functional Domain

Engage

Mission Execution• Air / Surface Missile• Land Attack Missile• Torpedo• Gun• Decoy

RV Assets• Aircraft• Boat• Un-manned Vehicle

RV Assets• Engineering• Damage• Bridge

Mission Execution• Air / Surface Missile• Land Attack Missile• Torpedo• Gun• Decoy

RV Assets• Aircraft• Boat• Un-manned Vehicle

RV Assets• Engineering• Damage• Bridge

Kill Assessment

Midcourse Guidance

25 October 2006 29



Functional Domain


Functional Domain

Common Services• Display• NAV• Database• Time• DX / DR• Environment

Common Services• Display• NAV• Database• Time• DX / DR• Environment

EXCOMM• Communications Service

Action• Network Schedule• Message Event• Network• Radios• Data Links• SatComm

EXCOMM• Communications Service

Action• Network Schedule• Message Event• Network• Radios• Data Links• SatComm• BG /BF COA Orders• Event: Weapon, RV, NAV

& Engineering

25 October 2006 30

Revised FORCEnet OA Functional Model

21 4

4 3

2 44 5

2 33 2

3 24 6

3 53 4

42

6

5

6

6

5

45

4

1.0 Search and Detect (SD)• ID Threat• Select Preferred Sensor• Verify Threat and Intel

4.0 EXCOMM• Update Network (Threat Info)• Transmit Data (Threat)• Request G1 Data• Receive G1 Data• Transmit Data (FCS)• Receive G1 Data_2• Relay Info to Supporting Ship(s)• Contact Threat Tracking Ship• Contact Firing Ship• Transmit Data (Firing Command)• Compile Data (Inventory) • Transmit Data (Inventory)• Verify Transmission (Inventory)• Transmit Data (Engagement)• Transmit All Data• Verify Transmission (All Data)

6.0 Common Services (CS)• Compile Data (Threat Info)• Verify Transmission (Threat Info)• Compile Data (FCS Info)• Verify Transmission (FCS Info)• Compile Data (Firing Cmnd. Info)• Verify Trans. (Fir. Cmnd. Info)• Compile Data (Engagement Info)• Verify Trans. (Engagement Info)

5.0 Mission Execution (ME)

• Update Inventory of Firing Ship• Uplink Midcourse Guidance• Sched. Sensor for Term. Support• Validate Sensor Track Data• Perform Kill Assessment• Mark as Kill or Miss• Compile Engagement Eval. Data• Compile Inventory Data• Compile Asset Data• Assess Shared Data

• Prepare Weapon

3.0 Planning, Assessment, and Decision (PAD)

• Formulate Solution• Apply Engagement Doctrine• Determine Engagement Solution

• Select Ship for Weapon Use• Select Ship for Sensor Track• Select Weapon Type

2.0 Track Data (TD)• Establish Track

25 October 2006 31

Revised FORCEnet OA System Domain

21 4

4 32 4

4 5

2 33 2

3 24 6

3 53 4

42

6

5

6

6

5

45

4

1.0 Search and Detect (SD)

• Sensor Track Report • Sensor Report (Status)• Sensor Asset

• Measurement Report• INTEL Report

3.0 Planning, Assessment, and Decision (PAD)

• Plan• Assigned Missions• Sensor Scheduler

• Capability• Tactical Picture• C2 Order, Schedule, Event

• Schedule: Weap., RV, NAV Engin.

• Threat Assessment

2.0 Track Data (TD)

• Track Repository• Support Source Track• Ship Track (System Track)

• Attribute Data• Track Kinematics

4.0 EXCOMM• G1 Data• G2 Data• G3 Data• Data Links• Network• SATCOM• Radios• BG/BF/COA Orders

5.0 Mission Execution (ME)• Weapon Systems• RV Assets• Asset Reports• Mission Evaluation• Midcourse Guidance

6.0 Common Services (CS)• Display• Time• Navigation• Environment• Databases

25 October 2006 32

Conclusions / Recommendations

• Functional analysis of PEO IWS OA Functional Domain model resulted in revised FORCEnet OA model

• Simulation validated logical functional flow of revised FORCEnet OA model

• Simulation validated system timing of revised FORCEnet OA model

• Revised FORCEnet OA model and Simulation used for model validation merit further scrutiny and refinement

25 October 2006 33

Recommended Future Actions

• Incorporate real-world timing parameters of current/future combat systems

• Incorporate real-world threat characteristics and parameters into simulation model

• Use simulation model to determine threat “processing” time using

• Refine simulation model based on results from using real-world combat system and threat parameters

• Use refined simulation model to assess combat system network architectures for saturation nodes and choke points

• Assess simulation model against other likely engagement scenarios

• Continue to revise NAVSEA FORCEnet OA model for use in architecting future single ship and strike group systems and networks

Open Architecture as an Enabler for FORCEnet

Documents

Transcript of Open Architecture as an Enabler for FORCEnet