Expansion of Link 16 and Coalition Networking (EL16CN)

Kevin Coyne

NAVSEA Dam NeckCoynekp@navseadn.navy.mil

Tele + 1 757 492-7656

Mobile +1 757 672-1767

Fax +1 757 492-6522

Robin Talbot

CDSA Dam Neckrobin.talbot@navy.mil

Tele + 1 757-492-7500

Mobile +1 757-646-4369

Fax +1 757 492-6229

Steve May

SPAWAR SSCmays@spawar.navy.mil

Tele + 1 619-553-8002

Mobile +1 619 887-6736

Fax +1 619 553-9096

Dr. Darren J. Sutton

RAN Scientific AdvisorDarren.sutton@defence.gov.au

Tele +61 2 6265 5010

Mobile +61 (0) 411 257 096

Fax +61 2 6265 6628

Presented by:

Daniel D. Thomas

NAVSEA DahlgrenDaniel.d.thomas3@navy.mil

Tele + 1 540-653-6941

Top Level Objectives: Coalition

• Architecture– Demonstrate the ability to perform testing with coalition participants

using land based test sites in a DEP/JDEP architecture. – Verify Multi Level Security (MLS) system does not functionally

degrade Link 11/16 coalition network performance. • Data Latency • Data Assurance • Data Accuracy

– Validate ability to run and transmit a centralized simulation involving coalition participants.

– Verify that CFBLnet can be used as a viable tool to expand JDEP functionality to coalition participants.

• Combat Systems– Measure and assess the ability to act as a force in a Joint/Coalition

environment – Verify joint/coalition system performance:

• Processing and receiving of force orders • Drop tracks • Joint/Coalition ID taxonomy

Test Objectives: Coalition (Cont.)

• RIMPAC Workup– Demonstrate JDEP/DEP via CFBLnet can be used for event execution

and analysis of coalition activities in preparation for RIMPAC 06. – Utilize ASTi to communicate in an operationally realistic environment in

the JDEP network with coalition participants. – Demonstrate JDEP/DEP network can be used to validate potential MMD

requirements and objectives. – Familiarize AT S&T/Training community with RIMPAC 06 scenarios and

platform representation for both US and AT platform participants. • Realized Benefits

– Provide a roadmap for integrating coalition partners into US tactical networks without compromising the security requirements of either party.

• Coalition Networking Attributes– Assess the long term feasibility of involving coalition partners in future

distributed networking events.

Participating Systems and Organizations

• Lead Organization - NSWCDN – Training & Readiness Branch (F21)

• POC Organizations:– CDSA Dam Neck – Test Planning/Execution – SPAWAR SSC – TSR SE, Link 11/16 Data Disclosure– RAN/DSTO – AT Test Planning/Execution

XCAOCCombat Air Operations Center (CAOC)

XE-2C Grp II HWILSpace and Naval Warfare Systems Center (SSC)

XAEGIS 7.1.1 HWILWallops Island (SCSC)

XTAOM/TPS-59 HWILCamp Pendleton (MCTSSA)

XANZAC HWILHMAS Watson

XLHD HWILCDSA Dam Neck

XE-2C HE2K HWILPatuxent River (NAWC)

XAWACS HWILBoeing – Seattle (AIL)

AEGIS 5.3.8.2 HWILNSWC Dahlgren (ATRC) X

DesiredRequiredNodeSite

Notional EL16CN Network Architecture

Link 11

Link 16

AWACS30/35 w/RSIP (E15)

LHDACDS BLK1 B/L

2.1.9 P/L25

E-2C Hawkeye3.02.07

TAOM / TPS - 59AN/TYQ-23v4

US Aegis (DF)7.1.1

AUS ANZAC2.3Link 16

Link 11

CEC

CEC

US Aegis5.3.8.2

CAOC

DG/RODG

Test Execution Schedule

Activities

AT Date/Time(GMT+10:00)

US Date/Time(EST)

Test Period 5Test Period 4Test Period 3Test Period 2Test Period 1

RIMPAC 06 Workup

•Site check-in• Pre-Brief• System initialization• Status checks• Modify network as necessary.•Train AT sailors for console operations.• Data transfer

Combat System

•Site check-in• Pre-Brief• System initialization• Status checks• Modify network as necessary.• Run Armageddon scenario overlaid with the TACOPS scenario to fully exercise TSR.• Test force order processing• Data transfer

Combat System

• Site check-in• Pre-Brief• System initialization• Status checks• Modify network as necessary.• Run Armageddon scenario.• Test force order processing• Data transfer

Architecture

•Site check-in• Pre-Brief• System initialization• Status checks• Modify network as necessary.• Run TACOPS scenario.• Data transfer

Architecture

• Establish voice communications.• Site check-in• Pre-Brief• System initialization• Status checks• System performance validations• Run Seven Track Scenario for gridlock and data registration purposes.• Measure latency.• Correlate• Run TACOPS scenario.• Data transfer

Day 5 (Friday)0900 - 1700

Day 4 (Thursday)0000 – 0800

Day 3 (Wednesday)0000 – 0800

Day 2 (Tuesday)0000 – 0800

Day 1 (Monday) 0000 – 0800

Day 5 (Thursday)1600 – 2400

Day 4 (Wednesday)0700 – 1500

Day 3 (Tuesday)0700 – 1500

Day 2 (Monday)0700 – 1500

Day 1 (Sunday)0700 - 1500

Current Status

• Event Planning Underway– Test Planning Beginning Discussions

• Procedures Based On Bi-Lateral Requirements– Data Analysis Beginning Discussions

• Defining Common Formats And Methods– Engineering Discussions To Determine Network Connectivity

• CFBL Connectivity & Availability

• Conflicts With Shared Assets Have Impacted Schedule– Original December Timeframe Not Available– In Processes Of Identifying a New Period Of Availability

• Documentation Underway– PA In Progress– Security Documentation Being Generated

Questions?