Digital Interoperability

Developing and Implementing a Network Architecture to Support Enhanced Company Level Operations

Colonel George MalkasianAC/S G-6 1st MARDIV

AFCEA Luncheon21 January 2015

Agenda

• Expeditionary Force 21

• Digital Interoperability

• 1st Marine Division Commanders Intent

• Objectives

• C2 Architecture

• STEEL KNIGHT Operational Demonstration

• Conclusion

The New Normal

A flexible, secure, and reliable network is essential to effectively operate in a

disaggregated and dynamic environment

Expeditionary Force 21

The dynamic operating environment and concept of employment detailed in Expeditionary Force 21 have altered the C2 capabilities required to operate.

EF-21 Requirements:•Improving the ability to share situational awareness and mitigate current, significant gaps in up-to-date intelligence products sourced from commercial, coalition, interagency, and DOD systems and processes. •Terrestrial communications system with a 65 nm minimum range via line of sight, retransmission, relay, or combinations of all three means.•Improve communications robustness within and to/from the MAGTF to ensure the reliable flow of information in a cyber-contested environment. •Improving system interoperability and security across all domains and between forces from other Services.•Explore the use of ground communication systems aboard Navy shipping, specifically in the Landing Force Operations Center and the Supporting Arms Control Center.

Expeditionary Force 21

• A critical component of EF-21 is the employment of the Company Landing Team and the C2 requirements necessary to conduct Enhanced Company Level Operations.

“…infantry battalions will be reviewed…to ensure that they have the capability and capacity to support one or more employed company landing teams simultaneously. Company landing teams provide a means to engage forward in more locations and respond to crises. During entry operations they enable dispersed operations to secure landing sites or maneuver deep to inland objectives. Lastly, they must have the maneuver capability to disperse and mass throughout the littorals. During crises they can form the basis of a immediate response.“

• Several efforts are underway to meet this requirement. The Marine Corps requires a holistic plan to accomplish this without the unnecessary expenditure of precious resources.

UNCLASSIFIED

Aerial Relay

In-Transit C2

Naval Integration

Internal C2

BLOS Reach Back

Aviation Integration

EF-21 Standard.•Given the anticipated complexity, tempo, and distributed nature of future power projection operations, naval forces will require both advanced information technology and flexible command relationships to support an increased level of coordination and integration among all elements of the force.

Digital Interoperability

Commanders IntentPurpose. Operationalize the concepts developed as part of the Talon Reach LOEs for employment by deploying forces.

Method. 1st Marine Division utilizes existing capabilities to develop and validate TTPs to extend C2 to Mission Commanders, and key staff, through all phases of mission execution.

Endstate:

1)Validate C2 capabilities and TTPs with existing equipment for employment by deployed units;

2) Identify immediate solutions to meet and/or enhance near term deployment C2 capabilities;

3)Capture and inform HQMC C4 to influence the ongoing process to meet the long term solution for the Marine Corps

Objectives- Validate Equipment.

- PRC-117G to tethered computer solution- Validate functionality- Assess functionality/ease of use during transit

- At a minimum, provide Chat / File Transfer (Still Imagery / Documents)

- Validate ability to extend C2 to Raid Force (Air and Surface).- Air: Communicate digitally via TACSAT & ANW2 with LFOC & R&S - Surface: Communicate digitally via SATCOM, TACSAT & ANW2 with LFOC & R&S

- Validate ability to digitally C2 Raid Force during transit.- Intra-raid force digital communication via ANW2 within the aircraft / vehicle- Intra-raid force digital communication via ANW2 & TACSAT between aircraft / vehicle

- Validate ability to digitally C2 Raid Force on the objective.- Intra-raid force digital communication via ANW2 - Digital communication via ANW2 with all elements ashore- Aerial relay of ANW2- LFOC reachback via SATCOM, TACSAT, & ANW2

- Enable future employment.- Develop TTPs- Identify equipment deficiencies and shortfalls- Assess the durability of equipment

C2 Architecture

TestingRequirements:•Equipment

• Gateway Computer Functionality – Dual connection TACSAT - ANW2• Software Load

•LFOC to Raid Force Communication (TACSAT)• Chat from LFOC to Raid Force• File transfer from LFOC to Raid Force

•Intra-Raid Force Communication (ANW2)• Chat within Raid Force• File transfer within Raid Force

•Integration • MV-22 Ground testing• MV-22 Flight testing• AAV NOTM testing

•Enhanced capabilities• Seamless LFOC to Raid Force communication, no manual relay (Chat & File

Transfer• Enhanced Software Capabilities (Moving Maps, Video)

Panasonic Toughpad

Obj 1

Co 3/7 (ME)T1: Attack to Destroy Obj 1P1: Prevent EN interference with amphibious assault

Co A/1/5 T1: Attack to Fix Obj 2P1: Prevent EN QRF from interfering with ME attack

1st Recon T1: ITG AAV LandingsP1: Assist navigation and securityT2: Provide ISRP2: Identify enemy pos

3/7

(-)

1/5

(-)

3

SCI Raid: CONOPS

Obj 2

In Transit C2 (Air)

2D PLT, 1st SQD LDR

ANW2

ANW2ANW2

GATEWAY

ANW2

JTAC/FIST

2d PLT, PLTSGT

ANW2

GATE WAYBACK-UP

2d PLT,1st SQD LEADER

3D PLT CMDR

TACSAT

LFOC

1ST PLT CMDR

ANW2

- PRC-117G- Tethered Computer

C2 Bird

R&S

ISR

2D PLT CMDR

CO

C-Band

2D PLT 3d SQD LDR

Intra Raid Force C2

R&S

CO

2d PLT, 2d SQD LDR

1st PLT CMDR

2d PLT, PLT SGT

JTAC/ FIST

2nd PLT CMDR

3rd PLT CMDR

GATEWAYBack-Up

2d PLT, 1st SQD LDR

ANW2

DEDICATEDTACSAT

LFOC

- PRC-117G- Tethered Computer

C2 Bird

Surface Raid Force

Ku SATCOM

ISR

2d PLT, 3d SQD LDR

C-Band

CO Surface Raid Force

San ClementeIsland

LFOC

MCAS Miramar

1. 1000: Raid Force Launches.

2. 1015 -1045: Raid Force loiters IVO LFOC; receives updates, change of mission.

3. 1045-1130: Raid Force travels BLOS IVO El Centro

4. NLT 1130: Raid Force IVO SCI

5. 1200: Raid Force inserted IVO Obj 3

6. 1200-1230: C2 Bird aerial refuel IVO SCI

7. 1400: Raid Force extracted, RTB

SCI Tilt Rotor Raid Timeline

1

2

3

4

5

7

6

29 Palms

Conclusion

• The digital architecture worked• Refined TTPs will improve performance• Additional software will continue to expand

functionality

• Way Forward• Training is ongoing to prepare 3/7 for deployment• Coordination with CD&I Digital Interoperability

Working Group on the near term solution• Continued development of the long term solution