Tactical Infrastructure Enterprise Services (TIES)

Joint Capability Technology Demonstration (JCTD)

 

Joint Staff J6 C5IData and Services Division

james.m.hoffman4.mil@mail.mil22 April 2015

TIES JCTD Objectives

• Deliver a Joint, federated C2 capability to meet operational requirements in a Denied-Disconnected Intermittent Limited (D-DIL) bandwidth domain, including Anti-Access/Aerial Denial (A2/AD).

• Objectives: • Integration of USMC SOI and Navy ACS for seamless ship-to-shore ops

• Joint federated, prioritized chat

• Integrate Force Federation and Discovery Services (FFDS) for compression, data prioritization, synchronization, replication, and aggregation

• Tactical Identity and Access Management (IdAM) solution (FY15)

• Serve as a pathfinder and risk reduction for the deployed component of the Mission Partner Environment (MPE)and Joint Information Environment (JIE).

• Deliver a framework to enable common services at the Tactical Edge for reuse and acquisition efficiency.

TIES Provides a Testbed for Extending Select JIE Services to the Tactical Level

2

TIES JCTD Stakeholders

• Director of Defense Research & Engineering (DDR&E) Rapid Fielding (RF)• U.S. Southern Command (SOUTHCOM)• Joint Staff J6 (JS J6)• U.S. Navy, Office of Naval Research (ONR) and PEO C4I (CANES)• U.S. Marine Corps, Marine Corps Systems Command (MCSC) • U.S. Air Force, Air Force Life Cycle Management Center (AFLCMC)*• US Army, Program Manager Mission Command (PM MC)

3

TIES JCTD Capability Overview

US ArmyBCCS

USMCMAGTF C2

US Air ForceAOC WS

ACS

TSOA

SOI

US NavyCANES

USNCombat Centers

USMCCombat Ops

Center(COC)

USAFAir Ops Center

(AOC)

USA Tactical Ops Center (TOC)

Key Technologies:-FFDS (discovery, routing)-TS3 (IdAM)-XMPP (chat bridging)

Reference Implementations:-Security Framework(IdAM)-Selected SOA services optimized D-DIL & A2/AD info exchange (Prioritization, synchronization, aggregation)-Collaboration (chat)

Unclassified (U) FOUO

Unclassified (U) FOUO 4

02/09/2011 C2 ADS PUMA5

• Selected as TIES JCTD Operational Demonstration venue• Goals/Objectives for BQ (build off FY14 success)

– Federated Tactical Chat– Reuse of common core service infrastructure in a D-DIL, A2/AD environment – IdAM*

• Replication/synchronization of entity profile (attributes only) data between Enterprise nodes and Joint tactical edge units in D-DIL environments– Exchange between Joint tactical nodes using FFDS & TM-PEP– TIES solution automates the movement of attribute data to remote

nodes in preparation for importing into remote directory store• Efforts linked with BQ planners

– Continuing to participate in BQ CWG, NWG, Connectivity WG, and AWG– Navy / USMC from Suffolk*; Army from APG

• Current ongoing efforts ahead– Metrics, network requirements, and scenarios

Bold Quest 15.2/NIE 16.1 Status

X

MAGTF

TAC

1

UK

X

X

2 1

Combined Arms Maneuver

I

APOD

Forcible Entry Ops

I

X

MAGTF

Wide Area Security 15

(-)

Amphibious Assault Establish the Lodgment Offensive/Defensive OperationsBattle HandoverShaping

• TIES JCTD Bold Quest 15.2 Vignettes- Fire Vignette- Foreign Humanitarian Assistance w/Medivac- Logistics/Resupply

TIES JCTD Scenario for BQ 15.2

6

TIES Navy/USMC

Afloat Nodes

TIES Army

Node

TIES USMC

Ashore Node

Bolden

Q

X

Q

02/09/2011 C2 ADS PUMA7

• Operations Center “operators” (Navy MOC, USMC COC, Army TOC) during BQ 15-2/NIE 16-1

• Use C2 applications (e.g. chat, COP, JC2 widgets, etc)– Final list still TBD

• Provide feedback

• Complete survey/questionnaire

Reserve Support

TIES Participating Systems BQ 15.2

• Tactical Systems– TCS (IOSv1) v4.2.0.9– JTCW Client and Gateway v1.1.0.6– Transverse Chat Client v1.8

(Approved in DADMS for Navy and Not Reviewed for USMC)

– Spark Chat Client v2.6.x• Navy only; maybe (2.6.3 is

latest but is disapproved for USN and approved for USMC in DADMS) See DML Comments

– JC2 CUI v14-1– GCCS-A v4.3.0.0– C2 Alerting

• TIES Infrastructure– FFDS v3– TM PEP– OTR– ACS v1.2.1– FCS v3.8– OpenFire (APG)

• Only if FCS impacts BQ chat

– TSOA v4.0.2.0.x

8

TIES JCTD COIs

COI 1: Operational Effectiveness / Functionality (Does the system perform as intended?) Do the TIES capabilities provide the ability to share prioritized C2 data and reuse information technology (IT) services in operational environments, including D-DIL?

COI 2: Operational Suitability (Is the system suitable, secure, and interoperable?) Are TIES capabilities suitable to operate with participating SOA infrastructure and C2 systems?

COI 3: Mission / Operational Impact (Does the system make a positive contribution?) Do TIES capabilities improve the joint warfighter’s ability to conduct operations in operational environments, including D-DIL?

11To see a further breakdown of these COIs, see the Integrated Assessment Plan

TIES OUA Data Requirements

1. Situational Awareness Interoperability: All participants can produce and/or consume tracks and overlays with all other nodes. USMC C2 alerts can be shared with all nodes.

2. Federated Chat Collaboration: All participants can collaborate via federated and prioritized chat.

3. IdAM data exchange: Army/Navy/USMC exchange IdAM data (LDIF files) and utilizing these entities data/attributes with each other.

12

TIES JCTD Schedule

Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Demonstrations/Assessments

CONOPS draft

CONOPS V1 CONOPSFinal

Deliverables

Capability Development

TD 1 Report

LOUA – Limited Operational Utility Assessment OUA – Operational Utility Assessment IATT- Interim Authority to Test

2014

2015

2013

Final Report(including LL, Ref Arch, etc)

Transition PlanManagement PlanImplementation Directive

Integrated Assessment Plan

IntegrationFFDS, Chat Fed, ACS

Capability Development

2014

IntegrationCapability

Development

OUA Report

Integration

Transition Agreements

Military Utility Assessment

Demonstrations/Assessments

Deliverables

Capability Development

BA14 IPC

BA14 MPC

TD 1

BA14 FPC

TD 2

BQ 15-2/NIE 16-1(OUA)

OUA Demo Execution Plan

LOUA Demo Execution Plan

TD 2 Report

Nov Integration Event June Integration

Event

IATT submission

IATT submission

SW lockdown

BACKUP

Glossary

• ACS – Agile Core Services• AOC – Air Operations Center• COC – Combat Operations Center• CPOF – Command Post of the Future• D-DIL - Denied, Disconnected, Intermittent, Limited• DJC2 - Deployable Joint Command and Control• FCS – Federated Chat Server• FFDS – Federation and Force Discovery Service• IOS - Intelligence Operations Server• JTCW – Joint Tactical Common Operational Picture Workstation• LAN – Local Area Network• MGEN - Multi-Generator (network traffic generation tool)• OTR – Open Tactical Router• SOI – Service Oriented Infrastructure• TCP – Transmission Control Protocol• TCS – Tactical Chat Server• TM-PEP – Traffic Management – Policy Enforcement Point• TOC - Tactical Operations Center• TSOA – Tactical Service Oriented Architecture• USAF – United States Air Force• WRED – Weighted Random Early Discard• XMPP - Extensible Messaging and Presence Protocol

15

TIES TD1 System View

C2 LAN

COC

Navy ship

D-D

IL

TOC

USMC SOI Using ACS

USAF Information

ServicesPrototype

ACS

XMPPSpark Client

SATCOM (OTR)FFDS

USAF AOC

ACS

TCS

TransverseClient or

AC plugin

FFDS

XMPPSpark Client

FFDS SOI onTSOA

Bridge(s)Bridge(s)

D-D

IL

LAN

LAN

AgileClient

AgileClient

Infrastructure Services Infrastructure Services

Infrastructure Services

IOSv1

JTCW

IOSv1

JTCW

LAN

FFDS

XMPPTransverse

Client

Infrastructure Services

USAF Information

ServicesPrototype

FCS

FCS

FCS

TM-PEP

TM-PEP

TM-PEP

TM-PEP

C2 Alert Service

C2 Alert Service

TIES TD1 Architecture (SV-1)

17

TIES JCTD TD1 Results

• Integrated the TIES services with stakeholder C2 systems to enable critical information exchange in a D-DIL environment– USMC TSOA/SOI integration with ACS (when embarked on Navy

ships) and FFDS– USAF Information Systems Prototype (airspace management)

services integration with ACS & FFDS• Evaluated the TIES services in challenging D-DIL networks

– FFDS and TM-PEP used to prioritize and deliver the Joint Services’ tactical C2 data between simulated afloat and ashore sites

– Federated Chat Service (FCS) provided an XMPP chat capability that prioritized chat messages based upon the predefined information prioritization policy (e.g. by chat room) between all federated sites

• Challenges:– JMS session bug, management traffic issue, FFDS client

reconnection issue, insufficient LAN documentation

JCTD IdAM Concept

19

Unclassified (U) FOUO

Unclassified/FOUO

Identity and Access Management Reference Architecture

DOD IdAM Capability Viewpoint Taxonomy (CV-2)

21

Figure 3 – DOD IdAM Capability Viewpoint Taxonomy (CV-2)

Contact Data Lookup Operational Capabilities

Web-Based Contact Data Lookup

Resource-Embedded Contact Data Lookup

Access Accountability Operational Capabilities

Create and Maintain IdAM Event Logs

Enable Access to IdAM Event Logs

Dynamic Access Control Operational Capabilities

Identification

IdAM Operational Capabilities

Site-LevelIdAM Data Management

DOD-LevelIdAM Data Management

Community of Interest (COI)-LevelIdAM Data Management

IdAM Data Capabilities

Authentication

Authorization

Access

IdAM Capabilities